Fund Transfer
wise.fund_transfer
ActionBusiness appsconnection required
Calls the Wise API with the connection's credentials.
Pay for a created transfer from a Wise balance or a pre-funded settlement account, which is what actually sets the money moving.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- Bearer token
- Providers
- Wise
- Secret shape
- the Wise API token, or {"api_token": "…"}
- Config it needs
- base_url, api_version, profile_id
- Resolved by
- config.connection_id, else node.connection_id
Configuration
5 fields, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
transfer_id The transfer id to fund. | string | Yes | — | — | — |
funding_type How the transfer is paid for: from a Wise balance, or from a pre-funded settlement account per transaction or in bulk. | string | No | BALANCE | one of "BALANCE", "TRUSTED_PRE_FUND_TX", "TRUSTED_PRE_FUND_BULK" | — |
balance_id The balance to debit when funding from a Wise balance. Wise picks the matching balance when this is blank. | number | No | — | ≥ 1 | — |
partner_reference Your own payment reference, which the pre-funded settlement models require and Wise echoes back. | string | No | — | — | — |
profile_id Act for this Wise profile instead of the one on the connection. | string | No | — | — | — |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"funding_type": "BALANCE"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
status COMPLETED when the transfer is paid for, CREATED when Wise accepted the funding but has not settled it, REJECTED when it refused. | string | — |
funded True only when the status is COMPLETED. | boolean | — |
pending True when the status is CREATED and settlement is still to come. | boolean | — |
error_code Wise's machine-readable reason for a rejection, such as balance.insufficient-funds or transfer.invalid-state. | string | — |
error_message Wise's developer-facing explanation of a rejection. It is not localised, so do not show it to an end customer. | string | — |
funding_type The funding model Wise applied. | string | — |
balance_transaction_id The balance transaction Wise created to settle the transfer. | number | — |
partner_reference Your payment reference, echoed back. | string | — |
result The full funding response exactly as Wise returned it. | object | — |
{
"balance_transaction_id": 0,
"error_code": "",
"error_message": "",
"funded": false,
"funding_type": "",
"partner_reference": "",
"pending": false,
"result": {},
"status": ""
}Notes
- Wise answers 201 for all three outcomes, so this node succeeds on a rejection too — branch on 'status' or 'funded', not on the step failing.
See Fund Transfer run in a workflow.
In a technical demo we add the Wise connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.