Get Recipient
wise.get_recipient
ActionBusiness appsconnection required
Calls the Wise API with the connection's credentials.
Retrieve one recipient account by id, with the bank details Wise holds for it and whether it is still active.
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
1 field, 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 |
|---|---|---|---|---|---|
account_id The recipient account id. | string | Yes | — | — | — |
Output
One shape.
result
| Field | Type | Example |
|---|---|---|
recipient The full recipient account object Wise returned. | object | — |
account_id The recipient account id, used as a transfer's target. | string | — |
currency Currency this recipient account is denominated in. | string | — |
type Account type for the route, such as iban or sort_code. | string | — |
active Whether Wise still considers this recipient usable. | boolean | — |
account_holder_name The recipient's full name as held by Wise. | string | — |
account_summary Wise's short human-readable description of the account. | string | — |
{
"account_holder_name": "",
"account_id": "",
"account_summary": "",
"active": false,
"currency": "",
"recipient": {},
"type": ""
}See Get Recipient 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.