Turn a company comment into a domain lookup
When a Notion comment raises a company to research, have Notis ask Hunter to identify its likely domain.
Trigger
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.
Action
Find Company Domain
Resolve a company name into its most likely domain name(s).
Why this helps
Useful research requests buried in comments are easy to forget once the conversation moves on.
- Give company research requests a clear next step.
- Reduce the need to revisit comment threads to remember context.
- Resolve a likely domain while the discussion is still fresh.
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 tell Notis what to do when a company is mentioned in a Notion comment.
- 3Use one plain-language prompt to request a Hunter domain search from the comment's company context.
- 4Select Notion's Comment Created trigger and choose a channel for run reports.
- 5Test by adding a comment about one company you can verify.
Questions about this workflow
Does this run on every comment?
The workspace-wide Comment Created trigger fires for new comments accessible to the integration; Notis can use the comment context described in your prompt.
Is a Notion capability required?
Notion's Read comments capability must be enabled, and an older connection may need to be re-authorized for comment events.
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.
Search People Across Companies
Search people across every matching company; addresses stay masked until revealed.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Count Reachable People
Estimate how many people are reachable across every company matching your filters.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Search Companies
Search a B2B company database with structured filters like location, industry, and size.
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.
Find Domain Emails
List all email addresses found for a domain, with sources and confidence scores.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Find Company Domain
Resolve a company name into its most likely domain name(s).
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.
Enrich Person and Company
Look up a person's profile and their company's profile from one email address.
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.
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.
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.