Verify contact emails when Notion research is complete
Turn the point when research is ready into a consistent email verification step.
Trigger
Page Content Updated
Triggers when the body content of a Notion page is 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 page content edit in the workspace the integration has access to. Notion aggregates content edits within a short window (~60s typical).
Action
Initiate Email Verification Job
Tool to initiate an asynchronous email verification job."
Why this helps
Found addresses can go straight into outreach if verification is left to memory.
- Add a repeatable check after research is complete.
- Keep the verification step attached to the contact context.
- Reduce manual reminders before outreach.
Setup
Build it in a few focused steps.
- 1Connect Notion and Emelia to Notis once through the portal.
- 2Create an automation in the portal or ask Notis for this workflow in plain language.
- 3Describe the research-complete signal and instruct Notis to start verification for the identified email.
- 4Select Page Content Updated scoped to the contact page or relevant data source and choose a report channel.
- 5Test with one completed contact record and confirm Emelia starts verification.
Questions about this workflow
Will each content edit re-run verification?
Specify a distinct ready signal in the instruction so routine edits do not trigger unnecessary checks.
Can this also add the contact to a campaign?
This workflow starts verification only. Campaign enrollment is a separate action.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Emelia. A trigger fires from one place; an action lands in another.
Notion triggers
Emelia actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add Contact to Blacklist
Tool to add a contact to the email blacklist. use after confirming that no further emails should be sent to a specific address. example: 'add blocked user@example.com to blacklist.'
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Add Contact To Campaign
Tool to add a contact to an email campaign. use when you have collected subscriber details and want to enroll them in a campaign.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Create Campaign
Tool to create a new email campaign. use after you have finalized the campaign name.
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.
Create LinkedIn Campaign
Tool to create a new linkedin campaign. use when you need to launch a linkedin outreach sequence.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Create Webhook
Tool to create a new webhook for campaign events. use when you need to subscribe to activity updates after determining the campaign id and desired events.
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.
Delete Contact From Campaign
Tool to remove a contact from an email campaign. use when you need to revoke a contact's subscription from a specific campaign. note: this operation is irreversible.
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.
Delete Contact From LinkedIn Campaign
Tool to delete a contact from a linkedin campaign. use when you need to remove a contact by campaign id and contact url. call after confirming the contact exists in the campaign.
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.
Delete Webhook
Tool to delete a specific webhook. use when you need to remove an existing webhook by url after identifying the campaign.
Connect any two apps with Notis in the middle.
Notion and Emelia, 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 Emelia.