Capture prospects mentioned on a Notion referral page
Keep referral discussion on its Notion page and have Notis create a HelloLeads lead when a comment contains a clear prospect to follow up with.
Trigger
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Action
Create Lead
Tool to add a new lead into HelloLeads. Use when you need to push a fresh lead record with mandatory first name and list key.
Why this helps
A shared referral page can collect useful names faster than someone can remember to transfer them into a lead tracker.
- Focus monitoring on the page your team uses for referrals.
- Reduce the risk of a name getting buried in comments.
- Keep follow-up organized in HelloLeads.
Setup
Build it in a few focused steps.
- 1Connect Notion and HelloLeads to Notis once through the portal and ensure Notion comment access is enabled.
- 2Create an automation in the portal or ask Notis conversationally to create one.
- 3Ask Notis in one plain-language instruction to create a HelloLeads lead when a comment on your referral page identifies a prospect.
- 4Choose the Notion New Comment trigger for that page, select a channel for run reports, and test with one real referral.
Questions about this workflow
How is this different from watching all comments?
New Comment can be scoped to a specified Notion block or page, which keeps the automation focused on your referral page.
What should the prompt say?
Describe the page's purpose and tell Notis to create a lead only when a comment provides a clear prospect to follow up with.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Helloleads. A trigger fires from one place; an action lands in another.
Notion triggers
Helloleads actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Lead
Tool to add a new lead into HelloLeads. Use when you need to push a fresh lead record with mandatory first name and list key.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
List Leads
Tool to list all leads from HelloLeads. Use after authentication to fetch the entire lead list. Returns empty list if none found.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
List Lead Lists
Tool to retrieve all lead list keys from HelloLeads. Use when you need to enumerate available lists for lead insertion.
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.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
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.
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 Helloleads, 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 Helloleads.