Connect Notion to Emelia
When something happens in Notion, Notis takes the next step in Emelia. Describe what you want in plain English, or start from one of the examples below.
When this happens · Trigger
Do this · Action
Ways Notis can move work from Notion to Emelia
Enroll ready prospects in an Emelia email campaign
When a prospect is added to a Notion database, have Notis review the available details and add suitable contacts to the right Emelia email campaign.
Find an email for a prospect marked ready
When a Notion prospect's status changes to ready for enrichment, start an Emelia email-finding job using the person's name and company details.
Verify prospect emails when records are approved
When an approved Notion prospect record is updated, ask Emelia to start verifying the email address before the contact enters active outreach.
Blacklist contacts flagged for no further email
When a comment on a designated Notion page explicitly records an email opt-out, have Notis identify the address and add it to Emelia's blacklist.
Remove withdrawn prospects from an email campaign
When a Notion prospect is marked withdrawn or disqualified, have Notis remove that person from the specified Emelia email campaign after confirming the match.
Find a phone number for selected prospects
When a new Notion prospect record includes an email and is marked for phone research, start an Emelia phone-finding job.
Launch LinkedIn outreach for an approved segment
When a Notion campaign brief is marked approved, have Notis create the corresponding LinkedIn outreach campaign in Emelia using the brief's requirements.
Create an email campaign from an approved brief
When an email campaign brief in Notion reaches approved status, ask Emelia to create the named campaign so setup does not get stranded after review.
Find contact emails from updated research notes
When a designated Notion research page is updated with a person's name and company, start an Emelia email-finding job for that contact.
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.
Four ways to start an automation.
A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a recurring schedule, and soon, your own database.
Integration triggers
Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,000+ apps can start a workflow.
Webhook triggers
A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.
Recurring triggers
Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.
Database triggers
Watch a row, query, or threshold in your own database and fire the moment the data changes. Row inserted, value crosses a limit, query starts matching.
Classic automation breaks. AI adapts.
Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.
Describe it. Notis builds it.
Skip the visual builder. Tell Notis what you want, in plain English. It writes the workflow, you review and deploy.
You · in the Notis Builder
NEW“When a row gets added to the Q4 OKRs Notion database and the status is Blocked, send a Telegram message to the owner with a summary of what's blocking, and ping me if there's no reply within 24 hours.”
Notis built this automation:
Watch every run.
Notis Desktop is Mission Control for your AI automations. See every run, replay, edit, or rewind. Set approval gates so Notis pauses before destructive actions.
- Full run history with inputs, outputs and traces
- Replay any run with edited inputs
- Approval inbox, confirm via chat in one tap
- Audit logs for compliance teams
Automations
Inbox
Migrate background jobs to a durable queue You can cancel it through Stripe
3 daysNotis v3 release update This one’s v3: Notis Manager (desktop app with …
8 daysAdd multi-tenant RBAC User initiates a voice call
13 daysDraft pricing v (tiers, limits, overages) and sanity-check margins
2 weeksVerify analytics events for new features That’s a really interesting automat…
1 monthEverything in the box.
Whatever starts the workflow, the platform underneath is the same: a thinking brain, full visibility, and you in control.
AI in the middle
Every step can include an LLM call: summarise, classify, extract, rewrite.
Full observability
Every run, every step, every input, all replay-able from Mission Control.
Human in the loop
Pause for approval. Notis pings you in chat with one-tap approve.
Self-healing
When an API changes shape, Notis adapts the parser. Less midnight fire-fighting.
More ways to connect Notion and Emelia
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.