Connect Abstract to Btcpay server

When something happens in Abstract, 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 Abstract to Btcpay server

View example

Create a BTCPay Request from a Verified Checkout

When a webhook receives a checkout request with an email verified through Abstract, create a payment request in the confirmed BTCPay store.

View example

Review BTCPay Payment Requests on a Schedule

Run a recurring review of payment requests for a confirmed BTCPay store and summarize the returned list for easier follow-up.

View example

Register a BTCPay Webhook from an Operations Request

Use an incoming Notis webhook request to register a BTCPay store webhook when the request supplies the store and destination details.

View example

Audit BTCPay Store Webhooks Regularly

On a recurring schedule, list configured webhooks for a store and summarize what is registered for a lightweight review.

View example

Provision a BTCPay Store from a Request

When a Notis webhook receives an approved provisioning request, create a BTCPay Server store and report the result.

View example

Get a Scheduled BTCPay Server Snapshot

At a recurring time, retrieve BTCPay Server instance information and summarize returned version, payment method, and synchronization details.

View example

Remove a BTCPay Payment Request After Cancellation

Use an incoming cancellation request to delete a specified BTCPay payment request for a store after the request is confirmed.

View example

Review Apps Associated with a BTCPay Store

Run a recurring inventory of apps associated with a specified store and summarize the returned metadata for review.

View example

Verify a BTCPay Webhook After Setup

When a setup request includes a store and webhook identifier, retrieve that webhook's details and report the returned configuration.

Supported Triggers and Actions

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

Abstract 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

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.