Reference · Tools
Wise Trigger
Starts workflow when Wise (TransferWise) events occur via webhooks
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.
- Node type
- Webhook trigger
- Parameters
- 2
- Outputs
- Output
- Credentials
- Wise
Wise Trigger
Triggers on Wise transfer state changes, balance credits, and balance updates
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.
Category: Finance
Tool Name: wise_trigger
Version: 1
Appearance: Icon: si-wise | Color: #9fe870
Node Type
Trigger — webhook (receives incoming HTTP callbacks)
Input / Output
| Direction | Port(s) |
|---|---|
| Input | None (trigger node) |
| Output | Output |
Credentials
This tool requires Wise credentials. See the Credentials Guide for setup instructions.
Parameters
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
| Profile ID | string | Yes | — | The Wise profile ID to scope the webhook subscription to. Retrieve from your Wise account (personal or business profile). |
| Event | options | Yes | — | 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— alwayswise_webhook_timestamp— ISO 8601 timestamp of when the notification was received_webhookEvent— the payload’sevent_type, falling back totrigger_on, orunknownwhen 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 }}.
Usage Examples
- Start a workflow when a Wise transfer status changes
- Trigger a notification when money is credited to a Wise balance
- Automate reconciliation when a Wise balance is updated
- Monitor transfer active cases for compliance review
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
Entry point that fires when Wise sends a webhook for subscribed events. Configure a Wise profile ID and select the event type to listen for: balance credit, balance update, transfer state change, or transfer active cases. Wise signs all webhook payloads using RSA-SHA1; the trigger verifies signatures automatically using the appropriate public key for your environment (live or test). Test notification pings from Wise are acknowledged but do not trigger workflow execution.
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 the Wise Trigger node
Drop it into a workflow, wire it to an agent, or call it on a schedule. You'll need Wise credentials first.
Open BusyBotLast updated . Spotted something wrong? Tell us.