Connect Notion to Nocrm io
When something happens in Notion, Notis takes the next step in Nocrm io. Describe what you want in plain English, or start from one of the examples below.
When this happens · Trigger
Do this · Action
Ways Notis can move work from Notion to Nocrm io
Turn Notion prospects into Nocrm.io leads
Create a Nocrm.io lead when a new prospect is added to your Notion database, so promising conversations reach your pipeline without duplicate data entry.
Set Nocrm.io leads to standby from Notion follow-up updates
When a Notion lead record changes to show a planned follow-up, have Notis set the corresponding Nocrm.io lead to standby so it stays organized for later.
Append Notion call notes to a Nocrm.io lead
When you update a Notion page with fresh conversation notes, have Notis append the useful context to the matching Nocrm.io lead's description.
Add Notion prospect comments to Nocrm.io context
Capture a useful comment on a Notion prospect page in the corresponding Nocrm.io lead description, so a decision or reminder does not stay buried in a thread.
Capture new referral pages as Nocrm.io leads
When a referral page is created under your designated Notion page, ask Notis to create the corresponding Nocrm.io lead and preserve the referral source in context.
Tag priority prospects in Nocrm.io from Notion
When a new prospect record in Notion signals high priority, have Notis add a clear priority tag to the matching Nocrm.io lead.
Assign Nocrm.io leads from a Notion ownership update
When ownership changes on a Notion prospect record, have Notis assign the corresponding Nocrm.io lead to the intended teammate.
Cancel Nocrm.io leads when Notion confirms closure
When a Notion prospect page records a confirmed no-go decision, have Notis change the corresponding Nocrm.io lead to cancelled to keep the pipeline current.
Put a Nocrm.io lead on standby from a follow-up comment
When a comment on a designated Notion prospect page records that the next contact should wait, have Notis set the matching Nocrm.io lead to standby.
Supported Triggers and Actions
Notis builds workflows that link Notion to Nocrm io. A trigger fires from one place; an action lands in another.
Notion triggers
Nocrm io actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add a tag to a lead
Tool to add a tag to a lead. use when you need to assign one or more tags to a specified lead via nocrm.io.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Append to lead's description
Tool to append text to the lead's description. use when you need to add context incrementally without overwriting. example: append 'left voicemail' to lead 1234.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Assign Lead to User
Tool to assign a lead to a user. use when reassigning a lead to the correct owner to trigger assignment notification.
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.
Change Lead Status to Cancelled
Tool to change a lead's status to 'cancelled'. use after confirming no further follow-up is needed and the lead should be marked as cancelled.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Change lead status standby
Tool to change a lead's status to 'standby'. use when scheduling follow-up after determining the next contact should occur in a set number of days.
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.
Create Lead
Tool to create a new lead. use when adding a fresh prospect to your pipeline via nocrm.io. example: create a lead titled 'acme corp' assigned to a user.
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.
Delete Lead
Tool to delete a lead. use when you need to permanently remove a specific lead after verifying it is no longer needed.
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.
Duplicate Lead
Tool to duplicate a lead. use when cloning an existing lead into a new step without overwriting original.
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.
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.
Recurring triggers
Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.
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.
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.
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:
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
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 monthEverything 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.
More ways to connect Notion and Nocrm io
Connect any two apps with Notis in the middle.
Notion and Nocrm io, 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 Nocrm io.