BTCPay Server and YNAB Integration

Demonstration of how apps are integrated in WEXTL workflow builder[4]

Connect BTCPay Server and YNAB to automate finance workflows. Trigger events from one app, run actions in the other and use AI to make smart decisions. Integrate apps in 3 simple steps - no code required.

  • 3-day trial
  • Cancel anytime
  • Up to 10 minutes quick set up
  • GDPR
  • Data Encryption
  • 2FA
  • Local Data Region

Learn about BTCPay Server and YNAB

Detailed info you need to know about BTCPay Server and YNAB integrations in WEXTL. Explore which modules apps support and how you connect them.

  • BTCPay Server

    • Finance
    • 1 trigger
    • 72 searches
    • 77 actions

    Self-hosted Bitcoin payments: invoices, payment requests, payouts, stores, webhooks and lightning.[5]

  • YNAB

    • Finance
    • 28 searches
    • 17 actions

    Personal budgeting on YNAB. Pull plans, accounts, categories, payees, months, transactions and scheduled transactions, create and update accounts, categories, category groups, payees, transactions (single or bulk) and scheduled transactions, and trigger vendor Direct Import.[6]

How to connect BTCPay Server to YNAB

Set up your BTCPay Server and YNAB integration in 3 simple steps[2]. No coding required. Up to 10 minutes setup.

How does the integration between BTCPay Server and YNAB work in WEXTL?

WEXTL exposes actions and triggers for BTCPay Server and YNAB that help you connect apps and automate repetitive tasks[1]. A trigger is an event that happens, and an action is a step that performs when the event has occurred.

BTCPay Server triggersYNAB actions

BTCPay Server modules

  • Watch Events Fires instantly when BTCPay Server posts a webhook event. Each run has the Event Type and Delivery ID.
  • Activate an Invoice Payment Method Turns on one payment method of an invoice, such as BTC-CHAIN or BTC-LN, for payment.
  • Add a Store User Gives a user access to a store through a Role. Name the user by id or email, and turn on Require Invitation to send an invitation first.
  • Approve a Payout Approves a pending payout. Use Revision to guard against edits made meanwhile and Rate Rule to convert with a custom rate. A failed approval is not retried automatically.
  • Approve a User Approves a user account on the server. Turn off Approved to withdraw an approval again.
  • Archive a Payment Request Archives a payment request of a store so it is taken out of the active ones.
  • Archive a Pull Payment Stops further claims on a pull payment by archiving it.
  • Archive an Invoice Hides an invoice from the default invoice lists.
  • Broadcast a Wallet Transaction Sends a signed Transaction in raw form to the network through the on-chain Payment Method of a store. Failures here are not retried automatically.
  • Cancel a Payout Cancels a payout that has not been sent yet.
  • Cancel a Store Invitation Withdraws a pending invitation to a store.
  • Connect to a Lightning Peer Joins a Lightning node, either the server node or a store node, to another peer. Write the peer address as nodeid@host:port.
  • Create a Lightning Invoice Creates a BOLT11 invoice on a Lightning node for an Amount (millisats). Use Expiry (seconds) to set its lifetime and Private Route Hints to include private channels.
  • Create a Payment Request Issues a request for payment in a store using a Title and an Amount. Add an Expiry Date, a Reference ID or Allow Custom Payment Amounts.
  • Create a Pull Payment Sets up a pull payment of a total Amount in a Currency. Use Payout Methods to limit how claims are paid and Auto Approve Claims to skip manual approval. A failed setup is not retried automatically.
  • Create a Pull Payment Payout Claims a payout against a pull payment, sent to a Destination through a Payout Method ID. Leave Amount empty to claim the rest. A failed claim is not retried automatically.
  • Create a Store Starts a store named Name. Set Website, Default Currency or Brand Color to shape how it looks and behaves.
  • Create a Store Payout Queues a payout out of store funds to a Destination for an Amount. Turn on Approved to approve it at once, or attach it to a Pull Payment ID. A failed attempt is not retried automatically.
  • Create a User Creates an account from an Email. Use Password to set one, Is Administrator for admin rights and Send Invitation Email to invite the user.
  • Create a Wallet Transaction Builds an on-chain transaction to Destinations. By default it signs and BROADCASTS it, which spends funds. Turn off Broadcast to avoid sending. A failed run is not retried automatically.
  • Create a Webhook Makes BTCPay Server call an Endpoint URL when store events occur. Use Events to restrict which, and Secret to sign every delivery.
  • Create an API Key Makes an API key for your own account. Use Label to name it and Permissions to restrict what it can do. You read the API Key value once.
  • Create an API Key for a User Makes an API key on behalf of another user. Use Label to name it and Permissions to limit the access it grants.
  • Create an App Attaches an app to a store under an App Name, of a chosen App Type. Use Notification URL to receive payment notices.
  • Create an Invoice Issues an invoice in a store for an Amount and Currency. Set Buyer Email to tie it to a customer and Order ID to match your own order. If the run fails, it is not retried automatically.
  • Create an Offering Adds a subscription offering to a store under a Name. Use Features for a JSON list and Success Redirect URL to send customers elsewhere after signing up.
  • Create an Offering Plan Adds a plan to a subscription Offering with a Name, Price and Currency. Use Recurring Type to set the renewal cycle and Trial Days for a free start.
  • Delete a File Deletes an uploaded file on BTCPay Server.
  • Delete a Notification Removes one notification from your inbox.
  • Delete a Store Removes a store from BTCPay Server.
  • Delete a Store Payment Method Disconnects a payment option from your store.
  • Delete a Subscriber Deletes one subscriber of an offering. Use Customer Selector to say which.
  • Delete a User Deletes a BTCPay Server user account.
  • Delete a Webhook Detaches a webhook from a store.
  • Delete an App Deletes an app from a store in BTCPay Server.
  • Delete the Current User Deletes the account of the user that owns the credential. Turn on Confirm Deletion to proceed.
  • Get a File Reads an uploaded file with its Original Name and URL.
  • Get a Lightning Address Reads a Lightning address of a store by Username. You see its Min, Max and Invoice Metadata.
  • Get a Lightning Deposit Address Generates an on-chain Address that tops up a Lightning node.
  • Get a Lightning Invoice Reads an invoice from a Lightning node by Lightning Invoice ID, including its BOLT11 string and a Status that tells whether it was paid.
  • Get a Lightning Node Balance Reads how much funds a Lightning node holds, split into two parts by Onchain and Offchain.
  • Get a Lightning Node Info Reads a Lightning node and its Alias, Version, Block Height and Peers Count.
  • Get a Lightning Payment Fetches one payment of a Lightning node by Payment Hash. It shows the Status and Preimage.
  • Get a Notification Opens one notification from your inbox with its Type, Body and Link.
  • Get a Payment Request Retrieves a payment request with its Title, Amount and Expiry Date.
  • Get a Payout Checks a payout and shows its Destination, Revision and Original Currency.
  • Get a Pull Payment Loads a pull payment with its Amount, Currency and BOLT11 Expiration.
  • Get a Pull Payment LNURL Gives the LNURL for a pull payment in two forms, LNURL Bech32 and LNURL URI.
  • Get a Pull Payment Payout Reads a single payout that was claimed against a pull payment, with its Destination and Date.
  • Get a Rate Configuration Shows how a store converts rates, with the Spread, the Preferred Source and the Effective Script.

YNAB modules

  • Create a Category Starts a category in a group of your plan, using Category Group ID and Name, plus an optional Note. Use Goal Target and Goal Target Date to attach a goal, and the repeat setting for a recurring NEED target.
  • Create a Category Group Creates a group to hold categories in a plan, using a Name capped at 50 characters.
  • Create a Payee Saves a payee into your plan, labelled by a Name of 500 characters at most.
  • Create a Scheduled Transaction Schedules a transaction on an Account ID, starting on a future Date. Fill an Amount and a Memo for the details, and the repeat setting recurs it anywhere from Never to Every Other Year.
  • Create a Transaction Records one transaction through Transaction. For many at once, leave that empty and fill Transactions (Bulk) instead.
  • Create an Account Opens an account under a Name, setting its Type and a starting Balance in milliunits, where 1000 equals one unit.
  • Delete a Scheduled Transaction Deletes a scheduled transaction of a plan from YNAB.
  • Delete a Transaction Deletes a transaction in a plan on YNAB.
  • Get a Category Looks up the category behind a Category ID. Use Get a Month Category for its data in one month.
  • Get a Month Returns the data of a single month in a plan.
  • Get a Month Category Shows how a category stands in a particular Month, as budget data for that period.
  • Get a Payee Pulls up one payee from a budget plan and returns the Payee record kept in YNAB.
  • Get a Payee Location Fetches a saved place that belongs to a payee.
  • Get a Plan Fetches a full export of a plan. A Last Knowledge of Server value narrows it to entities changed since then, and leaving it blank exports everything.
  • Get a Scheduled Transaction Opens one scheduled transaction of a plan for reading. List Scheduled Transactions returns all of them.
  • Get a Transaction Looks up a single transaction and the Server Knowledge value that goes with it.
  • Get an Account Fetches a single account from a plan. List Accounts covers all of them.
  • Get the Plan Settings Looks up how one plan is configured, as stored in YNAB.
  • Get the User Looks up the profile of the authenticated user behind the credential.
  • Import Transactions Triggers Direct Import for the linked accounts in a plan. The result lists the Transaction IDs of the imported ones.
  • List Accounts Collects all accounts, one result each. Set Last Knowledge of Server to get just the accounts that changed.
  • List Categories Reads the category groups of a plan with the categories inside them. Use Last Knowledge of Server to limit the result to what changed since then.
  • List Money Movement Groups Retrieves the groups into which money moved between categories is organised in a plan, plus a Server Knowledge value.
  • List Money Movement Groups by Month Shows those groups of money moved between categories, restricted to one month.
  • List Money Movements Gathers the transfers of money between categories that are recorded in a plan.
  • List Money Movements by Month Pulls the money that was moved between categories during one month.
  • List Months Returns the months in a plan. Add Last Knowledge of Server to cut it down to the ones modified later.
  • List Payee Locations Returns every location saved against payees in a plan.
  • List Payee Locations by Payee Returns the saved places of a single payee.
  • List Payees Shows who you pay, every payee as one result. Add Last Knowledge of Server for the changed ones alone.
  • List Plans Lists your plans and shows the Default Plan. Turn on Include Accounts to add the accounts of each plan to the response.
  • List Scheduled Transactions Gathers future and recurring entries, one result each, with Last Knowledge of Server for changes only.
  • List Transactions Pulls plan transactions. Use Since Date for the start, which defaults to one year ago, and Until Date for the end. Add type to filter by categorization or approval status.
  • List Transactions by Account Gets the transactions posted to one account. Use Since Date for the earliest day and type to narrow by approval status.
  • List Transactions by Category Finds the transactions assigned to one category. Use Until Date to stop at a date, or Last Knowledge of Server for changes only.
  • List Transactions by Month Pulls the transactions of one month in a plan, further restricted with Since Date, Until Date or type.
  • List Transactions by Payee Collects the transactions that name one payee, bounded in time by Since Date and Until Date. Use Last Knowledge of Server to fetch only what changed.
  • Make an API Call Runs a free-form request against the YNAB REST API using your saved credential.
  • Update a Category Changes the Name and Note of a category, moves it with Category Group ID, and adjusts its goal amount via Goal Target.
  • Update a Category Group Edits the Name of a category group, within the limit of 50 characters.
  • Update a Month Category Sets the amount assigned to a category in one month, through Budgeted in milliunits.
  • Update a Payee Renames a payee, which is the only change YNAB allows. The new Name may have 500 characters at most.
  • Update a Scheduled Transaction Edits a scheduled transaction. YNAB wants Account ID and Date on every update, so send them along with Amount or Memo.
  • Update a Transaction Amends a transaction by Account ID, Date, Amount, Memo, cleared or Approved. The help warns that split transactions have limits.
  • Update Transactions (Bulk) Applies edits to many transactions in a single call. Each row of Transactions needs either an ID or an Import ID, not both.

Explore alternative integrations

There are other apps[9] supported by WEXTL that can be paired with BTCPay Server and YNAB integrations. Pick any from the list below if the current combination isn't the one you need.

Automate BTCPay Server and YNAB on WEXTL®

Claim your 3-day trial to build BTCPay Server with YNAB integration and access every WEXTL® feature.

Cancel anytime.

Frequently asked questions

Common questions about connecting BTCPay Server and YNAB.

How do I connect BTCPay Server and YNAB?

Connect your BTCPay Server and YNAB accounts once, pick a trigger in one app and an action in the other, then map the fields so data flows automatically between them.[3]

What can I automate between BTCPay Server and YNAB?

Example: when the "Watch Events" trigger in BTCPay Server fires, WEXTL can "Create a Category" in YNAB. BTCPay Server has 1 trigger (including Watch Events). YNAB has 45 actions (including Create a Category, Create a Category Group, and Create a Payee). Add filters and transforms between steps when you need them.[1]

Can BTCPay Server trigger actions in YNAB, and YNAB in BTCPay Server?

Yes. The integration works in both directions. Use the triggers of each app to start a workflow and the actions of the other app to update it.[2]

Do I need to write code to integrate BTCPay Server and YNAB?

No. BTCPay Server-to-YNAB automations are built visually on the canvas. You can optionally add custom JavaScript with Functions when you need advanced logic.[4]

Does BTCPay Server integrate with YNAB in real time?

Yes. Trigger-based automations start the moment BTCPay Server (or YNAB) fires a new event. Webhook-backed apps run within seconds, and polling-only apps re-check on a schedule you control.[7]

How long does it take to set up a BTCPay Server + YNAB integration?

A first automation typically takes 5–10 minutes: connect the credential of each app once, drop a trigger + action onto the canvas, map the fields, and turn the workflow on.

Do I need a paid plan to connect BTCPay Server with YNAB?

You can build your BTCPay Server + YNAB automation on a 3-day trial with every feature unlocked. Cancel anytime.[8]

References

List of sources used to gather information about the BTCPay Server and YNAB integration.

  1. BTCPay Server and YNAB integration source code, module specs and credentials implementation.
  2. Our BTCPay Server and YNAB integration documentation, structured input and output parameters, scopes, and authentication methods.
  3. Official vendor API documentation for BTCPay Server and YNAB, used to verify field meanings, authentication flows, and anything our own specs don't fully capture.
  4. WEXTL® visual workflow builder, anonymized data from our technical support team.
  5. BTCPay Server integration information
  6. YNAB integration information
  7. WEXTL® Scheduling
  8. WEXTL® Pricing and Trial
  9. WEXTL® Apps Library

How we write our apps documentation

Explore how WEXTL® crafted BTCPay Server and YNAB integration page documentation. Used sources, the role of AI, and how the team validates the result.

Explore BTCPay Server and YNAB, or get started