Connect Agenty to Btcpay server

When something happens in Agenty, 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

Build an automation Browse examples

Examples

Ways Notis can move work from Agenty to Btcpay server

View example

Turn a Website Inquiry into a Bitcoin Payment Request

Create a BTCPay payment request when an Agenty browser workflow sends a qualified inquiry and the required store and payment details are available.

View example

Prepare a Payment Request After a Monitored Price Change

Use an Agenty website-change webhook to create a BTCPay payment request when it includes an approved price, store ID, and request details.

View example

Register a BTCPay Webhook for a Monitored Workflow

When an Agenty workflow signals that a store needs event notifications, register a BTCPay webhook using endpoint and store details supplied in the request.

View example

Review BTCPay Payment Requests on a Schedule

Have Notis periodically retrieve payment requests for a confirmed store and summarize the returned list for a quick review.

View example

Keep a Scheduled Inventory of Store Webhooks

Periodically list registered webhooks for a confirmed BTCPay store and summarize their returned configuration details.

View example

Get a Scheduled BTCPay Server Snapshot

Retrieve BTCPay Server instance information on a schedule and summarize the version, supported payment methods, and synchronization states returned.

View example

Review BTCPay Store Configuration Regularly

Retrieve the configuration for a confirmed BTCPay store on a schedule and summarize the returned details for review.

View example

Review Apps Associated with a BTCPay Store

Periodically list apps associated with a confirmed BTCPay store and summarize the basic metadata returned by BTCPay.

Supported Triggers and Actions

Notis builds workflows that link Agenty to Btcpay server. A trigger fires from one place; an action lands in another.

Agenty triggers

Btcpay server actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

Create Payment Request

Creates a reusable payment request page for customers to pay an amount.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

Create Store

Creates a new store.

ActionInstant

Create BTCPay Server User

Creates a new user account.

ActionInstant

Register a Webhook

Registers a webhook to receive real-time notifications about store events.

ActionInstant

Delete API Key

Immediately revokes an API key so it can no longer be used.

ActionInstant

Delete Payment Request

Archives a payment request; once deleted, it cannot be restored.

ActionInstant

Cancel Store Payout

ActionInstant

Get Current API Key

Retrieves details and permissions for the current API key only, not all account keys; it cannot change keys.

ActionInstant

Trigger Types

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.

New Notion pageStripe chargeCalendar event

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.

Any HTTP POSTCustom backendIoT event

Works with

ZapierPipedream

Most used

Recurring triggers

Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.

Daily · 8:00HourlyWeekdays only

Coming soon

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.

Row insertedValue > limitQuery match

Why AI automation

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.

Classic automationAI automation

Cost

$ · pay per run

$$ · AI models per run

Reliability

Breaks on schema change

Adapts to format changes

Setup

Click 8 dropdowns

Describe it in English

Handles fuzzy

Hard-coded fields only

Reads intent, summarises

Human in loop

Bolted on

Built in · approval inbox

Maintenance

You own every break

Self-heals · we own it

Ease of use

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:

TriggerRow added to "Q4 OKRs"

Condition✦Status = "Blocked"

AI step✦Summarise the blocker in plain English

ActionDM the row owner with summary

Timeout✦No reply in 24h → ping you

Observability

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.