Resources · n8n integration

Wise n8n integrationAutomate Wise with n8n.

Ready to move money from a workflow instead of a browser tab? The Wise n8n integration exposes 14 operations across 6 resources, from quotes and transfers to balances and statements, plus a trigger that listens to 4 events on a profile. Written for ops and finance teams already running n8n.

Try the Wise integration on n8nSee the 14 operations

Verified Trustpilot reviews · AI, automation & growth agency

Why automate

What does the Wise n8n integration actually cover?

The Wise n8n integration pairs two blocks. The Wise node calls the Wise API when the workflow runs, with 14 operations spread over 6 resources: Account, Exchange Rate, Profile, Quote, Recipient and Transfer. The Wise Trigger works the other way round and starts a workflow when Wise pushes one of its 4 events. Both share the same credential, a set of connection details saved once in n8n and picked from a dropdown in every node.

Three shapes come back again and again. The first one is a payout run. Rows arrive from Google Sheets, the workflow prepares a quote with quote.create, builds the transfer on top of it with transfer.create, and releases it with transfer.execute. Nothing leaves the account before that last node, so a manual approval step fits neatly in the middle.

The second one is a treasury watch. The trigger fires on balanceUpdate, the workflow reads the full picture with account.getBalances and posts a short recap in Slack. Finance sees the movement in the channel it already reads, instead of a tab nobody opened since Monday.

The third one is reconciliation. transfer.getAll pulls the transfers of a profile filtered by status, account.getStatement downloads the statement as a file, and that file lands as an attachment in Xero or Quickbooks without anyone exporting anything by hand.

The node has edges, and they are easy to plan around. Recipients can be listed, not created, so the accounts you pay to are set up in Wise first. A transfer always references a quote created before it. Listings that can grow use the standard pair Return All and Limit: leave Return All off and the node stops at Limit transfers instead of walking the whole history. For anything the node does not expose, the HTTP Request node calls the endpoint directly and reuses the same Wise credential through predefined authentication, so there is no second set of keys to manage.

One habit is worth keeping on a money workflow: run the first version against a Wise test sandbox account, which the credential handles through its Environment field. The n8n review goes into where the platform fits and where it does not.

Connect

How do you connect Wise to n8n?

  1. 01

    Generate an API token in Wise

    In Wise, open your user menu > Settings > API tokens and generate a token. That token is what n8n sends on every call, so it carries the rights of the account it was created from. Copy it once, it is the only value you cannot read again later from the interface.

  2. 02

    Create the Wise credential in n8n

    In n8n, go to Credentials and create a Wise credential, the saved connection n8n reuses everywhere. Paste the token in API Token, then set Environment: pick Test when the token comes from a Wise test sandbox account, Live otherwise. The same credential serves the Wise node and the Wise Trigger.

  3. 03

    Add a private key for SCA endpoints

    Some live endpoints are protected by Strong Customer Authentication. Generate an RSA key pair with openssl genrsa -out private.pem 2048, add the public key in Wise under Settings > API tokens > Manage public keys, and paste the private key content in the Private Key (Optional) field of the n8n credential.

Triggers

What can start a Wise workflow in n8n?

Wise Trigger is the node that starts a workflow when something happens in Wise. It listens to 4 events, listed below by family. Pick one or several, activate the workflow: n8n registers the webhook on your Wise account.

What you see in n8n

Every event, by family

One row per object, one chip per action. The event to tick in the node is object.action; hover a chip to read exactly when it fires.

balance.*2
    tranfer.*1
      transfer.*1

        Configuration notes

        01Configure the Wise TriggerThe Wise Trigger listens through a webhook, an URL that n8n exposes and Wise calls as soon as something happens. n8n registers that URL when you activate the workflow, so the event lands in n8n within seconds, without n8n asking Wise anything on a timer.

        The Wise Trigger listens through a webhook, an URL that n8n exposes and Wise calls as soon as something happens. n8n registers that URL when you activate the workflow, so the event lands in n8n within seconds, without n8n asking Wise anything on a timer.

        Key parameters

        • Profile Name or ID: required, and the reason the trigger is scoped. Choose the profile in the list n8n loads from your account, or set it with an expression, a short piece of code between double braces that reads a value instead of hard-coding it.
        • Event: the single event this node reacts to, picked among the 4 available. There is no catch-all value, so a workflow that needs two events carries two trigger nodes, each with its own branch.
        When to use it
        whenever the workflow should follow money that Wise moves on its own, rather than money your workflow decided to move.
        02Balance Credit and Balance UpdateThe balance family holds 2 of the 4 events, and the difference between them decides how noisy the workflow gets. balanceCredit fires every time a balance account is credited, so only money coming in. balanceUpdate fires every time a balance account is credited or debited, incoming and outgoing alike.

        The balance family holds 2 of the 4 events, and the difference between them decides how noisy the workflow gets. balanceCredit fires every time a balance account is credited, so only money coming in. balanceUpdate fires every time a balance account is credited or debited, incoming and outgoing alike.

        Key parameters

        • Event: pick balanceCredit for an inbound-only flow, balanceUpdate when the ledger matters in both directions.
        Use cases
        a client pays an invoice, the credit event starts the workflow, account.getBalances reads the currency balances and a message goes out to the channel that chases payments. With the update event instead, the same branch feeds a running log of every movement on the account. Whichever one you pick, the note stays tied to the profile set in Profile Name or ID, so a second profile to watch means a second trigger node and its own branch next to it.
        03Transfer State Changed and Transfer Active CaseThe other 2 events follow transfers rather than balances. tranferStateChange fires every time a transfer's status is updated, which is how a workflow learns that a payout left the account or came back. transferActiveCases fires every time a transfer's list of active cases is updated, meaning Wise has opened or closed something that needs attention on that transfer.

        The other 2 events follow transfers rather than balances. tranferStateChange fires every time a transfer's status is updated, which is how a workflow learns that a payout left the account or came back. transferActiveCases fires every time a transfer's list of active cases is updated, meaning Wise has opened or closed something that needs attention on that transfer.

        Key parameters

        • Event: the status event for normal progress, the active case event for transfers that need a human.
        Use cases
        on a status change, transfer.get pulls the transfer back with its receipt once it has been sent, and the file joins the accounting record. Note the event value itself, tranferStateChange, carries a typo in n8n: copy it as it is when you write an expression around it.
        Actions

        What can the Wise node do in a workflow?

        The Wise node exposes 14 operations across 6 resources. For each one: the node as you configure it in n8n, the required fields, and our field notes.

        Resources × operations matrix
        ResourceCreateGetGet ManyDeleteExecuteGet BalancesGet CurrenciesGet Statement
        Account✓✓✓
        Exchange Rate✓
        Profile✓✓
        Quote✓✓
        Recipient✓
        Transfer✓✓✓✓✓

        Account

        3 operations
        01

        Get balances

        account.getBalances

        What you see in n8n

        Notes & use cases

        Reads every currency balance held on a Wise profile and returns them as items, one per currency. It reads only, nothing moves.

        Key parameters

        • Profile Name or ID: the profile the balances belong to. Pick it from the list n8n loads from the account, or pass an ID with an expression such as {{ $json.profileId }} when an earlier node provides it.
        Use cases
        before a payout branch creates anything, check the balance that will fund it, and send the item to a review step when the currency is not covered.
        02

        Get currencies

        account.getCurrencies

        What you see in n8n

        Notes & use cases

        Lists the currencies opened in the borderless account of the connected user. Nothing to fill in: the operation reads the account the API token belongs to.

        Use cases
        validate a payout file before the workflow starts creating things. If a target currency is missing from the list the account holds, the row goes to a manual queue instead of failing halfway through a run of transfers.
        03

        Get a statement

        account.getStatement

        What you see in n8n

        Notes & use cases

        Downloads the statement of a borderless account and attaches it to the item as a file, ready to be mailed or stored.

        Key parameters

        • Borderless Account Name or ID: which account the statement covers, from the list or through an expression.
        • Put Output File in Field: the name of the binary field that carries the downloaded file to the next node.
        • File Name: the name the file gets, for example data.pdf.
        • Format: JSON, CSV, PDF or XML in CAMT.053 flavor. Add Line Style to choose Compact, one line per transaction, or Flat, which splits transaction fees onto their own lines.
        Use cases
        mail the monthly statement to the bookkeeping address on a schedule.

        Exchange Rate

        1 operation
        04

        Get an exchange rate

        exchangeRate.get

        What you see in n8n

        Notes & use cases

        Queries the exchange rate Wise publishes for a currency pair and returns it as data the next nodes can read, compare or store.

        Key parameters

        • Source Currency and Target Currency: the two currency codes of the pair to look up.
        • Time, Range and Interval, in Additional Fields: a point in time, a period, or the granularity of the series, Day, Hour or Minute, when history matters more than the current value.
        Use cases
        write the pair used for invoicing into a sheet every morning, so the finance team keeps its own series instead of screenshots.

        Profile

        2 operations
        05

        Get a profile

        profile.get

        What you see in n8n

        Notes & use cases

        Fetches a single Wise profile, personal or business, and returns its details. Most other operations need a profile, which makes this node a natural first step in a branch.

        Key parameters

        • Profile Name or ID: the profile to retrieve, selected in the dropdown n8n populates from the account, or given as an ID through an expression when the value travels with the item.
        Use cases
        a workflow shared between a personal and a business profile resolves the right one at the start, then reuses it in every Wise node downstream.
        06

        Get many profiles

        profile.getAll

        What you see in n8n

        Notes & use cases

        Returns all the profiles the API token can see, personal and business together. No parameter to set, which makes it the quickest way to find out what a token actually reaches.

        Use cases
        run it once while building, read the profile IDs in the output panel, and keep them at hand for the nodes that ask for a profile. It also works as a health check on a scheduled workflow: if this operation fails, the credential is the first suspect.

        Quote

        2 operations
        07

        Create a quote

        quote.create

        What you see in n8n

        Notes & use cases

        Prepares the quote a transfer will be built on. Wise answers with a quote whose ID the next operations reference.

        Key parameters

        • Profile Name or ID: the profile the quote is created under.
        • Target Account Name or ID: the account that will receive the funds.
        • Amount Type with Amount: Source when the amount is what leaves, Target when it is what must land.
        • Source Currency and Target Currency: the codes to send from and receive in.
        Use cases
        an approved supplier invoice creates its quote, then waits for a human to confirm before any transfer is built.
        08

        Get a quote

        quote.get

        What you see in n8n

        Notes & use cases

        Reads back a quote that already exists and returns its current content, without creating anything.

        Key parameters

        • Quote ID: the identifier of the quote to retrieve, usually stored by the branch that created it.
        Use cases
        a payout that waits for an approval is resumed by a second workflow. Before executing anything, that workflow reads the quote again, so nobody releases a transfer built on a quote prepared the day before without a fresh look at it.

        Recipient

        1 operation
        09

        Get many recipients

        recipient.getAll

        What you see in n8n

        Notes & use cases

        Returns the recipient accounts registered in Wise, the accounts a transfer can be sent to.

        Key parameters

        • Return All: on, the node walks the pages of the API and brings back every recipient; off, it stops at Limit.
        • Limit: the maximum number of recipients returned when Return All stays off, enough for a quick check while building.
        Use cases
        refresh a reference list every night so the payout file is checked against recipients that really exist before a single quote is created.

        Transfer

        5 operations
        10

        Create a transfer

        transfer.create

        What you see in n8n

        Notes & use cases

        Builds the transfer itself from a quote. The transfer exists and is staged after this node, but the funds have not moved yet.

        Key parameters

        • Profile Name or ID: the profile the transfer belongs to.
        • Quote ID: the quote the transfer is based on, which is why Create a quote runs first.
        • Target Account Name or ID: the account that receives the funds.
        • Reference, in Additional Fields: the text shown on the recipient's bank statement, the place to put an invoice number.
        Use cases
        stage every supplier payment of the week, then execute them in one approved batch.
        11

        Delete a transfer

        transfer.delete

        What you see in n8n

        Notes & use cases

        Removes a transfer from Wise using its identifier. This is the way back when a branch created something it should not have.

        Key parameters

        • Transfer ID: the transfer to delete, usually carried by the item since the node that created it.
        Use cases
        an approval step ends in a refusal, so the workflow deletes the staged transfer instead of leaving it waiting in the Wise interface for someone to notice it next month.
        12

        Execute a transfer

        transfer.execute

        What you see in n8n

        Notes & use cases

        Releases a transfer that was created earlier. This is the node that actually moves the funds, so it deserves its own branch and its own guardrail.

        Key parameters

        • Profile Name or ID: the profile the transfer is executed under.
        • Transfer ID: the transfer to release.
        Use cases
        put a Wait or an approval node right before it, so a payout run can be reviewed while it is still reversible. Everything upstream can be replayed safely, this node cannot.
        13

        Get a transfer

        transfer.get

        What you see in n8n

        Notes & use cases

        Retrieves one transfer and, on request, downloads its receipt as a file attached to the item.

        Key parameters

        • Transfer ID: the transfer to retrieve.
        • Download Receipt: on, the node fetches the receipt PDF. It only works for executed transfers with the status Outgoing Payment Sent.
        • Put Output File in Field: the binary field the receipt is written into.
        • File Name: the name given to the downloaded file, for example data.pdf.
        Use cases
        a status event arrives, the node pulls the receipt and files it with the supplier invoice it pays.
        14

        Get many transfers

        transfer.getAll

        What you see in n8n

        Notes & use cases

        Lists the transfers of a profile, with filters that narrow the history down to what the workflow is looking for.

        Key parameters

        • Profile Name or ID: the profile whose transfers are listed.
        • Return All and Limit: all the transfers of the period, or a capped batch.
        • Status, Range, Source Currency and Target Currency, in Filters: keep only Processing or Outgoing Payment Sent items, a date range, or one currency pair.
        Use cases
        a weekly reconciliation pulls the sent transfers and matches them line by line against the accounting ledger.
        Need help

        Need help automating Wise with n8n?

        A person reads every message.

        FAQ

        Questions people ask about Wise and n8n

        01Is the Wise n8n integration free to use?
        Yes on the n8n side. The Wise node and the Wise Trigger ship with n8n, so there is nothing to install and no add-on to buy. They behave the same on n8n Cloud, the hosted offer run by n8n, and on a self-hosted instance installed with Docker or npm under the Community Edition and its Sustainable Use license. A workflow built on one runs on the other without changes. What a Wise account itself involves is a separate question, settled with Wise and not covered here. The only cost to plan for is the hosting, if you self-host.
        02What credentials do you need to connect Wise to n8n?
        One API token, generated in Wise under user menu, Settings, API tokens. In n8n you create a Wise credential, paste it in the API Token field, and set Environment to Test for a Wise test sandbox account or Live for a real one. A third field, Private Key, stays optional until you call a live endpoint protected by Strong Customer Authentication: generate an RSA key pair, register the public key in Wise under Manage public keys, and paste the private key in the credential. The same credential is reused by the node and the trigger, and by every workflow in the instance.
        03What are the limits of the Wise node in n8n?
        The node covers 14 operations across 6 resources, which is wide but not complete. Recipients can be listed, not created, so the accounts you pay to must exist in Wise beforehand. A transfer is always built on a quote created first, then executed by a separate operation. On listings such as transfers or recipients, Return All decides whether the node walks every page of the API or stops at Limit. Anything the node does not expose stays reachable: the HTTP Request node calls the Wise endpoint directly and reuses the same credential through predefined authentication.
        04Does the Wise trigger react in real time?
        Yes. The Wise Trigger works by webhook, which means n8n exposes a URL and Wise calls it as soon as the event occurs. n8n registers that URL with Wise when you activate the workflow, and the event reaches the workflow within seconds. Nothing is fetched on a timer, so there is no frequency to tune and no delay to accept. Two things to keep in mind: the trigger is scoped to one profile through its Profile Name or ID parameter, and it listens to a single event among the 4 available, with no catch-all value. A workflow that needs several events carries several trigger nodes.
        05n8n or Make for Wise automation?
        It depends on where you want the data and how you want to pay. Make is hosted only and billed per operation, which suits a low volume with no infrastructure to run. n8n can be self-hosted with Docker or npm, so payment data stays on machines you control, and the same workflow also runs on n8n Cloud when you would rather not manage a server. For money workflows, self-hosting often wins on the audit question alone. Both let you build visually; n8n adds a Code node and the HTTP Request fallback when the Wise node stops short.
        Same platform

        Other docs you might need on this stack.

        Browse all integrations