Check recent email sends as campaign work begins
A new campaign subpage can prompt Notis to bring recent Emailoctopus sends into the conversation.
Trigger
Page Added to Page
Fires when a new subpage (a `child_page` type block) is added under a specified parent Notion page.
Action
Get Recent Campaigns
This tool retrieves a list of recent campaigns from the emailoctopus account. it uses the get endpoint at https://emailoctopus.com/api/1.6/campaigns and allows filtering by parameters like limit and page.
Why this helps
Campaign context is easy to lose between a planning page and the email tool that holds the send history.
- Make recent campaign history available at the start of a workstream.
- Spend less time switching between planning and sending tools.
Setup
Build it in a few focused steps.
- 1Connect Notion and Emailoctopus to Notis once in the portal.
- 2Create an automation or ask Notis to review recent Emailoctopus sends for new campaign subpages.
- 3Write one plain-language prompt explaining the relevant parent page and how to summarize retrieved campaign information.
- 4Choose the Notion Page Added to Page trigger and select the campaign parent page.
- 5Test by adding one real campaign subpage and check the run report.
Questions about this workflow
Can this create a new campaign?
No. The available action retrieves recent campaign information for review.
Will it run for unrelated subpages?
Choose the campaign parent page and describe the intended subpages in the prompt.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Emailoctopus. A trigger fires from one place; an action lands in another.
Notion triggers
Emailoctopus actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Contact
This tool creates a new contact in emailoctopus. the tool will add a contact to a specified list with the provided information.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create List
This tool creates a new mailing list in emailoctopus. it allows users to create a new list where contacts can be added and managed.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Delete Contact
This tool allows you to delete a contact from a specified list in emailoctopus. it uses the delete /api/1.6/lists/{list id}/contacts/{contact id} endpoint to permanently remove the contact from the list. this action is irreversible and is essential for list management and data privacy compliance.
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 List
This tool allows you to delete an existing mailing list from your emailoctopus account. once a list is deleted, it cannot be recovered, and all contacts within the list will be permanently removed. note: lists can only be deleted if no contacts within the list have received an email in the last 7 days.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get All Lists
This tool retrieves all the mailing lists associated with the emailoctopus account.
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 Recent Campaigns
This tool retrieves a list of recent campaigns from the emailoctopus account. it uses the get endpoint at https://emailoctopus.com/api/1.6/campaigns and allows filtering by parameters like limit and page.
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.
Unsubscribe Contact
This tool unsubscribes a contact from an emailoctopus list. it takes an email address as input, retrieves the contact's details using the find contact functionality, and unsubscribes the contact from the associated list.
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.
Connect any two apps with Notis in the middle.
Notion and Emailoctopus, 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 Emailoctopus.