Connect Notion to Userlist

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

When this happens · Trigger

Do this · Action

Build an automation Browse examples

Examples

Ways Notis can move work from Notion to Userlist

View example

Sync new B2B customers from Notion to Userlist

Automatically create company records in Userlist when you add a new customer to Notion, eliminating manual entry and keeping your segments fresh.

View example

Update customer tier in Userlist when Notion status changes

Keep customer tiers in sync between Notion and Userlist so email segments reflect current status and customers get the right messaging.

View example

Remove inactive companies from Userlist when marked in Notion

Automatically archive or remove companies from Userlist when you mark them as inactive or churned in Notion, keeping your email lists clean.

View example

Sync customer location and region from Notion to Userlist

Automatically update customer location and timezone data in Userlist when changed in Notion, enabling geo-targeted email campaigns.

View example

Sync customer acquisition channel from Notion to Userlist segments

Automatically sync how each customer was acquired from Notion to Userlist, enabling channel-specific email campaigns and attribution.

View example

Sync customer contacts to accounts when added as subpages in Notion

When you add a new contact as a subpage under a customer in Notion, Notis automatically links them to that company in Userlist.

View example

Sync customer contract and renewal dates from Notion to Userlist

Automatically sync contract end dates and renewal information from Notion to Userlist so you never miss a renewal opportunity.

View example

Weekly sync of all customer accounts from Notion to Userlist

Run a scheduled weekly sync to ensure all customer data in Notion stays current in Userlist without relying on manual updates.

View example

Sync customer company size to Userlist for firmographic segmentation

Automatically update company size in Userlist when changed in Notion, enabling email campaigns targeted by organization scale.

Supported Triggers and Actions

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

Notion triggers

Userlist actions

All Page Events

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

TriggerPolling

Delete Company from Userlist

Tool to delete a company from userlist. use when you need to remove a company by its unique identifier after verifying it.

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

Push User-Company Relationship

Tool to create or update a relationship between a user and a company in userlist. use after confirming valid user and company identifiers.

ActionInstant

New Comment

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

TriggerPolling

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

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

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

New Page

Triggers when a new page is added to a Notion database.

TriggerPolling

Page Added to Page

Fires when a new subpage (a `child_page` type block) is added under a specified parent Notion page.

TriggerPolling

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.

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.