Connect ActiveMerge to Btcpay server
When something happens in ActiveMerge, 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 ActiveMerge to Btcpay server
Request payment after document approval
Create a BTCPay payment request after an approved document workflow is reported to Notis.
Register payment notifications for a document workflow
Register a BTCPay store webhook when a document workflow is ready to be monitored for payment events.
Review payment requests on a schedule
List payment requests for a confirmed BTCPay store on a recurring schedule for a concise review.
Audit BTCPay store webhooks regularly
List the configured webhooks for a store on a schedule and summarize the returned configuration for review.
Check BTCPay instance information
Retrieve BTCPay Server version, payment methods, Tor address, and synchronization states on a schedule.
Check a BTCPay store before document-driven billing
Retrieve a store's configuration when a document workflow reports that payment setup needs review.
Verify a payment webhook after setup
Retrieve details for a specific BTCPay store webhook when a document process reports that notification setup needs checking.
Review BTCPay store apps
List apps associated with a specified store on a recurring schedule and summarize the returned metadata.
Check the current BTCPay API key
Retrieve the current key's label and granted permissions when a document workflow signals that access needs review.
Supported Triggers and Actions
Notis builds workflows that link ActiveMerge to Btcpay server. A trigger fires from one place; an action lands in another.
ActiveMerge triggers
Btcpay server actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Payment Request
Creates a reusable payment request page for customers to pay an amount.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Store
Creates a new store.
Create BTCPay Server User
Creates a new user account.
Register a Webhook
Registers a webhook to receive real-time notifications about store events.
Delete API Key
Immediately revokes an API key so it can no longer be used.
Delete Payment Request
Archives a payment request; once deleted, it cannot be restored.
Cancel Store Payout
Get Current API Key
Retrieves details and permissions for the current API key only, not all account keys; it cannot change keys.
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 ActiveMerge and Btcpay server
Connect any two apps with Notis in the middle.
ActiveMerge 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.