Welcome new customers from a Notion onboarding list
Start a Customer.io welcome broadcast when a new customer onboarding entry is added to Notion.
When something happens in Notion, Notis takes the next step in Customer.io. Describe what you want in plain English, or start from one of the examples below.
When this happens · Trigger
Fires when a new comment is created in the accessible workspace.
Do this · Action
Permanently deletes a customer profile and prevents it from being added again; this action is irreversible.
Start a Customer.io welcome broadcast when a new customer onboarding entry is added to Notion.
Use changes to a Notion trial record to trigger a Customer.io reminder broadcast for an upcoming trial end.
When a new Notion comment records a customer support update, trigger a prepared Customer.io broadcast with the appropriate update.
Trigger a prepared Customer.io launch broadcast when a new Notion page records a customer-facing release.
Trigger a prepared Customer.io event confirmation broadcast when Notion event details are updated and ready to share.
When a resource subpage is added under a Notion resource hub, trigger a prepared Customer.io announcement broadcast.
Use a relevant Notion customer milestone update to trigger a prepared Customer.io education broadcast.
When a feedback item is added to a Notion database, trigger a prepared Customer.io thank-you broadcast.
Use a Notion risk-status change to trigger a prepared Customer.io retention broadcast for the appropriate customer audience.
Notis builds workflows that link Notion to Customer.io. A trigger fires from one place; an action lands in another.
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Permanently deletes a customer profile and prevents it from being added again; this action is irreversible.
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Adds a person to a Customer.io group and can include group traits.
Fires when a new comment is created in the accessible workspace.
Retrieves the configured integrations in your Customer.io workspace.
Fires when a new database container is created.
Creates an alias to merge two Customer.io profiles.
Fires when a new data source is created in the workspace.
Updates and versions a linked Design Studio email, then publishes it live in its workflow for all languages.
Fires when a data source’s columns are added, removed, or renamed.
Retrieves messages sent from your workspace and their delivery metrics.
Fires when the body content of an accessible page is updated.
Retrieves details about a specific segment.
Fires when a new page is created in the accessible workspace.
Creates an empty manual segment in Customer.io.
A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a schedule (recurring or one-time), and a change in one of your Notis databases.
Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,600+ apps can start a workflow.
A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.
Run a workflow on the clock, on a recurring schedule or once at a set date and time. Daily standups, hourly syncs, a one-off launch reminder: the workhorse of Notis.
Fire when a row in one of your Notis databases is added or edited, with optional filters on its properties. New lead added, status changed, value crosses a limit.
Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.
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:
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.
Automations
Inbox
Migrate background jobs to a durable queue You can cancel it through Stripe
3 daysNotis v3 release update This one’s v3: Notis Manager (desktop app with …
8 daysAdd multi-tenant RBAC User initiates a voice call
13 daysDraft pricing v (tiers, limits, overages) and sanity-check margins
2 weeksVerify analytics events for new features That’s a really interesting automat…
1 monthWhatever starts the workflow, the platform underneath is the same: a thinking brain, full visibility, and you in control.
Every step can include an LLM call: summarise, classify, extract, rewrite.
Every run, every step, every input, all replay-able from Mission Control.
Pause for approval. Notis pings you in chat with one-tap approve.
When an API changes shape, Notis adapts the parser. Less midnight fire-fighting.
Notion and Customer.io, or any other combination from 1,600+ integrations.
When this happens · Trigger
Do this · Action
7-day trial of any paid plan, with $20 of usage included.
No card. Works with personal or business Customer.io.