Move sales handoffs into Nocrm.io without losing momentum
When a handoff gets its own Notion subpage, Notis can create a lead so the next conversation has a home.
Trigger
Page Added to Page
Fires when a new subpage (a `child_page` type block) is added under a specified parent Notion page.
Action
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.
Why this helps
A handoff can stall between the person who captured the opportunity and the person expected to follow up.
- Give newly handed-off opportunities a clear pipeline record.
- Reduce manual re-entry during busy transitions.
- Make it easier for the next owner to pick up the thread.
Setup
Build it in a few focused steps.
- 1Connect Notion and Nocrm.io to Notis once through the portal.
- 2Create the automation in the portal or ask Notis for it conversationally.
- 3Describe in one instruction how a new handoff subpage should become a Nocrm.io lead with its relevant context.
- 4Choose Page Added to Page for the handoff parent page, then select a channel for run reports.
- 5Test by creating one real handoff subpage and reviewing the resulting lead.
Questions about this workflow
Does this watch every subpage in Notion?
The trigger fires under a specified parent page. Choose the sales handoff page as that parent.
Can it retain what the handoff says?
Tell Notis in the plain-language instruction what details are useful for the new lead.
When this happens · Trigger
Do this · Action
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.
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.