Workflows
Design how disputes move through your platform on a visual canvas - webhook triggers, API calls, conditions, widget actions, and Chargeflow engine actions, with presets to start from.
Workflows is where you design what happens to a dispute inside your platform: which events trigger what, which calls run, and which engine actions fire.
Beta
Workflows are in beta. Availability is set per platform by your Chargeflow account manager. See Support to get access.
The canvas
Drag nodes, connect them, and simulate the flow before it runs against real disputes.
| Node type | What it covers |
|---|---|
| Webhooks | dispute.created, alert.created, evidence.ready |
| API calls | Calls out to your own services |
| Conditions and delays | Branch on dispute data, or wait |
| Widget actions | What a merchant clicking in an embedded widget triggers |
| Engine actions | Score dispute, generate evidence, deflect alert, sync disputes |
Presets
Four starting points, each a complete flow you can edit rather than a blank canvas:
| Preset | What it does |
|---|---|
| Evidence generation (EaaS) | Dispute in, evidence generated, evidence returned |
| Auto-evidence submission | Generate and submit without a human step |
| Merchant onboarding | The sequence that takes a merchant from invited to routing disputes |
| Alert auto-deflection | Receive an alert and resolve it before it becomes a chargeback |
Simulate before you ship
The simulate step is the difference between a workflow and an outage. Dispute flows touch deadlines and money, so run the flow against sample data and confirm the branch you expect actually fires before enabling it on live merchants.