Create a Chaser invoice from an approved Notion record
When an invoice record is added to Notion, have Notis check that it is approved and complete before creating the matching Chaser invoice.
When something happens in Notion, Notis takes the next step in Chaser. Describe what you want in plain English, or start from one of the examples below.
When this happens · Trigger
Fires when a new comment is created in the accessible workspace.
Do this · Action
Creates a new invoice record in the organization.
When an invoice record is added to Notion, have Notis check that it is approved and complete before creating the matching Chaser invoice.
When an invoice record's properties change in Notion, have Notis update the matching Chaser invoice when the change is an intentional status update.
When a new client intake page appears in Notion, have Notis create a Chaser customer if the details are complete and no matching customer exists.
When a client record's contact properties change in Notion, have Notis update the matching Chaser customer using the confirmed customer identifier.
When a new Notion comment confirms that a tracked invoice has been paid, have Notis update the matching Chaser invoice after checking the invoice reference.
When the body of an invoice page is updated with a clear dispute note, have Notis update the corresponding Chaser invoice for review.
When a new credit note request is added to Notion, have Notis create a Chaser credit note only after the adjustment is approved and tied to an existing invoice.
When a Notion adjustment record's properties change to approved, have Notis create the corresponding Chaser credit note after checking the invoice reference.
When a new renewal billing record is created in Notion, have Notis create a Chaser invoice if the renewal is due and its customer details are confirmed.
Notis builds workflows that link Notion to Chaser. A trigger fires from one place; an action lands in another.
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Creates a new invoice record in the organization.
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Adds a contact person to an existing customer account.
Fires when a new comment is created in the accessible workspace.
Retrieves credit notes.
Fires when a new database container is created.
Retrieves detailed information about a specific customer.
Fires when a new data source is created in the workspace.
Creates an overpayment record for an existing customer to track credit toward future invoices.
Fires when a data source’s columns are added, removed, or renamed.
Retrieves a list of all customers and their contact and status details.
Fires when the body content of an accessible page is updated.
Deletes a contact person from a customer record.
Fires when a new page is created in the accessible workspace.
Retrieves information about the connected organizations.
A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a schedule (recurring or one-time), and a change in one of your Notis databases.
Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,500+ apps can start a workflow.
A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.
Run a workflow on the clock, on a recurring schedule or once at a set date and time. Daily standups, hourly syncs, a one-off launch reminder: the workhorse of Notis.
Fire when a row in one of your Notis databases is added or edited, with optional filters on its properties. New lead added, status changed, value crosses a limit.
Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.
Skip the visual builder. Tell Notis what you want, in plain English. It writes the workflow, you review and deploy.
You · in the Notis Builder
NEW“When a row gets added to the Q4 OKRs Notion database and the status is Blocked, send a Telegram message to the owner with a summary of what's blocking, and ping me if there's no reply within 24 hours.”
Notis built this automation:
Notis Desktop is Mission Control for your AI automations. See every run, replay, edit, or rewind. Set approval gates so Notis pauses before destructive actions.
Automations
Inbox
Migrate background jobs to a durable queue You can cancel it through Stripe
3 daysNotis v3 release update This one’s v3: Notis Manager (desktop app with …
8 daysAdd multi-tenant RBAC User initiates a voice call
13 daysDraft pricing v (tiers, limits, overages) and sanity-check margins
2 weeksVerify analytics events for new features That’s a really interesting automat…
1 monthWhatever starts the workflow, the platform underneath is the same: a thinking brain, full visibility, and you in control.
Every step can include an LLM call: summarise, classify, extract, rewrite.
Every run, every step, every input, all replay-able from Mission Control.
Pause for approval. Notis pings you in chat with one-tap approve.
When an API changes shape, Notis adapts the parser. Less midnight fire-fighting.
Notion and Chaser, or any other combination from 1,500+ integrations.
When this happens · Trigger
Do this · Action
7-day trial of any paid plan, with $20 of usage included.
No card. Works with personal or business Chaser.