n8n¶
The community node n8n-nodes-lumatrack records one run event per workflow
execution. Drop it at the end of a workflow and the value report builds
itself.
Install¶
The package is being published to npm as n8n-nodes-lumatrack. Once the
listing is live you install it in n8n under Settings, Community Nodes,
Install by entering n8n-nodes-lumatrack; this page will drop this
notice when that lands. Until then, every n8n workflow can report through
plain HTTP with an HTTP Request node.
Credentials¶
Create a "LumaTrack API" credential:
| Field | Value |
|---|---|
| Base URL | Your LumaTrack host, e.g. https://lumatrack.example.com |
| API key | From Settings, API keys in LumaTrack (shown once at creation) |
Node fields¶
| Field | Notes |
|---|---|
| Automation slug | GET /api/v1/automations lists slugs; create automations in the app or API |
| Status | Success or Failure |
| External ID | Defaults to the n8n execution id, which makes retries idempotent automatically |
| Duration (seconds) | -1 omits the field; 0 is a real zero-second run |
| Metadata | Arbitrary JSON kept with the run; invalid JSON fails the node with a clear message |
The node honors n8n's Continue On Fail setting: with it enabled, a LumaTrack outage records an error item instead of failing your workflow.
Wire the error path too¶
One LumaTrack node at the end of the success path with Status = Success is half the integration. The other half: attach an error workflow (or an error branch) with a LumaTrack node set to Status = Failure. Failed executions cost money and save nothing; reporting them is what makes the reliability chart and the net numbers credible.
Many workflows, one automation?¶
Map them however your accounting works. If three workflows together replace one manual task, point all three at the same automation slug. If one workflow does two unrelated jobs, consider splitting it, or pick the slug per branch with an expression.