Enrich new Notion prospects automatically
Add a prospect to Notion and let Dropcontact handle the first pass at finding a verified business email and company details.
Trigger
New Page
Triggers when a new page is added to a Notion database.
Action
Batch Enrich Contacts
Tool to batch enrich contacts with email validation and company info. use after gathering up to 250 contacts.
Why this helps
Prospect research can interrupt focused work and leave new leads waiting in a queue.
- Start prospect research as soon as a new record arrives.
- Reduce the tab switching involved in looking up business contact details.
- Keep outreach preparation moving while you focus elsewhere.
Setup
Build it in a few focused steps.
- 1Connect Notion and Dropcontact to Notis once in the portal.
- 2Ask Notis to create an automation that enriches each new prospect record in Dropcontact and reports the result.
- 3Select the Notion New Page trigger for the relevant database.
- 4Choose where Notis should send run reports, then test with one real prospect record.
Questions about this workflow
Does this run for any new Notion page?
Choose the New Page trigger for the prospect database when creating the automation, and describe in the prompt which new records should be enriched.
What should a prospect record include?
Include the person's name and available company context so Dropcontact has useful information to work with.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Dropcontact. A trigger fires from one place; an action lands in another.
Notion triggers
Dropcontact actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Batch Enrich Contacts
Tool to batch enrich contacts with email validation and company info. use after gathering up to 250 contacts.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
List Webhook Subscriptions
Tool to list webhook subscriptions. use when you need to inspect your configured webhooks.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Retrieve Enrichment Results
Tool to retrieve enrichment results. use after submitting enrichment requests and use when you need to fetch the completed enrichment data by request 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.
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 Dropcontact, 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 Dropcontact.