Connect 21risk to Btcpay server
When something happens in 21risk, 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
Do this · Action
Ways Notis can move work from 21risk to Btcpay server
Check BTCPay readiness after a 21risk audit
Review BTCPay server status when a 21risk audit reaches Notis.
Review BTCPay store configuration on a schedule
Run a recurring review of a BTCPay store informed by 21risk compliance priorities.
Create a BTCPay payment request after audit approval
Turn an approved 21risk control into a ready payment request.
Inventory BTCPay payment requests for risk review
Give your weekly 21risk review a current list of BTCPay payment requests.
Register a BTCPay webhook for a new risk control
Register store notifications when 21risk identifies a control that needs payment monitoring.
Audit BTCPay store webhooks against 21risk controls
Review registered store webhooks and summarize control coverage.
Verify a BTCPay webhook after a risk setup change
Check a specific webhook when 21risk reports a setup change.
Inventory BTCPay store apps for a monthly risk review
List store apps and summarize their relevance to 21risk oversight.
Check a BTCPay user after a 21risk assignment
Retrieve BTCPay user information when a risk action assigns payment ownership.
Supported Triggers and Actions
Notis builds workflows that link 21risk to Btcpay server. A trigger fires from one place; an action lands in another.
21risk 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.
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.
Register a Webhook
Tool to register a new webhook. use when you need to receive store event notifications.
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.
Delete Payment Request
Tool to delete a specific payment request. use when you need to archive/remove an existing payment request for a store.
Delete Store Payout
Tool to delete a specific payout from a store. use when you need to cancel a payout no longer needed.
Get API Key
Tool to retrieve the current api key. use after authentication to get api key details.
Four ways to start an automation.
A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a recurring schedule, and soon, your own database.
Integration triggers
Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,000+ apps can start a workflow.
Webhook triggers
A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.
Recurring triggers
Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.
Database triggers
Watch a row, query, or threshold in your own database and fire the moment the data changes. Row inserted, value crosses a limit, query starts matching.
Classic automation breaks. AI adapts.
Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.
Describe it. Notis builds it.
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:
Watch every run.
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.
- Full run history with inputs, outputs and traces
- Replay any run with edited inputs
- Approval inbox, confirm via chat in one tap
- Audit logs for compliance teams
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 monthEverything in the box.
Whatever starts the workflow, the platform underneath is the same: a thinking brain, full visibility, and you in control.
AI in the middle
Every step can include an LLM call: summarise, classify, extract, rewrite.
Full observability
Every run, every step, every input, all replay-able from Mission Control.
Human in the loop
Pause for approval. Notis pings you in chat with one-tap approve.
Self-healing
When an API changes shape, Notis adapts the parser. Less midnight fire-fighting.
More ways to connect 21risk and Btcpay server
Connect any two apps with Notis in the middle.
21risk 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.