TriggerWiseReal-timeUpdated May 2026
How do I trigger on Wise transfer state changes?
Short answer: Drop the "Wise → Transfer State Changed" trigger on your workflow canvas, add filters if you want them, and publish. It fires within seconds of the event in Wise, not on a polling schedule.
Anatomy
What this trigger looks like in a workflow.
Drop it on the canvas. Configure a couple of fields. Publish.
In the builder
Trigger
Transfer State Changed
When the matching event happens
when transfer state changedon transfer state changedtransfer state modifiedtransfer state changedwhen a wise transfer state changeswatch for transfer state changednew transfer state changed
What this trigger returns
for the curiousYou don’t need to read this. Tiny Command auto-maps every field into the visual picker so downstream nodes can pull values by clicking. We show it here for power users who want to know what’s on the wire.
{"event": "transfers#state-change","state": "outgoing_payment_sent","transfer_id": 12345}
Output shape
Fields available to downstream nodes.
Every field below can be referenced by name in any action or filter that comes after this trigger.
| Field | Type | Example |
|---|---|---|
| event | string | "transfers#state-change" |
| state | string | "outgoing_payment_sent" |
| transfer_id | number | 12345 |
Pairs with
Drop these actions after Transfer State Changed.
FAQ
Questions about Transfer State Changed.
How does the Transfer State Changed trigger work in Wise?
Fires whenever a Wise transfer changes state (incoming_payment_waiting, processing, funds_converted, outgoing_payment_sent, cancelled). Use to give end-customers visibility or to settle internal ledgers.
Is the Transfer State Changed trigger real-time?
Yes. Transfer State Changed uses webhooks or push subscriptions, not polling. Your workflow fires within seconds of the event happening in Wise.
What data does Transfer State Changed return?
The full event payload from Wise. The output shape table on this page lists every field, its type, and an example value so you can map fields into downstream nodes.
Can I filter Transfer State Changed so only some events start a workflow?
Yes. Add a Filter node right after the trigger and match on any field, whether that's subject, sender, status, or anything else in the payload. Workflows only continue when the filter passes.
Do I need Wise admin permissions to use Transfer State Changed?
For most Wise accounts a standard user can authorize the trigger. Some Wise plans require an admin to enable third-party webhooks. Check Wise's docs if the trigger fails to register.
More triggers
Other Wise triggers.
Trigger
Balance Credited
Fires when a Wise multi-currency balance is credited. Use it to auto-reconcile customer payments, post to your accounting system, or notify finance in real-time.
TriggerTransfer Issue
Fires when a Wise transfer has an active issue (compliance hold, invalid recipient details, refund). Use it to alert ops and unblock the transfer quickly.
Build a workflow on this trigger.
One trigger. 3+ downstream actions. Zero glue.
