Enrich prospect batches from a Notion intake
Reduce research overhead by enriching a batch of people from Apollo when intake arrives.
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
Bulk people enrichment
Use to enrich multiple person profiles simultaneously with comprehensive data from apollo's database.
Why this helps
Prospect research requires switching between tools and repeating the same profile lookup for each person.
- Gather profile data for multiple people in one action.
- Reduce repeated prospect research steps.
- Keep intake and enrichment connected.
Setup
Build it in a few focused steps.
- 1Connect Notion and Apollo to Notis once through the portal.
- 2Create an automation in the portal, or ask Notis conversationally.
- 3Describe using a new Notion batch intake page to enrich the included people in Apollo.
- 4Choose the Notion Page Created trigger, select a run-report channel, and test with a small real batch.
Questions about this workflow
How many profiles can bulk enrichment handle?
Apollo bulk people enrichment supports multiple person profiles; describe a manageable batch in your instruction.
Will enrichment create contacts in Apollo?
This action enriches person profiles. It is not the same as creating Apollo contacts.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Apollo. A trigger fires from one place; an action lands in another.
Notion triggers
Apollo actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add Contacts to Sequence
Adds contacts to a specified apollo email sequence by initiating an asynchronous background job and returning its details.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Bulk organization enrichment
Enriches data for up to 10 organizations simultaneously by providing a list of their base company domains (e.g., 'apollo.io', not 'www.apollo.io').
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Bulk people enrichment
Use to enrich multiple person profiles simultaneously with comprehensive data from apollo's database.
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.
Bulk update account stage
Bulk updates the stage for specified existing apollo.io accounts, moving them to a valid new account stage.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Create an Apollo account
Creates a new account in apollo.io; a new record is created even if a similar account exists, and provided `owner id` or `account stage id` must be valid existing ids.
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.
Create Apollo contact
Creates a new contact in apollo.io; use `account id` to link to an organization and `contact stage id` for sales stage, noting that apollo does not perform automatic deduplication.
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.
Create Apollo deal
Creates a new sales opportunity (deal) in apollo.io; all provided ids (`owner id`, `account id`, `opportunity stage id`) must be valid existing apollo identifiers.
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.
Create Apollo Task
Creates a distinct apollo.io task for each contact id in contact ids, assigning them to user id; this action is not for free plan users and repeated calls create duplicate tasks.
Connect any two apps with Notis in the middle.
Notion and Apollo, 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 Apollo.