Zapier integration

Zapier connects TrainAR to 7,000+ apps through "Zaps" — automations that listen for an event in one app and fire an action in another. With TrainAR + Zapier, you can trigger any Zap on a TrainAR event (a session completed, a task created, a skill executed) without writing code.

Status: The TrainAR app is live for internal use and submitted to the Zapier marketplace for editorial review. While that review is in progress, you can use it through a private invite link — contact us if you'd like access. Once Zapier completes their review, the app will be searchable directly inside Zapier.

What you can do with TrainAR + Zapier

Trigger Zaps on:

Trigger	Fires when
Task created	A new task appears in TrainAR (manually, via API, or from an integration).
Task status changed	A task moves between open / in_progress / completed / cancelled.
Task completed	A task is marked completed.
Session started	An engineer begins a training session on the glasses.
Session completed	A session ends — payload includes score, duration, video URL, AI summary.
Skill executed	The on-glasses AI assistant called one of your custom skills.

Common Zap recipes:

• Session completed → post score + video link to a Slack channel.
• Task completed → mark the matching row complete in your spreadsheet.
• Session started → notify the trainer's supervisor by email.
• Skill executed → log to a Google Sheet for auditing.
• Task created (from ServiceM8) → message the assignee on WhatsApp.

Actions (creating tasks, inviting users, executing skills from Zapier) aren't in the current Zapier app — they're in the n8n integration instead. We'll add them to Zapier when the marketplace listing goes public.

Setup

You'll need:

• Admin access to TrainAR.
• A Zapier account on any plan that supports webhook triggers.

1. Create a TrainAR API key

1. TrainAR Dashboard → Settings → API Keys → New API Key.
2. Give it a descriptive name like Zapier integration.
3. Tick the manage:webhooks permission scope. (No other scopes needed for triggers.)
4. Click Generate. Copy the key now — it starts with tak_ and is shown only once.

2. Create a Zap that uses TrainAR

1. In Zapier, click + Create to start a new Zap.
2. For the trigger app, search TrainAR and select it.
3. Choose the trigger event (e.g. Session Completed).
4. When prompted to Connect a new account, paste your TrainAR API key.
5. Zapier registers a webhook with TrainAR. You'll see a confirmation back in TrainAR → Dashboard → Integrations → Zapier card — the new endpoint appears as an active connection.
6. Continue building your Zap — map the TrainAR fields to the action app of your choice.
7. Test the Zap with sample data, then turn it on.

3. Verify it's working

In TrainAR, do something that fires the trigger event (e.g. complete a test session). Within seconds you should see the Zap fire in Zapier's task history.

Managing connected Zaps

Open TrainAR → Dashboard → Integrations → Zapier card to see all the Zap webhook endpoints registered against your tenant, with delivery status for the last fired event on each.

You can revoke individual endpoints from here — useful if a Zap was turned off in Zapier but you want to confirm it's no longer receiving TrainAR events.

Troubleshooting

Zap isn't triggering. Check the Zapier card in TrainAR — if the webhook endpoint doesn't appear, the OAuth handshake didn't complete. Reconnect in Zapier.

Authentication error in Zapier. Your API key may lack the manage:webhooks scope. Regenerate a key with that scope and reconnect.

Zap fires but data fields are empty. The trigger event payload changed in a TrainAR update. Re-pull sample data in Zapier (the editor offers a "Refresh fields" option) and re-map.

I'm seeing a deprecation warning. The Zapier app v1.0.1 used an older webhook-subscribe endpoint that's being phased out. Upgrading the Zap (it'll auto-prompt) migrates it to the current endpoint.

Privacy

Zapier only receives the event payloads it subscribes to. The payload shapes for each event are documented under Build your own integration — same content TrainAR sends to Zapier is what's documented there.

You can disconnect Zapier at any time from the Integrations card or by deleting the Zap in Zapier. All connected endpoints stop receiving TrainAR events immediately.