Skip to main content
Start free

Docs

Connect n8n

Give NoCrash a read-only key to pull your run history, then drop in one node to see every single run.

The short version

You connect n8n in two layers. The first takes a minute and watches your whole instance. The second is one node you add to a workflow when you want NoCrash to see each run as it happens. You can do just the first, or both.

Layer 1 — connect your instance

This lets NoCrash pull your run history so it can spot a workflow that quietly stopped.

  1. In n8n, create an API key. In NoCrash, open Add something to watch → n8n and paste two things: your n8n instance address and that API key.
  2. NoCrash only ever reads. The key needs permission to list workflows and read executions — nothing that can change or run anything. The connect screen shows the exact permissions inline.
  3. Save. NoCrash checks your instance on a schedule and starts watching the workflows it finds.

Your API key is stored encrypted and is never shown back to you in full.

Layer 1 sees that a workflow ran. The node lets NoCrash see each run — including the ones that fail a step partway through.

  1. In n8n, install the community node n8n-nodes-workflow-monitor from the community nodes screen.
  2. Drop the node at the end of the workflow you care about.
  3. Paste your NoCrash API key into the node’s credential field.
  4. Save and run the workflow once. NoCrash receives the run and the workflow turns green.

After that, every run pings NoCrash on its way out — so a run that fails a step shows up as red, not as silence.

Confirm it’s working

Open NoCrash. The workflow appears in your list with a coloured dot:

  • Green — it’s running and finishing cleanly.
  • Yellow — something’s worth a look.
  • Red — it broke.

If a workflow you expected isn’t there yet, give the next scheduled check a moment, or use Refresh now to pull immediately.

If your API key expires

n8n lets you create API keys that expire — some after 30 days. When a key expires (or you revoke it), NoCrash can no longer reach your n8n, and the workflows it was watching would otherwise go quiet.

You don’t have to remember the date. The moment a key stops working, NoCrash tells you — on the connection, in your daily brief, and through your alerts — with a one-tap link to add a new one. Monitoring never silently stops; you just paste in a fresh key and we pick up right where we left off.

To avoid the interruption entirely, you can create a key with no expiration in Settings → API.

If your n8n is private

If your n8n sits behind a firewall or Cloudflare, NoCrash needs permission to reach it. See Reaching protected endpoints.