Skip to content
Notis

Connect Notion to Emailoctopus

When something happens in Notion, Notis takes the next step in Emailoctopus. Describe what you want in plain English, or start from one of the examples below.

When this happens · Trigger

Do this · Action

Examples

Ways Notis can move work from Notion to Emailoctopus

View example

Add new Notion leads to Emailoctopus

Create an Emailoctopus contact when a new lead page appears in Notion.

View example

Honor email opt-out updates from Notion

Unsubscribe a contact in Emailoctopus when a Notion record is updated to show an opt-out.

View example

Add newsletter signups from Notion

Create an Emailoctopus contact when a new Notion page records a newsletter signup.

View example

Capture event attendees mentioned in Notion comments

Add an attendee as an Emailoctopus contact when a Notion comment records their signup details.

View example

Capture client contacts from page comments

Add a client contact to Emailoctopus when relevant details are added to a specified Notion page or block.

View example

Add launch press contacts as launch notes change

Create an Emailoctopus contact when edits to a launch page add relevant press contact information.

View example

Capture contacts from campaign subpages

Add relevant contacts to Emailoctopus when a new campaign subpage is created in Notion.

View example

Apply contact preference updates from Notion

Unsubscribe an Emailoctopus contact when an updated Notion page records a clear preference change.

View example

Add newly qualified prospects to Emailoctopus

Create a contact when a Notion prospect record is updated to a qualified status.

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.

TriggerScheduled

Create Contact

This tool creates a new contact in emailoctopus. the tool will add a contact to a specified list with the provided information.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

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.

ActionInstant

All Page Events

Triggers when any Notion page is created or updated across the workspace.

TriggerPolling

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.

ActionInstant

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.

TriggerInstant

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.

ActionInstant

New Comment

Triggers when a new comment is added to a specified Notion block or page.

TriggerPolling

Get All Lists

This tool retrieves all the mailing lists associated with the emailoctopus account.

ActionInstant

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.

TriggerInstant

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.

ActionInstant

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.

TriggerInstant

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.

ActionInstant

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.

TriggerInstant
Trigger Types

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.

New Notion pageStripe chargeCalendar event

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.

Any HTTP POSTCustom backendIoT event
Works with
ZapierPipedream
Most used

Recurring triggers

Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.

Daily · 8:00HourlyWeekdays only
Coming soon

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.

Row insertedValue > limitQuery match
Why AI automation

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.

Classic automationAI automation
Cost
$ · pay per run
$$ · AI models per run
Reliability
Breaks on schema change
Adapts to format changes
Setup
Click 8 dropdowns
Describe it in English
Handles fuzzy
Hard-coded fields only
Reads intent, summarises
Human in loop
Bolted on
Built in · approval inbox
Maintenance
You own every break
Self-heals · we own it
Ease of use

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.

Notis

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:

TriggerRow added to "Q4 OKRs"
Condition✦Status = "Blocked"
AI step✦Summarise the blocker in plain English
ActionDM the row owner with summary
Timeout✦No reply in 24h → ping you
Observability

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

All12Manager5Telegram1Messages0Whatsapp2Email4Slack8

Migrate background jobs to a durable queue You can cancel it through Stripe

3 days

Notis v3 release update This one’s v3: Notis Manager (desktop app with …

8 days

Add multi-tenant RBAC User initiates a voice call

13 days

Draft pricing v (tiers, limits, overages) and sanity-check margins

2 weeks

Verify analytics events for new features That’s a really interesting automat…

1 month

Everything 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.

Related pairs

More ways to connect Notion and Emailoctopus

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.