Back to Nodes

LumaTrack

Last updated Aug 22, 2026

Record automation run events in LumaTrack, the system of record for automation value.

187 Weekly Downloads
587 Monthly Downloads

Included Nodes

LumaTrack
LumaTrack Trigger

Description

n8n-nodes-lumatrack

Record every workflow execution as a run event in LumaTrack,
the system of record for automation value. Drop the node at the end of a
workflow (and on the error path, with Status set to Failure) and the value
report builds itself.

Install

A verified community node: on n8n Cloud, search for “LumaTrack” in the
nodes panel. Self-hosted: Settings, Community Nodes, Install, enter
n8n-nodes-lumatrack.

Credentials

  • API key: Settings, API keys in LumaTrack (shown once at creation)
  • Base URL: prefilled with https://lumatrack.io. Change it only if you run

LumaTrack on your own domain.

Fields

Two nodes ship in this package: LumaTrack (operations: Record Run,
Record Incident, Resolve Incident, Get ROI Summary; usable as an AI Agent
tool) and LumaTrack Trigger (starts workflows from LumaTrack webhook
events, signature-verified).

| Record Run field | Notes |
|—|—|
| Automation | Dropdown of your automations, or a slug by expression |
| Status | Success, Failure, Skipped or Cancelled. Report failures too: they cost money and save nothing. Skipped did no work; Cancelled was interrupted part way. Neither earns value and neither is counted as a failure |
| Reason | Why a run failed, did nothing, or was interrupted; each status keeps its own Pareto |
| Units from input items | One run for the whole execution, units = input item count (the after-a-loop pattern) |
| Units processed | Records/items the execution worked through; -1 omits (server default 1). Drives per-unit valuation |
| Executed at | ISO 8601 for evidence that happened earlier; empty = now |
| Duration (seconds) | Optional wall-clock runtime |
| External ID | Defaults to the n8n execution ID, making retries idempotent |
| AI usage | Model + tokens, priced server-side; metered or subscription billing |
| Metered usage | Per-unit cost-component consumption by name |
| Metadata | Arbitrary JSON kept with the run |
| Custom metadata | Your own name/value pairs, no hand-written JSON; merged over Metadata on a shared key |
| Additional fields → Source | Reporting system stored on the run; defaults to n8n |
| Additional fields → Manual run | Records a real manual execution as evidence, valued as opportunity cost, never as automation savings |

Record Incident reports one loss event (ticket, outage, truck roll) to
the loss ledger: pick an event type, optionally add measured downtime, a
cost override, and an occurred-at for evidence that happened earlier. The
External ID default (execution ID + item index) keeps retried deliveries
from double-counting while a batch of N alerts still books N incidents.
Resolve Incident stamps an incident resolved (by its evt_… ID) and
records its total measured downtime. Responses flow through as items; a
non-empty ignored_fields in a response means a misspelled field, never a
silent success.

The trigger node verifies X-LumaTrack-Signature (HMAC-SHA256 of the exact
body) with your webhook endpoint’s secret; register the trigger’s URL in
LumaTrack under Settings, Webhooks. Its event filter covers the full
outbound catalog, including incident recorded/resolved and initiative
implemented/transitioned events.

Sub-workflows report as their own executions (their execution IDs are the
idempotency default). A node inside a loop dedupes every iteration into one
run; aggregate first and report once with Units processed, or set External
ID to ={{ $execution.id }}-{{ $itemIndex }}.

Build from source: npm install && npm run build.