Skip to content
Notis

Connect Notion to Esputnik

When something happens in Notion, Notis takes the next step in Esputnik. 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 Esputnik

View example

Add campaign contacts from Notion

When a new campaign contact is added to a Notion database, ask Notis to add or update that contact in eSputnik in a single bulk import.

View example

Refresh eSputnik contact details from Notion

When contact properties change in a Notion database, ask Notis to update the corresponding eSputnik contact details from the revised entry.

View example

Remove eSputnik contacts on request

When a Notion contact record is updated with a clear removal request, ask Notis to delete the matching eSputnik contact by external customer ID.

View example

Delete eSputnik contact by Yespo ID

When a Notion contact record is updated with a confirmed deletion request and Yespo ID, ask Notis to delete that contact in eSputnik.

View example

Check eSputnik subscriptions for a contact

When a Notion contact is flagged for a subscription check, ask Notis to retrieve that contact's eSputnik subscription categories for review.

View example

Review eSputnik broadcasts from a Notion task

When a new Notion task requests a broadcast review, ask Notis to retrieve the current eSputnik broadcasts for review.

View example

Check eSputnik balance before campaign work

When a Notion campaign task is updated to request a budget check, ask Notis to retrieve the current eSputnik organization balance.

View example

Retrieve eSputnik billing history for review

When a Notion finance task is updated to request a billing review, ask Notis to retrieve eSputnik organization billing history.

View example

Refresh audience contacts after schema changes

When a Notion contact data source schema changes, ask Notis to bulk add or update contacts from the current source for eSputnik processing.

Supported Triggers and Actions

Notis builds workflows that link Notion to Esputnik. A trigger fires from one place; an action lands in another.

Notion triggers

Esputnik actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

ADD_DOMAIN

Tool to register a domain for web tracking or widgets. Use after confirming the site ID.

ActionInstant

Webhook trigger

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

TriggerInstant

Add Orders Bulk

Tool to transfer orders in bulk to eSputnik. Use when you need to import up to 1000 orders at once.

ActionInstant

All Page Events

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

TriggerPolling

Bulk Add or Update Contacts

Tool to bulk add or update up to 3000 contacts asynchronously. Use when you have a batch of contacts to import or update in one request and need a single session ID for tracking.

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

Change Token Activity

Action to change (activate/deactivate) the activity state of a mobile push token. Endpoint: PUT /api/v1/contact/token/activated/{app_uuid}/{token_id} Body: { "active": boolean } Response: { "active": boolean }

ActionInstant

New Comment

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

TriggerPolling

Delete Contact

Tool to delete a contact by its Yespo ID. Use when you need to remove a contact with no pending interactions.

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

Delete Contact by External ID

Tool to delete a contact by externalCustomerId.

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

Delete SMS Message

Tool to delete a base SMS message by ID. Use when you need to remove an SMS template before sending. Example: "Delete SMS message with ID 123"

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

Get App Inbox Message

Tool to retrieve an App Inbox message by ID. Use when you need to fetch its content, metadata, and translations before sending or editing.

ActionInstant
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 Esputnik

Connect any two apps with Notis in the middle.

Notion and Esputnik, 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 Esputnik.