Skip to content
Notis

Connect Asana to BTCPay Server

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

Fires when an attachment is added to a task.

Do this · Action

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

Examples

Ways Notis can move work from Asana to BTCPay Server

Create a Bitcoin payment request from an Asana task

Turn a new Asana task into a BTCPay Server payment request when the task includes the payment details and store ID.

Create payment requests when tasks reach an approved section

When an Asana task moves into your chosen approval section, ask Notis to create a BTCPay Server payment request using its details and store ID.

Turn payment instructions in Asana comments into a request

Use a new comment on an Asana task to create a BTCPay Server payment request when the comment supplies the needed details and store ID.

Create payment requests from tagged Asana tasks

When a tag is added to an Asana task, use Notis to create a BTCPay Server payment request if the tag signals payment readiness and the task has a store ID.

Create a payment request after an Asana task update

Use a task update as the prompt to create a BTCPay Server request when the updated task now includes complete payment details and a store ID.

Provision a BTCPay Server store from an Asana setup task

Use a new Asana task to request BTCPay Server store creation when it clearly describes a new store that needs provisioning.

Review BTCPay Server payment requests on a schedule

Ask Notis to retrieve payment requests for a confirmed store on a recurring schedule and send a concise review report.

Review BTCPay Server store webhooks on a schedule

Have Notis list a store's configured webhooks on a recurring schedule and report the details for review.

Review apps associated with a BTCPay Server store

On a recurring schedule, retrieve the apps associated with a specific store and send a concise inventory report.

Supported Triggers and Actions

Notis builds workflows that link Asana to BTCPay Server. A trigger fires from one place; an action lands in another.

Asana 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

Attachment Added to Task

Fires when an attachment is added to a task.

TriggerInstant

Create BTCPay Server User

Creates a new user account.

ActionInstant

New Comment on Task

Fires when a comment is added to a task in a project.

TriggerInstant

Register a Webhook

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

ActionInstant

New Task Created

Fires when a new task is created in a project.

TriggerInstant

Delete API Key

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

ActionInstant

Task Moved to Section

Fires when a task is moved to a section in a project.

TriggerInstant

Delete Payment Request

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

ActionInstant

Tag Added to Task

Fires when a tag is added to a task.

TriggerInstant

Cancel Store Payout

Deletes a pending payout; it cannot be canceled once processed or completed.

Conditions and details

The operation deletes a specific payout that is pending and no longer needed. It can be canceled only while awaiting approval or awaiting payment; payouts that have already been processed or completed cannot be canceled. The API key must have permission to manage payouts for the store.

ActionInstant

Task Updated

Fires when a task is updated in a project.

TriggerInstant

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 schedule (recurring or one-time), and a change in one of your Notis databases.

Integration triggers

Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,600+ 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

Scheduled triggers

Run a workflow on the clock, on a recurring schedule or once at a set date and time. Daily standups, hourly syncs, a one-off launch reminder: the workhorse of Notis.

Daily · 8:00Weekdays onlyOnce · Dec 13
Beta

Database triggers

Fire when a row in one of your Notis databases is added or edited, with optional filters on its properties. New lead added, status changed, value crosses a limit.

Row addedProperty editedValue > limit
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.

Notis

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.

  • 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

All12Manager5Telegram1Messages0WhatsApp2Email4Slack8

Migrate background jobs to a durable queue You can cancel it through Stripe

3 days

Notis v3 release update This one’s v3: Notis Manager (desktop app with …

8 days

Add multi-tenant RBAC User initiates a voice call

13 days

Draft pricing v (tiers, limits, overages) and sanity-check margins

2 weeks

Verify analytics events for new features That’s a really interesting automat…

1 month

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

Related pairs

More ways to connect Asana and BTCPay Server

Connect any two apps with Notis in the middle.

Asana and BTCPay Server, or any other combination from 1,600+ 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.