Before · what we sent in
- 3 made-up payments, €480.00, €1,250.50, €99.00.
- 1 payment delivered twice.
- The accounts system answered “unavailable” 8 times.
- 2 bad messages: one with the amount changed, one with details missing.
A payment arrives and is booked in the accounts. We switched the accounts system off halfway to see what the workflow does.
A demo on practice data, with made-up payments. Not a client’s system.
Before · what we sent in
After · what the accounts held
| Invoice | Amount | Times delivered | Entries |
|---|---|---|---|
| INV-2041 | €480.00 | 2 | 1 |
| INV-2042 | €1,250.50 | 1 | 1 |
| INV-2043 | €99.00 | 1 | 1 |
Read the full recorded resultsDownload the workflowDownload the alert workflow
10 recorded runs on n8n 2.46.6, on our own machine. The check that a payment message is genuine is simplified here. A real build uses the payment provider’s own check.
GuraForge is a new studio. When a client lets us publish a measured result, it goes on this page. Until then, this test is what we can show.
Get a free check