Turn Notion partner introductions into HelloLeads leads
Write down an introduction in your Notion partner hub and let Notis put the new prospect into HelloLeads for follow-up.
Trigger
Page Created
Triggers when a new Notion page is created. Customer optionally scopes with at most one of: - data_source_id: new row in this data source - parent_page_id: new sub-page under this page (immediate parent only) With neither set, fires for any new page in the workspace the integration has access to. Notion sends ~60s aggregation latency on most events.
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
Warm introductions lose momentum when creating a record is postponed until after the next meeting or task.
- Capture warm introductions while context is fresh.
- Keep partner-sourced opportunities together in HelloLeads.
- Reduce the number of follow-up steps after receiving an introduction.
Setup
Build it in a few focused steps.
- 1Connect Notion and HelloLeads to Notis once through the portal.
- 2Create an automation in the portal or ask Notis conversationally to create one.
- 3In one plain-language instruction, ask Notis to create a HelloLeads lead for each new introduction page under your partner hub.
- 4Choose the Notion Page Created trigger scoped to the partner hub, select a channel for run reports, and test with one real introduction.
Questions about this workflow
Can this watch a specific Notion parent page?
Yes. Page Created can be scoped to new subpages under a specified parent page.
What makes this useful for partner referrals?
It turns the act of recording an introduction into the start of a trackable HelloLeads follow-up.
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.