Connect · free · runs in your browser
Your tools should talk to each other.
Pick what you use. See what could run on its own, and what we’d build first.
What do you use?
Pick a tool to begin.
A real run · made-up payments
One connection, tested until it broke.
A payment arrives and is booked in the accounts. We ran this workflow on n8n against a practice ledger, then switched the ledger off mid-run. These are the recorded results.
- A normal payment.Booked on the first try.
201 - The ledger drops out briefly.Retried, then booked once.
503 → 503 → 201 - The ledger stays down.2 runs stop after three tries each. Nothing is booked. One alert for 2 failures.
503 → 503 → 503 → 503 → 503 → 503 - The ledger comes back.The waiting payment is delivered again and booked once.
201 - A payment arrives twice.Counted as a repeat. Still one entry.
2 deliveries · 1 entry - Someone changes the amount.Refused before it reaches the ledger.
401
| Invoice | Amount | Times delivered | Entries |
|---|---|---|---|
| INV-2041 | €480.00 | 2 | 1 |
| INV-2042 | €1,250.50 | 1 | 1 |
| INV-2043 | €99.00 | 1 | 1 |
Download the workflowDownload the alert workflowRead the full receipt
Watch the workflow in the editor
A short, captioned walkthrough of the event ID, retry settings, error workflow and a fresh replay check. Fictional data and a practice ledger throughout.
Open or download the walkthrough (1 minute 47 seconds, 2 MB). Silent, with captions on screen. The demonstration signature is simplified; a production build needs the provider’s own verification.
10 recorded runs on n8n 2.46.6, on our own machine. No real payment provider or accounting tool was called. The signing key in the file is a demo value.