Keep Moneybird contact details aligned with Notion
Fix a client detail in your workspace and let Notis carry the correction to Moneybird.
Trigger
Page Properties Updated
Triggers when properties of a Notion page are 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 property change in the workspace the integration has access to. Adding a column to a data source fires this trigger once per existing row. Customers can branch on `data.updated_properties` (array of property IDs) to filter downstream.
Action
Update Contact
Tool to update a contact. use when you need to modify existing contact details by id. only provided fields will be changed.
Why this helps
Contact information gets inconsistent when a correction is made in one tool but not the other.
- Propagate approved contact corrections to accounting.
- Reduce uncertainty about which app has the current email or address.
- Keep routine client record maintenance in one familiar place.
Setup
Build it in a few focused steps.
- 1Connect Notion and Moneybird to Notis once through the portal.
- 2Create an automation with a plain-language instruction to update the matching Moneybird contact when a client record changes.
- 3Pick Notion Page Properties Updated for the client data source and choose a report channel.
- 4Test with one client correction and verify the matching Moneybird contact.
Questions about this workflow
How does Notis identify the contact to update?
Keep a stable Moneybird contact ID or another unambiguous identifier on the Notion client record and mention it in the instruction.
Can this update only changed contact details?
Ask Notis to use the corrected information in the record and change only the relevant details.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Moneybird. A trigger fires from one place; an action lands in another.
Notion triggers
Moneybird actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add Note to Contact
Tool to add a note or to-do to a contact. use when you need to record a comment or assign a task to a contact.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Archive Contact
Tool to archive a contact. use when a contact is no longer needed and should be hidden permanently.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Create Moneybird Contact
Tool to create a new contact in moneybird. use after you have an administration id and need to onboard a new company/person. provide either company name or both firstname and lastname.
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 Contact Person
Tool to create a new contact person. use when you have the contact id and need to add a person after confirming their firstname and lastname.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Create Sales Invoice
Tool to create a new sales invoice. use when you need to bill a contact with specified line items.
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.
Delete Contact
Tool to delete a contact. use after confirming that contact should be removed.
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 Contact Note
Tool to delete a note from a contact. use when a note is no longer needed and should be removed permanently.
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.
Delete Contact Person
Tool to delete a contact person from a contact. use after confirming the administration id, contact id, and contact person id.
Connect any two apps with Notis in the middle.
Notion and Moneybird, 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 Moneybird.