Move qualified opportunities forward automatically
When your Notion pipeline says a prospect is qualified, Lemlist can reflect that decision immediately.
Trigger
New Page
Triggers when a new page is added to a Notion database.
Action
Mark Lead As Interested In Campaign
Tool to mark a lead as interested in a specific campaign. use after confirming the lead's positive engagement in that campaign.
Why this helps
A founder makes a clear qualification decision in Notion, then forgets to update the outreach system.
- Keep qualification decisions visible in Lemlist.
- Remove a repetitive status-update task.
- Help outreach follow the same priority signal as your pipeline.
Setup
Build it in a few focused steps.
- 1Connect Notion and Lemlist to Notis once through the portal.
- 2Create an automation in the portal or ask Notis for it in plain language.
- 3Tell Notis to mark the matching Lemlist lead as interested in the campaign when a new qualified opportunity is added to Notion.
- 4Pick the new page trigger, choose a reporting channel, and test with one qualified opportunity.
Questions about this workflow
How does Notis know which campaign to use?
State the campaign rule in the plain-language instruction, such as using the campaign named in the Notion record.
Will this send a new email?
No. It updates the Lemlist lead status to interested.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Lemlist. A trigger fires from one place; an action lands in another.
Notion triggers
Lemlist actions
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Delete Schedule
Tool to delete a specific schedule by scheduleid. use when you need to remove a schedule permanently after confirming its 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.
Delete Unsubscribed Email
Tool to delete an email from the unsubscribed list. use when restoring a subscriber who has opted back in and you need to remove them from the suppressed contacts.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Unsubscribe Lead From Campaign
Tool to unsubscribe a lead from a campaign. use when you need to stop further outreach by removing a lead from the specified campaign.
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 All Webhooks
Tool to retrieve the list of all webhooks configured for the team. use when you need to sync or audit active webhooks.
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 Campaign By ID
Tool to retrieve a specific campaign by campaignid. use when you need detailed campaign information by id.
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.
Start Campaign Export
Tool to start an asynchronous export of all campaign statistics (csv). use when you need to initiate a csv export for a given campaign and track its progress.
New Page
Triggers when a new page is added to a Notion database.
Get Campaign Export Status
Tool to check the status of an asynchronous campaign export. use after starting an export to poll until done or error.
Page Added to Page
Fires when a new subpage (a `child_page` type block) is added under a specified parent Notion page.
Get Campaign Sequences
Tool to retrieve a list of all sequences for a campaign with steps and conditions. use after fetching campaign to inspect its nested sequences and branching rules.
Connect any two apps with Notis in the middle.
Not just Notion and Lemlist. Any 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 Lemlist.