Turn Notion Signup Records into Email Contacts
Keep new subscribers moving into the right Benchmark email list as soon as their signup is recorded in Notion.
Trigger
New Page
Triggers when a new page is added to a Notion database.
Action
Add Contact to List
Tool to add a new contact to a specific list. use after verifying the list id exists.
Why this helps
Copying signup details between tools is easy to postpone, leaving new subscribers waiting or forgotten.
- Reduces manual copying after a signup is recorded.
- Keeps subscriber intake in one repeatable flow.
- Skips records that do not contain a usable email address.
Setup
Build it in a few focused steps.
- 1Connect Notion and Benchmark email to Notis once in the portal.
- 2Create an automation in the portal or ask Notis conversationally to add new Notion signup records to a Benchmark email list.
- 3Choose the Notion New Page trigger for the signup database.
- 4Choose where Notis should report runs, then test with one real signup record.
Questions about this workflow
Does this add every new Notion page as a contact?
The prompt should limit the workflow to signup records and ask Notis to confirm a usable email address before adding a contact.
Can I use a specific Benchmark email list?
Yes. Name the intended list in the plain-language instruction so Notis can use it for qualifying signups.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Benchmark email. A trigger fires from one place; an action lands in another.
Notion triggers
Benchmark email actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Delete Contact From List
Tool to delete a contact from a specific list by contactid. use when you have list and contact ids. example: "delete contact 2040826674 from list 15257899"
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete Contact List
Tool to delete a contact list. use after confirming that the list is no longer in use.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Delete Email Campaign
Tool to delete an email campaign. use when removing a campaign by its id. use after confirming the campaign id is correct.
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 Linked Agency Account
Tool to delete a linked agency account. use when revoking a linked agency account by its id. use after confirming the account id is correct.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Delete Webhook
Tool to delete a webhook from a contact list by its id. use when removing obsolete or invalid webhooks after confirming list and webhook details.
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 Confirmed Emails
Tool to retrieve all confirmed email addresses for the client account. use after user completes email confirmation flows to fetch final list.
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 Client Account Settings
Tool to get client account settings such as company, language, timezone, and sender info. use when you need to fetch account configuration before sending campaigns.
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.
Get client details
Tool to get client details including profile data, contact count, and plan information. use when verifying account profile and limits.
Connect any two apps with Notis in the middle.
Notion and Benchmark email, 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 Benchmark email.