Integration

n8n

The n8n-nodes-stillrunningcommunity node reports your workflow's health to StillRunning from inside n8n. You find out the moment a workflow fails silently, never fires, freezes, or gets stuck in the queue, the failure modes n8n can't alert you about because no execution record is ever written.

Everything pushes out from inside your workflow. StillRunning never pulls from, authenticates to, or stores credentials for your n8n instance.

Install

In n8n: Settings → Community Nodes → Install and enter n8n-nodes-stillrunning. Or from the command line for a self-hosted instance:

npm install n8n-nodes-stillrunning

Tier 1 — no credentials beyond your token (~30s)

1. Create a workflow at stillrunning.ai/app/new and copy its ping token. 2. In n8n, add a StillRunning API credential and paste the token. 3. Add the node where you need it:

Success path — drop a StillRunning node at the end of your workflow, operation Report Success. Drag a direct LLM node's output into the optional token/cost/model fields to track AI spend.

Failure path — in your workflow's Error Workflow, add a StillRunning node, operation Report Failure. Leave Read Error From Input on, it reads the failed node and error message straight from the Error Trigger payload. No key needed.

Operations

Report Success — pings success with optional duration, tokens, cost, model, and tool calls.
Report Failure — pings fail with the failed node + error message (auto-read from the Error Trigger).
Heartbeat— a bare "still alive" ping for long-running or step-based jobs.

Every ping carries source: "n8n" and the n8n executionId.

Tier 2 — full enrichment for AI Agent workflows

n8n's AI Agent node drops token usage from its output wire (a documented n8n limitation), so the wired token/cost fields only flow from direct LLM nodes. To capture cost and per-node timing for Agent workflows, use the enrichment template: it calls GET /executions/{id} inside your own n8n with a local credential, the key never leaves your instance, then pushes the enriched result to StillRunning.

Import the template (ships in the package at templates/error-workflow-enrichment.json), set it as your workflow's Error Workflow, and create two credentials inside n8n: an httpHeaderAuth credential named X-N8N-API-KEY with your n8n API key (Settings → n8n API), and your StillRunning ping token. The template:

Error Trigger
  → Get Execution   (GET /api/v1/executions/{id}?includeData=true, local n8n key)
  → Build Payload   (Code: failed node, error, per-node timing, token usage)
  → Push to StillRunning   (POST /api/ping/{token}?event=fail)

The execution record carries each node's executionStatus, executionTime, and output, so the failed node and per-node timing are reliable. Token usage paths vary by provider; the template extracts them best-effort and StillRunning records what it receives.

Monitoring never breaks your workflow

If a ping itself fails (network blip, StillRunning down), the node reports it on its output item (stillRunning.ok = false) and passes your data through, it never throws into the workflow it's monitoring.