Move approved invoice details from Notion into Chaser
Capture invoice details once in Notion, then let Notis create the corresponding Chaser invoice when the record is ready.
Trigger
New Page
Triggers when a new page is added to a Notion database.
Action
Create Invoice
Tool to create a new invoice record in the organization. use after ensuring the customer exists in chaser.
Why this helps
Re-entering invoice details across tools creates friction and makes it easier to overlook an approved bill.
- Avoid retyping approved invoice details into Chaser.
- Use a clear approval signal before creating an invoice.
- Keep invoice intake in the workspace where the team already works.
Setup
Build it in a few focused steps.
- 1Connect Notion and Chaser to Notis once through the portal.
- 2Create an automation in the portal or ask Notis conversationally to create one.
- 3Write one plain-language instruction to create a Chaser invoice from each new approved Notion invoice record, using its available details and checking that the customer exists.
- 4Choose the Notion New Page trigger and a channel for run reports.
- 5Test with one approved invoice record and confirm the result in Chaser.
Questions about this workflow
Does every new Notion page become an invoice?
The instruction can tell Notis to act only on new pages that represent approved invoice records and to skip incomplete or unrelated pages.
What if the customer is not in Chaser yet?
The automation should check for a matching customer first and report that it needs attention rather than creating an invoice without a customer.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Chaser. A trigger fires from one place; an action lands in another.
Notion triggers
Chaser actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Invoice
Tool to create a new invoice record in the organization. use after ensuring the customer exists in chaser.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Credit Notes
Tool to retrieve a list of credit notes. use after authenticating this detail.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get Customer by ID
Tool to retrieve details for a specific customer by their external (source system) id. use after obtaining the external id when you need specific customer information.
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.
Get Customers
Tool to retrieve a list of all customers associated with the organization. use when you need to display or process complete customer contact and status information.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get Organization
Tool to retrieve information about the connected organizations. use when you need organization ids, currency, timezone, or legal details before other operations.
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 Credit Note
Tool to create a new credit note record in the organization. use after confirming invoice adjustments.
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 Customer
Tool to create a new customer record in chaser. use after obtaining basic auth credentials.
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.
Update Customer
Tool to update an existing customer's information using their unique externalid. use after confirming the customer's externalid. e.g., "update contactemailaddress for externalid cust abc123."
Connect any two apps with Notis in the middle.
Notion and Chaser, 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 Chaser.