Hunch
Tutorials

Get Hunch set up and working.

Step-by-step tutorials for every part of the platform. Start with the Knowledge Base and work through in order.

01
10 min

Set up your Knowledge Base

The Knowledge Base is where you tell Hunch about your business. Hunch uses this when researching accounts, evaluating ICP fit, and writing why-now briefs. The more detail you add here, the better Hunch's output gets.

1

Go to Knowledge Base

In the left sidebar, click Knowledge Base. You'll see a set of sections Hunch has pre-created based on common sales intel categories.

2

Auto-fill from your website

Enter your company domain and click the Scrape & fill button. Hunch fetches your site and pre-populates Overview, Value Proposition, and Product sections. Review what it wrote and correct anything that missed the mark.

3

Fill in your ICP

Edit the ICP (Ideal Customer Profile) section. Describe who your ideal customer is in plain English: company size, industry, geography, stage, and any other characteristics. Be specific. The more precise your ICP, the more accurately Hunch scores accounts against it.

4

Add any other sections you want

You can add sections for Target Market, Competitors, Proof Points, or a Custom section with any sales context that matters. Each section is a markdown editor. Add what your reps would want to know when researching an account.

5

Save and move on

Changes save as you go. You can always come back and add more. Hunch references this content every time it runs a signal search or evaluates an account.

02
8 min

Define your signals

Signals are the buying intent indicators you want Hunch to track. You define each one in plain English. Hunch compiles your description into a research criteria set it uses when monitoring your accounts.

1

Go to Signals

Click Signals in the left sidebar. You'll see a list of any signals already created for your workspace.

2

Click Add Signal

A dialog opens. Give the signal a name (for your reference) and a plain English description of what you want Hunch to find.

3

Write a specific description

The description is the core of how Hunch works. Be concrete: 'Companies that recently hired a VP of Sales or CRO' is better than 'leadership hiring.' Include timeframe context if relevant: 'in the last 60 days.' The more specific, the better the output.

4

Set priority and timeframe

Choose a priority (High, Medium, or Low) and a timeframe in days. Timeframe controls how far back Hunch looks when searching for evidence of this signal.

5

Activate and run

Save the signal. Hunch will run it against all your active accounts on the next daily cycle, or you can trigger a manual run from the Signals page. Hunch runs that complete appear in the run history at the bottom of the page.

03
5 min

Add accounts to monitor

Accounts are the companies Hunch monitors. You can add them manually, by pasting a list of domains, or via the API. Once active, Hunch runs your signals against them on a daily schedule.

1

Go to Accounts

Click Accounts in the left sidebar. The table shows all accounts in your workspace with their status, latest signal, and ICP score.

2

Click Add Accounts

In the dialog, paste one or more company names or domains. Hunch enriches each one with firmographic data (employees, industry, location, funding, tech stack, and more) and adds them to your list.

3

Assign tags and owners

Inline on each row, you can add tags and assign the account to a team member. Tags let you filter your account list. Owners control who gets notified when a signal fires on that account.

4

Set status to active

New accounts start in 'suggested' status. Hunch only monitors accounts with 'active' status. To activate, click the status column on any row and set it to Active. You can activate in bulk from the table.

5

Or add via the REST API

If you're pulling accounts from a CRM or building automation, use the POST /api/v1/accounts endpoint. It accepts up to 500 accounts in a single request.

04
6 min

Use the Suggested tab

The Suggested tab shows accounts Hunch found for you based on your saved searches. Hunch re-runs these searches every day and adds net-new accounts to Suggested. This is how you discover companies you weren't already tracking.

1

Open the Suggested tab

From the Accounts page, click the Suggested tab. You'll see any accounts Hunch surfaced from your saved searches, sorted by ICP fit score.

2

Review each account

Click any account to open its detail drawer. You'll see the firmographic data, the signal that matched, and Hunch's why-now brief explaining why this account is worth reaching out to.

3

Activate or reject

For each suggested account, choose to activate it (moves it to your active monitoring list) or reject it (hides it from future suggestions). This daily review workflow keeps your pipeline clean.

4

Set up a saved search

To control what Hunch surfaces in the Suggested tab, set up a saved search. From the accounts table, define the combination of signals, geography, industry, and employee range you want Hunch to look for. Save it. Hunch re-runs it daily and adds any new matches to Suggested.

05
3 min

Connect Slack notifications

Hunch posts to a Slack channel of your choice the moment a signal fires. The full research brief comes through inline, so your reps see the context without leaving Slack.

1

Go to Settings

Click Settings in the sidebar, then scroll to the Integrations section.

2

Connect Slack

Click Connect Slack. Hunch will open Slack's OAuth flow. Select your workspace and authorize the Hunch bot.

3

Choose a channel

After connecting, enter the name of the Slack channel you want Hunch to post to. This can be a #signals channel, #sales, or any channel your team watches.

4

Enable and test

Toggle Slack notifications on. Click Send test message to verify the connection. Hunch will post a sample signal brief to confirm everything is working.

5

Individual DMs (optional)

Team members can receive personal DMs for accounts assigned to them. In Settings, under notification preferences, enter your Slack Member ID and enable personal alerts.

06
5 min

Configure email and webhooks

The daily email digest delivers a summary of the past 24 hours of signal activity to each team member's inbox every morning at 8am UTC. Webhooks push signed event payloads to any external endpoint when a signal fires.

1

Enable the email digest

In Settings, scroll to the Email Digest section. Toggle it on and confirm the email address. Each team member can control their own digest subscription from their profile.

2

What the digest contains

The digest includes the top signals detected in the past 24 hours and the top suggested accounts from your saved searches. It links back to the Hunch app for full details.

3

Set up a webhook (optional)

In Settings, scroll to Webhooks. Paste your HTTPS endpoint URL. Hunch will generate a signing secret. Store it securely in your environment and use it to verify incoming payloads.

4

Webhook event types

Hunch sends three event types: signal.detected (when a signal fires on an active account), account.suggested (when a new account appears in your Suggested tab), and daily.digest (a daily summary payload for programmatic consumption).

5

Verify webhook signatures

Each webhook payload includes a Signal-Signature header with an HMAC-SHA256 hash of the payload body, signed with your secret. Always verify this before processing the payload in your system.

07
8 min

Use the REST API

The Hunch REST API gives you full programmatic access to accounts, signals, runs, ICPs, and workspace data. Use it to pull signal results into your own tools, push accounts from your CRM, or trigger runs on a custom schedule.

1

Generate an API key

In Settings, scroll to API Keys. Click Create API key, give it a name, and copy the key. It's shown once and can't be retrieved again, so save it somewhere secure.

2

Authenticate requests

Pass your key as a Bearer token in the Authorization header on every request: Authorization: Bearer sk-your-key. All endpoints return JSON.

3

List your accounts

GET /api/v1/accounts returns your full account list, sorted by score. You can filter by status, owner_id, tag, and domain. Paginated at 50 per page.

4

Fetch signals for an account

GET /api/v1/accounts/:id/signals returns all signals detected on a specific account, including the headline, narrative, evidence sources, and suggested outreach copy.

5

Trigger a signal run

POST /api/v1/signals/:id/run triggers Hunch to run a specific signal definition against all active accounts. Useful if you want to trigger runs from your own scheduler instead of relying on Hunch's daily cron.

6

Full reference

See the API reference at /api-docs for all endpoints, parameters, and response formats.

Need help getting set up?

Email us at hello@gethunch.ai and we'll walk you through the setup and help you define your first signals.