Integrations

n8n

Track n8n workflows - self-hosted or cloud - by calling the InfiniAnalytics API from HTTP Request nodes at each stage of your flow.

Requirements

  • An n8n instance (self-hosted or cloud)
  • An InfiniAnalytics account and API token
  • An automation UUID from the InfiniAnalytics dashboard

Workflow Template

Start from the official n8n community template - it already wires up the InfiniAnalytics HTTP calls around a Claude/Slack ticket-triage flow, ready to adapt to your own workflow:

View n8n Template

Setup

  1. 1

    Add credentials

    Create an HTTP header auth credential in n8n with your InfiniAnalytics Bearer token, so it can be reused across the Start/Event/End/Error request nodes.

  2. 2

    Generate the execution ID

    At the start of the workflow, add a Set node that generates an execution ID for this run:

    n8n expression
    {{ new Date().toISOString() }}
  3. 3

    Reference the execution ID in later nodes

    In every subsequent HTTP Request node (Event, End, Error), reference the same execution ID so all events are grouped into one execution:

    n8n expression
    {{ $('execution_id').first().json.execution_id }}
  4. 4

    Send lifecycle events

    Add HTTP Request nodes calling the InfiniAnalytics events endpoint at the start of the workflow (START), after each meaningful step (EVENT), and on the success/error branches (END/ERROR). See the API Reference for the request format.

  5. 5

    Wire up error handling

    Connect n8n's error trigger/branch to the same ERROR request node so failed executions are always recorded, even when the workflow throws partway through.

Multi-step workflows that call out to other technologies (e.g. a Python subprocess) can share the same execution ID across all of them - InfiniAnalytics stitches every event with the same ID into a single execution record.