Review BTCPay readiness when your setup guidance changes
Update the payment notes in Notion and let Notis retrieve the current BTCPay Server instance information.
Trigger
Page Content Updated
Triggers when the body content of a Notion page is 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 page content edit in the workspace the integration has access to. Notion aggregates content edits within a short window (~60s typical).
Action
Get BTCPay Server Info
Tool to retrieve information about the btcpay server instance. use when needing server version, tor address, supported payment methods, and synchronization states.
Why this helps
Payment setup notes can change while the team continues relying on old assumptions about server readiness.
- Tie a setup-document change to a current instance check.
- Reduce the need to remember a separate verification step.
- Bring server information into a workflow the team already maintains.
Setup
Build it in a few focused steps.
- 1Connect Notion and BTCPay Server to Notis once in the portal.
- 2Tell Notis to retrieve BTCPay Server instance information when the payment-readiness guidance page is edited.
- 3Select the Notion Page Content Updated trigger for that page and choose a channel for run reports.
- 4Test by making one real guidance edit and review the run result.
Questions about this workflow
What information can the action retrieve?
The BTCPay Server information action can return instance details such as version, supported payment methods, and synchronization states.
Does this change BTCPay configuration?
No. This workflow retrieves instance information for a check.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Btcpay server. A trigger fires from one place; an action lands in another.
Notion triggers
Btcpay server actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Payment Request
Tool to create a new payment request for a store. use after confirming store id.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Store
Tool to create a new store in btcpay server. use when you need to provision a new store before processing transactions.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Create BTCPay Server User
Tool to create a new btcpay server user. use when you need to register a new user programmatically as an administrator.
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.
Register a Webhook
Tool to register a new webhook. use when you need to receive store event notifications.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Delete API Key
Tool to revoke a specific api key. use when you need to remove an api key to immediately prevent its use. call after identifying the key to revoke.
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 Payment Request
Tool to delete a specific payment request. use when you need to archive/remove an existing payment request for a store.
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 Store Payout
Tool to delete a specific payout from a store. use when you need to cancel a payout no longer needed.
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.
Get API Key
Tool to retrieve the current api key. use after authentication to get api key details.
Connect any two apps with Notis in the middle.
Notion and Btcpay server, 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 Btcpay server.