Search all guides

Reference · Tools

Wise trigger

Receives webhook notifications from Wise for transfer state changes, balance credits, and balance updates to start a workflow.

Webhook trigger Finance v1

The Wise Trigger fires on the event you subscribe to — balance credit, balance update, transfer state change, or transfer active cases — with signatures verified for you. A typical build is reconciling an invoice the moment its payment lands in a Wise balance.

Works as
Webhook trigger
Tool name
wise_trigger
Parameters
2
Outputs
Output
Credentials
Wise
Official docs
Wise docs docs.wise.com

What you can build with Wise

  • Start a workflow when a Wise transfer status changes.
  • Trigger a notification when money is credited to a Wise balance.
  • When automate reconciliation when a Wise balance is updated.
  • Monitor transfer active cases for compliance review.

Overview

Receives webhook notifications from Wise (formerly TransferWise) when transfer or balance events occur. Supports four event types: balance credit, balance update, transfer state change, and transfer active cases update. Verifies webhook authenticity using RSA-SHA1 signature validation against Wise’s public key (separate keys for live and sandbox environments). Test notifications from Wise are acknowledged but not forwarded to the workflow. Requires a Wise profile ID to scope the webhook subscription. Useful for automating payment tracking, balance monitoring, transfer status notifications, and financial reconciliation workflows.

Node Type

Trigger — webhook (receives incoming HTTP callbacks)

Input / Output

DirectionPort(s)
InputNone (trigger node)
OutputOutput

Credentials

This tool requires Wise credentials. See the Credentials Guide for setup instructions.

Parameters

ParameterTypeRequiredDefaultDescription
Profile IDstringYes—The Wise profile ID to scope the webhook subscription to. Retrieve from your Wise account (personal or business profile).
EventoptionsYes—Which Wise event to listen for.
Options: balanceCredit (a balance account is credited), balanceUpdate (a balance account is credited or debited), transferActiveCases (a transfer’s list of active cases is updated), transferStateChange (a transfer’s status is updated)

Output Data

Each accepted notification produces one output item containing the full Wise payload exactly as it arrived, plus:

  • _trigger — always wise_webhook
  • _timestamp — ISO 8601 timestamp of when the notification was received
  • _webhookEvent — the payload’s event_type, falling back to trigger_on, or unknown when neither is present

Wise’s test notification pings are acknowledged but do not start the workflow.

Reference the payload downstream by expression, e.g. {{ $json.data.resource.id }}.

Example Configuration

React to transfer status changes:

{
  "type": "wise_trigger",
  "parameters": {
    "profileId": "12345678",
    "event": "transferStateChange"
  }
}

Notify when money arrives in a balance:

{
  "type": "wise_trigger",
  "parameters": {
    "profileId": "12345678",
    "event": "balanceCredit"
  }
}

Reconcile on every balance movement, credit or debit:

{
  "type": "wise_trigger",
  "parameters": {
    "profileId": "12345678",
    "event": "balanceUpdate"
  }
}

Review transfers that gain an active case:

{
  "type": "wise_trigger",
  "parameters": {
    "profileId": "12345678",
    "event": "transferActiveCases"
  }
}

Trigger Behavior

  • Activation: When the workflow is activated, a webhook endpoint is registered with the service.
  • Deactivation: The webhook is automatically unregistered when the workflow is deactivated.
  • Payload: The incoming webhook payload is parsed and output as workflow items.
  • Verification: Supports signature verification where applicable.

Tips

This tool detects events from Wise, such as balance changes or transfer status updates. It is the right tool when you need to start a workflow based on specific Wise financial activities, rather than polling or manual checks. It produces a trigger signal containing the verified Wise event data.

Frequently asked questions

Are the webhooks verified?

Yes — Wise signs all payloads using RSA-SHA1, and the trigger verifies them automatically with the right public key for your environment, live or test.

Which events are available?

Balance credit, balance update, transfer state change, and transfer active cases, chosen when configuring the trigger alongside a Wise profile ID.

Do test notifications work?

Test-environment notifications are verified against the corresponding test key, so sandbox testing behaves consistently with live.

Which credential does it need?

A Wise credential, the same one the action node uses.

Build with Wise

Drop it into a workflow, wire it to an agent, or call it on a schedule. You'll need Wise credentials first.

Open BusyBot

Last reviewed . Spotted something wrong? Tell us.