Connect Box to Btcpay server

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

View example

Turn a Box invoice into a Bitcoin payment request

When a new invoice file lands in Box, use its available details to prepare a BTCPay Server payment request for the confirmed store.

View example

Review BTCPay requests when an invoice changes

When a new version of a tracked Box invoice is uploaded, retrieve payment requests for its confirmed store so Notis can report items that may need review.

View example

Start payment setup after a Box sign request completes

When a Box Sign request changes to a completed state, use available document details to create a BTCPay Server payment request for the confirmed store.

View example

Create a BTCPay request from changed payment terms

When a tracked Box file changes, review its available content for updated payment terms and create a BTCPay request only when the amount and store are clear.

View example

Provision a BTCPay store from a Box client packet

When a new client item is added to a Box onboarding folder, use its available details to create a BTCPay Server store when the required information is clear.

View example

Include BTCPay app inventory in a new collaboration report

When a new collaboration is created on a Box folder, retrieve the associated store's app list and include it in a concise handoff report.

View example

Add BTCPay server health context to a scheduled operations check

On a schedule, retrieve BTCPay Server instance information and summarize the available synchronization and payment method status for an operations check.

View example

Audit BTCPay store webhooks on a schedule

On a recurring schedule, list configured webhooks for a confirmed BTCPay store and summarize the current configuration for review.

Supported Triggers and Actions

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

Box 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

Tool to create a new payment request for a store. use after confirming store id.

ActionInstant

Webhook trigger

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

TriggerInstant

Create Store

Tool to create a new store in btcpay server. use when you need to provision a new store before processing transactions.

ActionInstant

Collaboration Details Changed

Triggers when a collaboration's details change (e.g., role, status, expiration). This trigger monitors a specific collaboration and detects when any meaningful field changes, such as role, status, expiration date, access type, or acknowledgment status.

TriggerPolling

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.

ActionInstant

Comment Changed

Triggers when a comment's content or details change in Box. This trigger monitors a specific Box comment and detects when any meaningful field changes, such as message text edits, tagged message changes, or modification timestamp updates.

TriggerPolling

Register a Webhook

Tool to register a new webhook. use when you need to receive store event notifications.

ActionInstant

New File Comment Added

Triggers when a new comment is added to a file in Box. This trigger monitors a specific Box file and fires when new comments are detected.

TriggerPolling

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.

ActionInstant

File Metadata Changed

Triggers when a file's metadata or properties change in Box. This trigger monitors a specific Box file and fires when changes are detected in key fields like name, description, size, modification time, parent folder, or status.

TriggerPolling

Delete Payment Request

Tool to delete a specific payment request. use when you need to archive/remove an existing payment request for a store.

ActionInstant

File Shared Link Changed

Triggers when a file's shared link settings change in Box. This trigger monitors a specific Box file's shared link and fires when changes are detected in the shared link configuration, such as access level, permissions, password protection, expiration date, or vanity URL.

TriggerPolling

Delete Store Payout

Tool to delete a specific payout from a store. use when you need to cancel a payout no longer needed.

ActionInstant

New File Version Uploaded

Triggers when a new file version is uploaded to a file in Box. This trigger monitors a specific Box file and fires when new versions are detected.

TriggerPolling

Get API Key

Tool to retrieve the current api key. use after authentication to get api key details.

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.