Refresh Apollo contact details from an updated Notion record
Keep contact research moving when you update a person's details in Notion. Apollo can enrich the identity information already on the page.
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
Apollo People Enrichment
Enrich one person with verified contact and profile data — email, profile, and optionally a mobile phone number — from an email, name, LinkedIn URL, or Apollo id.
Why this helps
A name or profile link noted during a busy day often stays incomplete until someone remembers to research it later.
- Turn an updated contact note into a timely enrichment lookup.
- Reduce manual searches across separate tools.
- Make profile and verified contact information easier to review.
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 to enrich a person in Apollo when a Notion contact record changes.
- 3Select the Notion Page Properties Updated trigger for the contact database.
- 4Choose a run-report channel and test with one real contact record.
Questions about this workflow
What identity information helps Apollo find the person?
A contact record may contain an email, name, LinkedIn URL, or Apollo id. Notis can use available identity context for the enrichment request.
Will every property edit cause a lookup?
The selected trigger fires when page properties are updated. Keep the automation scoped to the appropriate database if available.
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.
Apollo People Enrichment
Enrich one person with verified contact and profile data — email, profile, and optionally a mobile phone number — from an email, name, LinkedIn URL, or Apollo id.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Apollo Organization Job Postings
Retrieve a company's active job postings by its Apollo organization id.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Apollo Get Complete Organization Info
Get the complete record for a company by its Apollo organization id.
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.
Apollo Organization Search
Find companies by headcount, location, revenue, funding, keywords, and technology.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Apollo News Articles Search
Search news articles about companies by organization, category, and date.
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.
Apollo Get Complete Person Info
Get the complete record for a person by their Apollo person 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 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.