Keep new Notion leads ready for follow-up in Omnisend
Capture a new lead in Notion once and let Notis prepare the matching Omnisend contact automatically.
Trigger
New Page
Triggers when a new page is added to a Notion database.
Action
Create or Update Contact
Tool to create or update a contact in omnisend. use after collecting subscriber details.
Why this helps
Manually copying a lead into a marketing tool adds busywork and makes it easy to forget a promising prospect.
- Avoid retyping contact details across tools.
- Keep lead follow-up moving while you focus on conversations.
- Use one Notion lead record as the starting point.
Setup
Build it in a few focused steps.
- 1Connect Notion and Omnisend to Notis once through the portal.
- 2Create an automation in the portal or ask Notis conversationally for a new-lead sync.
- 3In one plain-language instruction, ask Notis to create or update an Omnisend contact from each new lead entry.
- 4Select the Notion New Page trigger for the lead database and choose a channel for run reports.
- 5Test with one real lead and confirm its contact appears correctly in Omnisend.
Questions about this workflow
Does this run for every new Notion page?
Choose the New Page trigger for the lead database so the automation responds to new entries there.
What does the prompt do?
It tells Notis to use the lead details available in Notion to create or update the matching Omnisend contact.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Omnisend. A trigger fires from one place; an action lands in another.
Notion triggers
Omnisend actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Batch
Tool to create a new batch operation for multiple items. use when you need to process many records asynchronously in one call, e.g., bulk contacts, products, orders, or events. use after preparing the items list to avoid rate limits.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create or Update Contact
Tool to create or update a contact in omnisend. use after collecting subscriber details.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Delete Product
Tool to remove a product from omnisend by its id. use when you need to delete a product and ensure it is no longer available in your catalog.
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.
Get Batches
Tool to retrieve a list of batch operations. use after initiating a batch job to monitor its progress and results.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get Batch Information
Tool to retrieve information about a specific batch by id. use after submitting a batch when you need a detailed status and counts.
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.
Get Batch Items
Tool to retrieve processed items of a specific batch by id. use when you need to inspect individual results of a batch operation after fetching batch details.
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.
Get Contact
Tool to retrieve details of a single contact by id. use when you already have a contactid and need the full profile.
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.
List Contacts
Tool to retrieve a paginated list of contacts with optional filtering. use when you need to fetch contacts in batches and handle cursor pagination.
Connect any two apps with Notis in the middle.
Notion and Omnisend, 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 Omnisend.