Log n8n workflows to Zambo

Every run gets a verifiable receipt your clients can check themselves. One HTTP Request node. No call, no workflow rewrite.

Heads up: this guide is verified against the live API schema, but the full end-to-end run with a real key has not been done yet. If you run it and anything differs, tell us at rambo-ops@agentmail.to and we will fix this page the same day.

1Get a Zambo key

Logging needs an authenticated key. Grab a Day Pass ($0.99, 24 hours): checkout, copy the key shown once. Running client work all month? The $29/month Zambo Pass gives you an ongoing key.

Store it in n8n as a Header Auth credential: name X-Zambo-Key, value your key. Do not paste the key directly into the node.

Verifying a receipt is always free and needs no account. Only logging needs the key.

2Add one HTTP Request node

Drop an HTTP Request node after the last step of your workflow. Set these switches first:

Setting	Value
Method	`POST`
URL	`https://zambo.dev/mcp`
Authentication	Generic Credential Type, Header Auth, your Zambo credential
Send Headers	On (handled by the credential)
Send Body	On
Body Content Type	`JSON`
JSON / Body	Expression mode (not fixed), paste the body below
Execute Once	On, so one run logs one receipt, not one per item

Body (n8n fills in your run details automatically):

{
  "jsonrpc": "2.0",
  "id": "n8n-{{$execution.id}}",
  "method": "tools/call",
  "params": {
    "name": "journal_log",
    "arguments": {
      "job_id": "n8n-{{$workflow.name}}-{{$execution.id}}",
      "tool_name": "{{$workflow.name}}",
      "executor_identity": "n8n",
      "metadata": {
        "workflow": "{{$workflow.name}}",
        "mode": "{{$execution.mode}}"
      }
    }
  }
}

Only job_id, tool_name and executor_identity are required. Everything else is optional. Raw inputs are never stored: if you pass inputs, Zambo hashes them, keeps the hash, and discards the rest. Do not put client names or anything sensitive in metadata: receipts are public.

3Share the receipt link

Run the workflow. The node's output confirms the entry and includes your receipt ID. Your client checks it at:

https://zambo.dev/run/YOUR_RECEIPT_ID

Or paste the id into zambo.dev/verify/. No account needed on their side.

The receipt is recorded with LOGGED BY AGENT provenance: it is your workflow's report, honestly labeled as such.

The honest scope

What verification checks: that the published bytes match the recorded hash. If the record was altered after the fact, verification fails.
What it does not prove: that your workflow ran correctly, that the model was right, or that an outside action (a payment, a booking, an email) actually happened.
Zambo records the report your workflow sends. It does not claim it ran or observed the workflow. The receipt is logged honestly as your report, which is exactly why a client can trust what it does say.

FAQ

Do my clients need Zambo accounts?
No. Verification links are public and free.

Does this slow down my workflow?
One extra HTTP call at the end of the run. Put it on the success branch, and optionally a second one on the error branch so failures are recorded too.

Can I log one receipt per client instead of per run?
Yes. Use a stable job_id per client engagement (for example client-acme-onboarding) and Zambo appends each run to that job timeline.

What if n8n already logs everything?
n8n logs are yours; your client has to take your word for them. A Zambo receipt is independently checkable: the client verifies the record themselves instead of trusting a screenshot.

Built by Zambo, the cross-AI execution layer. Questions? rambo-ops@agentmail.to