Get Account Requirements

wise.get_account_requirements
ActionBusiness appsconnection required

Calls the Wise API with the connection's credentials.

Ask Wise which recipient fields a quote's route actually needs, so a recipient can be built for that currency and payout method rather than guessed.

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

3 fields, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
quote_id
The quote whose route the requirements are for.
stringYes———
originator_legal_entity_type
Legal entity type of the actual sender, which correspondent partners must supply.
stringNo—one of "BUSINESS", "PRIVATE"—
address_required
Set true to have Wise mark the recipient address required even when the route does not demand it.
booleanNo———

Output

One shape.

result

FieldTypeExample
items
The records Wise returned for this request.
array—
count
How many records are in 'items'.
number—
types
The requirement group identifiers, one per supported account type.
array—
{
  "count": 0,
  "items": [],
  "types": []
}

See Get Account Requirements 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.