Logproof

Install, ten minutes to the first row

Your flow tells Logproof what it did with one HTTP call per run. Nothing else changes in the flow.

1. Get a key

Open Settings in your workspace, create a key and copy it. The key is shown once.

2. Post a run with curl

Try it from your own machine first, so you see a row appear.

curl -X POST https://runledger-aarons-projects-25c3a9c9.vercel.app/api/v1/runs \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "flow": "Lead follow-up drafts",
    "summary": "Drafted 6 follow-ups for leads older than 5 days",
    "source": "n8n",
    "risk": "low",
    "status": "ok"
  }'

The reply is { id, status, approve_url }. Reload your log and the row is there.

3. The same call as an n8n node

Add an HTTP Request node at the end of your flow. Method POST, URL https://runledger-aarons-projects-25c3a9c9.vercel.app/api/v1/runs, one header Authorization: Bearer YOUR_API_KEY, body type JSON. Or paste this node straight into the canvas.

{
  "name": "Logproof log run",
  "type": "n8n-nodes-base.httpRequest",
  "typeVersion": 4.2,
  "parameters": {
    "method": "POST",
    "url": "https://runledger-aarons-projects-25c3a9c9.vercel.app/api/v1/runs",
    "sendHeaders": true,
    "headerParameters": {
      "parameters": [
        { "name": "Authorization", "value": "Bearer YOUR_API_KEY" }
      ]
    },
    "sendBody": true,
    "specifyBody": "json",
    "jsonBody": "={{ JSON.stringify({ flow: 'Lead follow-up drafts', summary: 'Drafted ' + $items().length + ' follow-ups', source: 'n8n', risk: 'low', status: 'ok', external_id: $execution.id }) }}",
    "options": {}
  }
}

4. Wait for a person on risky steps

Post the run with risk: "high". It lands at the top of the log as Needs approval and nothing else happens until someone taps Approve or Reject. Your flow can learn the decision two ways.

Option A, a callback

In n8n add a Wait node set to On webhook call, copy its resume URL and pass it as callback_url. Logproof posts the decision to that URL and your flow carries on.

curl -X POST https://runledger-aarons-projects-25c3a9c9.vercel.app/api/v1/runs \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "flow": "Invoice reminders",
    "summary": "About to email 14 clients with overdue invoices",
    "risk": "high",
    "callback_url": "https://your-n8n/webhook-waiting/abc123"
  }'

Option B, poll

Add a Wait node of 60 seconds, then an HTTP Request node that reads the run, then an IF node. Loop back to the Wait node while the status is still pending_approval.

curl https://runledger-aarons-projects-25c3a9c9.vercel.app/api/v1/runs/RUN_ID \
  -H "Authorization: Bearer YOUR_API_KEY"

# { "id": "...", "status": "approved", "decision_note": "Go ahead", "decided_at": "..." }

Field reference

  • flow required. The name a person would use, for example Invoice reminders.
  • summary required. One plain sentence a business owner understands.
  • risk low or high. High means the run waits for approval.
  • status ok or failed. Ignored when risk is high.
  • source, external_id, payload, callback_url optional. Payload is capped at 32 KB and fields named password, token, secret, authorization and api_key are replaced before storage.
  • Rate limit, 60 requests per minute per key.