Tasks · Last updated 4 November 2026 · 4 min read

Tasks → sessions writeback

When an engineer completes a training session against a task, TrainAR can push the outcome back to the source field-service system as a job note.

When an engineer completes a training session against a task, TrainAR can push the outcome back to the source field-service system as a job note. This is the "writeback" step - it lets dispatch and customer-success see the work landed in their FSM without anyone copy-pasting.

What writeback does

When a session completes, TrainAR fires a session.completed event for the linked task. If writeback is enabled on the source integration, the system posts a note to the corresponding job in the FSM.

The note carries:

  • The task title
  • Who completed it (name and email)
  • What was recorded, for example "Procedures recorded: 3"
  • How long the session took, and when it finished
  • A link to the session's page in your TrainAR dashboard
  • Any completion notes

Lines with missing data are left out.

Files go with the note. Completed form PDFs (job sheets, certificates) and the photos taken during the session are attached to the job:

Platform How files arrive
ServiceM8, Simpro, Commusoft, Payaca Attached to the job
Jobber Attached to the job note
Powered Now Form PDFs as documents, photos as images on the job
BigChange As links in the note (its API does not accept files)

If a platform ever refuses an attachment, TrainAR posts the files as links in a note instead, so nothing is lost.

Note

Writeback never changes the job's status, stage, or pipeline position. TrainAR won't close, reopen, or move your jobs - that stays your team's call, in your FSM.

Per-FSM endpoint

The writeback hits a different API path depending on the FSM:

FSM Endpoint shape
ServiceM8 customers/{customerId}/jobs/{jobId}/jobnotes
Simpro /api/v1.0/companies/{companyId}/jobs/{jobId}/notes/
Jobber Job note + note attachments via GraphQL
Commusoft Job note via REST
BigChange Job note via REST
Payaca Project note + file attachments via REST
Powered Now Job note + documents and images via REST

TrainAR authenticates via the token that's stored when you connected the integration. You don't configure endpoints - they're carried by the integration definition.

When writeback fires

The trigger is session completion. The post-session pipeline finishes (recording uploads, procedures extracted, summary generated), then writeback fires.

There's a single retry workflow (process-writeback-retries) that re-attempts failed writebacks on a schedule. If the FSM's API was momentarily down, the retry will succeed without you doing anything.

Configuring writeback

Per integration, writeback is on/off - toggled by Writeback enabled in the Post-Connection Setup modal (after first connecting) and in the Integration Settings modal at any time afterward.

Under the hood this flips the integration's sync_direction between import (one-way, no writeback) and both (writeback enabled).

There is no per-field configuration - what gets sent in the note is fixed by the integration. If you don't want session details pushed to the FSM, the option today is to disable writeback entirely.

Privacy considerations

  • The session link in the note opens the session in your TrainAR dashboard, so only people with a login to your account can view it. File links used as a fallback are signed and long-lived.
  • The "Notes" line surfaces session completion notes the engineer or AI provided - keep that in mind when training your team.
  • Customer-facing FSMs may show job notes to customers (depends on the FSM). Sample the writeback format in a test job in your FSM before going live to see how it renders for your team.

Failures

If a writeback fails (auth expired, FSM rejected the payload, network error), it's logged on the integration and the retry job picks it up. If retries continue to fail, the integration card in Dashboard → Integrations shows an error badge with the last error. The usual fix is re-authenticating (Reconnect button) - OAuth tokens have a finite lifetime.

Where to next