Revisit Heyreach lead lists when qualification changes
Update a prospect's priority in Notion and retrieve Heyreach list context as a cue to reassess your outreach queue.
Trigger
Page Properties Updated
Triggers when properties of a Notion page are updated. Customer optionally scopes with at most one of: - data_source_id: any row in this data source - page_id: this specific page - parent_page_id: any page whose immediate parent is this page With none set, fires for any property change in the workspace the integration has access to. Adding a column to a data source fires this trigger once per existing row. Customers can branch on `data.updated_properties` (array of property IDs) to filter downstream.
Action
Get Leads From List
Tool to get a paginated list of leads from a lead list. use when you need to filter and page through leads for a specific list.
Why this helps
A changed prospect priority can remain disconnected from the lead list you use to plan outreach.
- Links qualification changes with a list review.
- Helps surface list context when priorities shift.
- Creates a repeatable review cue without another reminder to yourself.
Setup
Build it in a few focused steps.
- 1Connect Notion and Heyreach to Notis once through the portal.
- 2Create an automation in the portal or ask Notis conversationally to revisit a Heyreach list after a prospect update.
- 3Use one plain-language instruction to describe when a change should prompt a list retrieval and what list to review.
- 4Select the Notion Page Properties Updated trigger and choose a reporting channel.
- 5Test by changing the priority of one real prospect record.
Questions about this workflow
Will this update prospect priority in Heyreach?
No. The action retrieves leads for review; it does not update them.
Can I specify the relevant list in the prompt?
Yes. Describe the list context in your plain-language instruction.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Heyreach. A trigger fires from one place; an action lands in another.
Notion triggers
Heyreach actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Check API Key
Tool to check if the api key is valid. use before making other api calls to confirm authentication.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Empty List
Tool to create an empty list. use after deciding on list name and type.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Create Webhook
Tool to create a new webhook. use when you need programmatic callbacks for heyreach events after confirming a valid api key.
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.
Delete Webhook
Tool to delete an existing webhook. use when you need to remove callbacks for outdated or unwanted webhooks.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get All Campaigns
Tool to retrieve all campaigns. use when you need a paginated list of campaigns for management or reporting.
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.
Get All Leads
Tool to retrieve all leads in a heyreach list. use when you need paginated collection of leads after confirming a valid api key.
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.
Get All LinkedIn Accounts
Tool to retrieve all linkedin accounts. use when you need a paginated list of linkedin accounts after confirming a valid api key.
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.
Get All Lists
Tool to retrieve all lists. use when you need a paginated list of lists after confirming a valid api key.
Connect any two apps with Notis in the middle.
Notion and Heyreach, 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 Heyreach.