Triggers, actions and searches
Three triggers, two actions, two searches - everything you need to wire TrainAR sessions and tasks into the rest of your operational stack.
Triggers (TrainAR fires, Zapier listens)
- Task created — fires when a new operational task is created in TrainAR (event:
task.created) - Task status changed — fires when a task moves between open / in_progress / completed / cancelled (event:
task.status_changed) - Session completed — fires when a training session completes, with the session payload (event:
session.completed)
Actions (Zapier writes into TrainAR)
- Create task — POST to TrainAR's tenant tasks API with title, description, priority, due date, assignee, external ID
- Update task status — PATCH a task by ID with new status, plus optional title / description / priority / assignee
Searches (Zapier looks up data in TrainAR)
- Find user — by email or full name
- Find task — by title or external ID
Authentication is API-key based. Generate a key in your TrainAR settings, paste into Zapier's connection setup, done.
Three Zaps you can build today
Set up in five minutes. The same triggers power thousands more.
Session completed → Slack
When an engineer finishes an AR session on the glasses, post a summary to your #ops Slack channel.
TrainAR: Session completedSlack: Post message
Session completed → Google Sheet
Append every completed AR session to a shared spreadsheet for finance or weekly reporting.
TrainAR: Session completedGoogle Sheets: Add row
Email or form → TrainAR task
When a customer email or web form arrives, create a TrainAR task automatically with title, description and priority.
Gmail / Typeform: New itemTrainAR: Create task
What's coming next
Already in the build queue and shipping as the underlying webhook surface expands.
- More triggers:
task.completed,session.started,skill.executed - Assign task to user action
- List recent sessions search
- Public Zapier marketplace listing