Skip to content
Per-pair page

Connect Notion to Hunter in two minutes.

Real-time triggers from Notion, ready-made actions in Hunter. Filter, transform, and route without writing a line of code.

Trigger app
Notion as the trigger

Workflows fire when something happens in Notion.

Action app
Hunter as the action

Workflows do something in Hunter, instantly.

Both directions

Pick the way that fits your stack.

Pair pages are mirrored. Each direction gets its own dedicated page.

NotionHunter

When something happens in Notion, do it in Hunter.

3 Notion triggers wired to 4 Hunter actions. Most-used pairing: New Database ItemHunter Domain Search.

HunterNotion

Or fire it the other way around.

0 Hunter triggers wired to 12 Notion actions downstream.

  • Use any trigger in the catalog as the upstream.
See HunterNotion
Popular pairings

Common Notion → Hunter workflows.

Pick a pairing to set it up in two minutes. Each one is a fully editable recipe.

Showing 9 of 12 combinations
When new database item in Notion, hunter domain search in Hunter.

Fires when a new item is added to a Notion database. Common use: mirror submissions into another tracker, send notifications, or run AI enrichment on the new row.

When new database item in Notion, hunter email count in Hunter.

Fires when a new item is added to a Notion database. Common use: mirror submissions into another tracker, send notifications, or run AI enrichment on the new row.

When new database item in Notion, hunter find email in Hunter.

Fires when a new item is added to a Notion database. Common use: mirror submissions into another tracker, send notifications, or run AI enrichment on the new row.

When new database item in Notion, hunter verify email in Hunter.

Fires when a new item is added to a Notion database. Common use: mirror submissions into another tracker, send notifications, or run AI enrichment on the new row.

When new page in Notion, hunter domain search in Hunter.

Fires when a new page is created in a Notion database (functionally the same event as Database Item Added; pick whichever name feels natural).

When new page in Notion, hunter email count in Hunter.

Fires when a new page is created in a Notion database (functionally the same event as Database Item Added; pick whichever name feels natural).

When new page in Notion, hunter find email in Hunter.

Fires when a new page is created in a Notion database (functionally the same event as Database Item Added; pick whichever name feels natural).

When new page in Notion, hunter verify email in Hunter.

Fires when a new page is created in a Notion database (functionally the same event as Database Item Added; pick whichever name feels natural).

When page updated in Notion, hunter domain search in Hunter.

Fires when a page is updated in a Notion database. Combine with property filters to react only to specific transitions (e.g. Status to Done).

How it works

Connect Notion and Hunter in five steps.

No code, no glue, no half-day setup. Each step is one click.

  1. 1
    Connect
    Authorize Notion and Hunter

    Open Tiny Command, authorize Notion and Hunter once each. Both connections are available to every workflow on your account.

  2. 2
    Trigger
    Pick a Notion trigger

    Drop the Notion → New Database Item trigger onto the canvas. Tiny Command auto-registers the webhook.

    POST /v1/webhooks/notion.trigger-database-item-added
  3. 3
    Transform
    Add a filter or AI step

    Optionally add a Filter node ("subject contains URGENT") or an AI step ("classify intent") between trigger and action.

  4. 4
    Action
    Add the Hunter action

    Drop the Hunter → Hunter Domain Search action below it. Map fields from the Notion payload into the Hunter inputs.

    hunter.domain-search
  5. 5
    Publish
    Publish and forget

    Hit Publish. Tiny Command runs it in production from second one. Watch the run-log fill up.

FAQ

Questions about Notion + Hunter.

How long does it take to connect Notion and Hunter on Tiny Command?
Under two minutes. Authorize Notion and Hunter once each, drop the Notion trigger and Hunter action onto a workflow canvas, map a couple of fields, and publish. No code, no glue.
Is the Notion ↔ Hunter integration real-time?
Yes. Both Notion and Hunter expose webhooks, so events from one fire workflows in the other within seconds rather than on a polling interval.
Can I filter or transform data between Notion and Hunter?
Yes. Add a Filter node to only pass through matching events, a Switch node to branch by value, or an AI / Code node to transform payloads before they hit Hunter.
What Notion events can trigger a Hunter workflow?
Any of the 3 Notion triggers, including "New Database Item". Each fires in real time when the matching event happens in Notion.
Do I need a paid plan to use Notion with Hunter?
No. There's a free tier that covers most Notion+Hunter use cases without a credit card. Paid plans unlock higher run volumes and team features when you outgrow it.
What if I want Hunter → Notion instead?
Build it the same way, in reverse. There's a dedicated /integrations/hunter/with/notion page with the reverse-direction triggers and actions.
Related

Other apps that pair well with Notion.


Wire Notion to Hunter in 2 minutes.

Free tier available. No credit card. No onboarding call.