n8n integration

n8n is a self-hostable workflow automation platform. The TrainAR community node lets you trigger n8n workflows from TrainAR events and call TrainAR's API from inside any workflow — both directions, both triggers and actions.

Status: Available now on self-hosted n8n. Install via Settings → Community Nodes. The same node will be one-click installable on n8n Cloud once n8n's verification process completes (already submitted).

What you can do with TrainAR + n8n

The community node ships one trigger (6 events) and one action node (6 operations across 3 resources):

Trigger events (TrainAR → n8n):

Event	Fires when
task.created	A new operational task is created in TrainAR.
task.status_changed	A task changes status (open / in_progress / completed / cancelled).
task.completed	A task is completed.
session.started	An engineer starts a training session on the glasses.
session.completed	A training session ends — payload includes score, duration, video URL, AI summary.
skill.executed	A skill was executed on the glasses (success or failure).

Action operations (n8n → TrainAR):

Resource	Operation	What it does
Task	Create	Create a new operational task
Task	Update Status	Move a task between open / in_progress / completed / cancelled
Task	Find	List recent tasks (with optional title filter)
User	Invite	Send an invitation email to a new user in your tenant
User	Find	List users in your tenant
Skill	Execute	Run a TrainAR skill server-to-server (auto-resolves session context)

Install on self-hosted n8n

You'll need:

• A self-hosted n8n instance running n8n 1.0.0+ and Node.js 20+.
• Admin access to TrainAR.

1. Install the community node

1. In n8n, go to Settings → Community Nodes → Install.
2. Paste n8n-nodes-trainar and click Install.
3. Wait for the install to complete and reload n8n.

After reload, TrainAR Trigger and TrainAR action nodes appear in the node panel.

2. Create a TrainAR API key

1. TrainAR Dashboard → Settings → API Keys → New API Key.
2. Tick the scopes the workflows will need:
   • manage:webhooks — required for the Trigger node.
   • read:tasks, write:tasks — for Task Find / Create / Update Status.
   • read:users, manage:users — for User Find / Invite.
   • read:skills, write:skills — for Skill Execute.
3. Click Generate and copy the key (starts with tak_).

3. Add the credential in n8n

1. In n8n, Credentials → New → TrainAR API.
2. Paste your API key. Save.

4. Build your first workflow

Drag a TrainAR Trigger node onto the canvas, select the event(s) you want to listen to, then connect downstream nodes. When you save and activate the workflow, n8n registers a webhook with TrainAR — you'll see the active endpoint listed under TrainAR Dashboard → Integrations → n8n card.

Public URL requirement for triggers

n8n triggers register a webhook URL with TrainAR. TrainAR validates that the URL is reachable from the public internet before accepting the subscription. This means:

• Production n8n on a public domain — works out of the box.
• Local development (http://localhost:5678) — won't work directly. Use a tunnel:

  cloudflared tunnel --url http://localhost:5678
  

  Then set the environment variable WEBHOOK_URL=<tunnel-url> and restart n8n so it advertises the public URL to TrainAR.

n8n Cloud

n8n Cloud doesn't currently let you install arbitrary community nodes — it only ships nodes that have completed n8n's verification process. The TrainAR node is in that verification queue. Once it's approved, you'll be able to add the TrainAR node from n8n Cloud's node panel with one click, no install required.

We'll update this page when verification is complete.

Managing connected workflows

TrainAR Dashboard → Integrations → n8n card shows every n8n webhook endpoint your tenant has registered, with the workflow it's associated with and the last event delivered. You can revoke endpoints from here if you've turned off the workflow in n8n but want to make sure no further events are delivered.

Troubleshooting

"Failed to create webhook endpoint" when activating a Trigger workflow. The webhook URL n8n is presenting isn't publicly reachable. If you're on localhost, set up a tunnel and configure WEBHOOK_URL.

Actions silently return input items unchanged. You may be on an older version of the community node. The current version is 1.0.2. Update via Settings → Community Nodes and reload.

manage:webhooks permission error. The API key was generated without the right scope. Regenerate with the correct scopes ticked.

Skill Execute returns 403. The API key lacks the write:skills scope. Regenerate with write:skills enabled.

Trigger fires but payload fields are missing. TrainAR event payloads are flattened so n8n shows top-level fields directly. If you're expecting a nested field that isn't appearing, check the Webhooks reference for the full payload shape per event.

Where to find the source

The community node is open source. Code, contribution guide, and changelog at github.com/Train-AR/n8n-nodes-trainar. Issues, feature requests, and PRs welcome.

Privacy

Each trigger event payload is sent only to the n8n webhook URL it's registered against. The action operations call TrainAR's Tenant REST API on your behalf — they can only do what your API key's scopes allow.

Disconnect at any time by removing the credential in n8n or revoking the API key in TrainAR. All webhook endpoints associated with that key stop receiving events.