Check for an existing Moneybird contact before onboarding
Give client setup a quick duplicate check before a second record gets created.
Trigger
Page Created
Triggers when a new Notion page is created. Customer optionally scopes with at most one of: - data_source_id: new row in this data source - parent_page_id: new sub-page under this page (immediate parent only) With neither set, fires for any new page in the workspace the integration has access to. Notion sends ~60s aggregation latency on most events.
Action
Filter Contacts
Tool to filter contacts. use when you need to retrieve contacts matching specific criteria like created after or first name.
Why this helps
Starting an onboarding record without checking accounting can create duplicate contacts and more cleanup.
- Add a check before creating another client contact.
- Reduce duplicate record cleanup.
- Keep onboarding decisions informed by existing accounting records.
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 search Moneybird contacts for a likely match to each new Notion client candidate and report the result.
- 3Pick Notion Page Created for the client candidate database and choose a report channel.
- 4Test with one known client and one new client candidate.
Questions about this workflow
Does this create a contact when none is found?
This workflow searches for a match and reports the result. Add a separate contact-creation instruction only if that is the intended next step.
What makes a useful match?
Include enough identifying information, such as a company name or full person name, and ask Notis to report uncertain matches.
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.