Skip to content
GuraForge

One we built, then tried to break.

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.

Watch it run

1 minute 47 seconds. Silent, with captions. Open or download the video.

Before and after the test

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.

After · what the accounts held

  • 3 entries. Each payment booked once, with the right amount.
  • 1 alert to the owner, covering 2 failed runs.
  • Both bad messages refused. Neither was booked.
  • 0 emails sent to customers. No real payment or accounting tool was touched.
The practice accounts after the test
InvoiceAmountTimes deliveredEntries
INV-2041€480.0021
INV-2042€1,250.5011
INV-2043€99.0011

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.

No client results yet

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