Save approved prospects from a Notion database
Move a prospect into Hunter at the point you mark them ready for your pipeline.
Trigger
New Page
Triggers when a new page is added to a Notion database.
Action
Create Lead
Tool to create a new lead. use after gathering all prospect details to save them to your hunter account.
Why this helps
Approved prospects can sit in a planning database because adding them to the lead tool feels like a separate task.
- Tie lead creation to the moment a prospect is ready.
- Avoid re-entering details in a second tool.
- Keep an explicit approval step in the Notion workflow.
Setup
Build it in a few focused steps.
- 1Connect Notion and Hunter to Notis once in the portal.
- 2Create an automation in the portal or ask Notis conversationally.
- 3In one plain-language instruction, ask Notis to create a Hunter lead for a newly added Notion prospect only when its page clearly marks it approved and includes usable contact details.
- 4Choose Notion's New Page trigger scoped to the prospect database and a channel for run reports.
- 5Test with one real approved prospect page.
Questions about this workflow
Can I limit this to a particular database?
Choose the New Page trigger for the prospect database when creating the automation.
Will an unapproved page create a Hunter lead?
The prompt should instruct Notis to create a lead only when the page clearly indicates approval and contains usable details.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Hunter. A trigger fires from one place; an action lands in another.
Notion triggers
Hunter actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Account Information
Tool to retrieve information about your hunter account. use when you need to check your plan details and usage limits after confirming credentials.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Company Enrichment
Tool to get enrichment information for a company by its domain. use when you need full company details (industry, description, location, metrics) from hunter.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Create custom lead attribute
Tool to create a new custom lead attribute in your account. use after deciding on the attribute label.
Comment Created
Triggers when a new comment is created in Notion. Optional `page_id` filter scopes to comments on a specific page. When omitted, fires for any new comment in the workspace the integration has access to. Requires the 'Read comments' capability on the Notion integration. If a connection was authorized before that capability was enabled, the user must re-authorize the connection for comment events to flow.
Create Lead
Tool to create a new lead. use after gathering all prospect details to save them to your hunter account.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Create Leads List
Tool to create a new leads list. use when you need to organize leads into a custom list before adding leads.
Database Created
Triggers when a new Notion database (the container) is created. A database is the post-2025-09-03 container that holds one or more data sources. This trigger fires for the container's creation event (`database.created`), distinct from `NOTION_DATASOURCE_CREATED` which fires when a new data source is added to an existing database. Most customers calling Notion's `POST /v1/databases` (the legacy API) or creating a database via the Notion UI will see this event. Adding a new data source to an existing database fires `data_source.created` instead — use `NOTION_DATASOURCE_CREATED` for that. Notion's payload puts `entity.type: "block"` (the container is a `child_database` block in the content tree) and `entity.id` is the database id.
Delete Custom Attribute
Tool to delete an existing custom attribute. use after confirming the attribute id to be removed.
Data Source Created
Triggers when a new Notion data source is created. Fires workspace-wide. The payload's `data.parent` carries the data source's tree parent (typically the teamspace) for downstream filtering. A single template-based database creation can fire multiple `data_source.created` events at once — one per data source the template instantiates.
Delete Lead
Tool to delete a lead. use after confirming the lead's id to remove it from your hunter.io account.
Data Source Schema Updated
Triggers when a Notion data source's schema is updated. Fires on column add / remove / rename. Payload includes `data.updated_properties: [{id, name, action}]` so consumers can discriminate the kind of change downstream. Optional `data_source_id` filter scopes to schema changes on a single data source. When omitted, fires for any schema change in the workspace the integration has access to. Note: adding a column also fires `page.properties_updated` once per existing row in the data source. Customers wanting a single structural-change signal should use this trigger.
Delete Leads List
Tool to delete a leads list by its id. use after confirming the leads list id to remove it from your hunter.io account.
Connect any two apps with Notis in the middle.
Notion and Hunter, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Hunter.