Connect Affinity to Btcpay server

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

View example

Create a BTCPay Request for an Investor Commitment

Turn an investor commitment from Affinity into a BTCPay payment request when you submit its deal details to a Notis webhook.

View example

Prepare a BTCPay Request for a Portfolio Company Invoice

Start a payment request for a portfolio company invoice using deal context submitted from your Affinity workflow.

View example

Set Up BTCPay Payment Requests for Investor Event Tickets

Create a BTCPay payment request for event ticket details submitted from an Affinity contact or deal workflow.

View example

Create a BTCPay Request When a Deal Reaches a Billing Milestone

Submit a billing milestone from an Affinity deal and have Notis create its BTCPay Server payment request.

View example

Create a BTCPay Request for an Investor Outreach Service Fee

Turn a confirmed service fee from your Affinity outreach process into a BTCPay Server payment request.

View example

Register a BTCPay Webhook for Deal Payment Notifications

View example

Verify the BTCPay Webhook for an Affinity Deal

Retrieve the configured BTCPay Server webhook details for a store and webhook ID included with deal context.

View example

Review BTCPay Store Webhooks Alongside Affinity Deal Follow-Up

On a schedule, list webhooks for a confirmed BTCPay store so you can review notification setup during deal follow-up.

View example

Check BTCPay Server Readiness During Deal Operations Review

On a schedule, retrieve BTCPay Server instance information to review supported payment methods and synchronization states.

Supported Triggers and Actions

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

Affinity 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.