Make the next customer touchpoint easier to pick up
Update your follow-up notes in Notion and let Notis refresh the corresponding Centralstationcrm person.
Trigger
Page Content Updated
Triggers when the body content of a Notion page is updated. Customer optionally scopes with at most one of: - data_source_id: any row in this data source - page_id: this specific page - parent_page_id: any page whose immediate parent is this page With none set, fires for any page content edit in the workspace the integration has access to. Notion aggregates content edits within a short window (~60s typical).
Action
Update Person
Tool to update an existing person by id. use after retrieving the person's current details when you need to modify one or more fields.
Why this helps
After a pause or interruption, the next useful step can be hard to recover if context is split between tools.
- Keep customer context connected to the CRM record you revisit.
- Reduce the work of reconstructing a next step after interruptions.
- Make handoffs and resumed work less dependent on memory.
Setup
Build it in a few focused steps.
- 1Connect Notion and Centralstationcrm to Notis once through the portal.
- 2Create an automation or ask Notis to update the matching Centralstationcrm person when follow-up notes are edited in Notion.
- 3Pick Page Content Updated and identify the follow-up notes location and the intended contact in your instruction.
- 4Choose a channel for run reports and test with one real customer note.
Questions about this workflow
What context can Notis use?
It can use the details available in the Notion page and the information needed to identify the matching CRM person.
Should every note edit update the person?
Describe which follow-up details matter and how Notis should treat edits to the page.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Centralstationcrm. A trigger fires from one place; an action lands in another.
Notion triggers
Centralstationcrm actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Check Connection
Tool to verify the connection status of the centralstationcrm api key. use when validating credentials before making other api calls.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Count People
Tool to retrieve the total number of people in the account. use when you need the current total number of contacts in your centralstationcrm account. example: "how many contacts exist in my account?"
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Create Company
Tool to create a new company record. use when you need to add an organization to your crm before linking it to contacts or deals.
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.
Create Deal
Tool to create a new deal record. use when needing to log a sales opportunity after grouping contacts or companies.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Create Person
Tool to create a new person record. use when you need to add a person to your crm before linking them to other records.
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 Person Address
Tool to create a new address for a specific person. use when you need to add or update postal details after confirming person id.
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.
Create Person Assistant
Tool to create a new assistant (assi) entry for a specific person. use after confirming the person id when you need to manage assistant contacts.
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.
Create Person Avatar
Tool to create a new avatar for a specific person. use when you need to attach a base64-encoded image file after confirming the person's id.
Connect any two apps with Notis in the middle.
Notion and Centralstationcrm, 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 Centralstationcrm.