Create a BTCPay request from a Notion client record
When a new client record is added in Notion, create a matching BTCPay payment request so collecting payment is part of onboarding.
When something happens in Notion, Notis takes the next step in BTCPay Server. 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 reusable payment request page for customers to pay an amount.
When a new client record is added in Notion, create a matching BTCPay payment request so collecting payment is part of onboarding.
Use a Notion invoice status update as the signal to create a BTCPay Server payment request for an approved invoice.
When a new retainer period is added to a Notion database, create a corresponding payment request in BTCPay Server.
Turn qualifying Notion event-registration pages into BTCPay Server payment requests for paid sessions or tickets.
A new billable milestone in Notion can prompt Notis to create its payment request in BTCPay Server.
When an offer's Notion status changes to cancelled, have Notis remove its corresponding BTCPay Server payment request.
A Notion status change to ready for payment can start creation of the matching BTCPay Server request.
When a new paid-campaign record is added to Notion, create a BTCPay Server payment request for the campaign.
When a team member confirms in a Notion comment that a charge is ready, have Notis create the matching BTCPay request.
Notis builds workflows that link Notion to BTCPay Server. 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 reusable payment request page for customers to pay an amount.
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Creates a new store.
Fires when a new comment is created in the accessible workspace.
Creates a new user account.
Fires when a new database container is created.
Registers a webhook to receive real-time notifications about store events.
Fires when a new data source is created in the workspace.
Immediately revokes an API key so it can no longer be used.
Fires when a data source’s columns are added, removed, or renamed.
Archives a payment request; once deleted, it cannot be restored.
Fires when the body content of an accessible page is updated.
Deletes a pending payout; it cannot be canceled once processed or completed.
The operation deletes a specific payout that is pending and no longer needed. It can be canceled only while awaiting approval or awaiting payment; payouts that have already been processed or completed cannot be canceled. The API key must have permission to manage payouts for the store.
Fires when a new page is created in the accessible workspace.
Retrieves details and permissions for the current API key only, not all account keys; it cannot change keys.
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,600+ 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 BTCPay Server, or any other combination from 1,600+ 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 BTCPay Server.