Via HTTP · Automation

n8n, in every client’s workflows.

Start an n8n workflow, with the client’s own n8n account.

Triggers: 0start a workflow
Recipe: 1one web request step

Via HTTP

Start an n8n workflow, with one step

Keep a client’s existing n8n workflow, and let Thrum start it, watch it and report on it. The web request step, filled in: paste it, swap in the client’s ids, add their key.

Run against n8n itself on 1 October 2026.

01
Add the client’s credential
On the client’s page in Thrum: Add credential, type Other (JSON). In n8n: add a Webhook node, method POST, Authentication “Header Auth” with the name X-Formit-Secret and a long random value, then publish the workflow (activate, before n8n 2) and copy its Production URL. Store both here.
```
{
  "url": "https://n8n.example.com/webhook/…",
  "secret": "…"
}
```

Add a web request step

Name it “Start the n8n workflow”, set it as here, and pick the credential. Values in double braces are read from the run: here, the lead the form brought in.

{
  "method": "POST",
  "url": "{{ credential.url }}",
  "headers": {
    "X-Formit-Secret": "{{ credential.secret }}"
  },
  "body": {
    "name": "{{ lead.name }}",
    "email": "{{ lead.email }}",
    "phone": "{{ lead.phone }}",
    "request": "{{ lead.summary }}",
    "lead_url": "{{ lead.url }}"
  }
}

What goes out, and what comes back

Use the Production URL, which works only while the n8n workflow is published; the Test URL works once, while the editor listens.

POST https://n8n.example.com/webhook/0a1b2c3d-new-lead
content-type: application/json
x-formit-secret: ••••••••

{
  "name": "Nadia Karim",
  "email": "nadia@example.com",
  "phone": "+447700900222",
  "request": "Quote for a new bathroom, two basins and a shower",
  "lead_url": "https://portal.northsideplumbing.co.uk/leads/0f9a2c"
}

200
{
  "message": "Workflow was started"
}

Watched like everything else

When n8n stops answering or refuses the client’s key, you hear about it, and your client does not.

A failing request: Tried 3 times, 5 seconds apart and doubling, only for errors a retry can fix
A service that asks for a pause: Given it, up to an hour
Requests at once, per account: 2, per worker; the rest wait their turn
Timeout: 15 seconds, unless the step sets its own
Private and internal addresses: Refused, on every redirect too
The client’s key: Encrypted, bound to the client, and kept out of every run record
A step that keeps failing: Marks the workflow Degraded and alerts you, not the client

n8n and its logo are trademarks of their owner, used here only to say what Thrum works with; no endorsement is implied.

Thrum is cooking.

Get early access and you’ll be among the first in. Early members get a launch perk.

Get early access See pricing