Commusoft integration

Commusoft is field-service software for UK plumbing, heating, and gas businesses. Connect it to TrainAR to import jobs and post training completion notes back to the job's communication timeline.

What syncs

Into TrainAR (15-minute polling + on-demand):

• Commusoft jobs become tasks in TrainAR.
• Status mapping: completed, done, finished, closed, invoiced → completed; cancelled, archived, deleted → cancelled; everything else → open.
• Commusoft customer ID, job ID, and job UUID are stored on the task so writeback routes to the correct job.
• Commusoft users are mapped to TrainAR users for assignment.

Back to Commusoft (when Sync direction = Import + Writeback):

When a training session is completed against a Commusoft-sourced task, TrainAR posts a communication note onto the job with task title, completed-by name/email, score, duration, session link, and video URL.

What you'll need

• Admin access to Commusoft.
• Your Commusoft client ID (the subdomain of your Commusoft URL).
• A Commusoft username and password with permission to create job notes.
• Admin access to TrainAR.

Setup

Commusoft uses an API-key auth flow rather than OAuth. TrainAR's connect screen collects your credentials, calls Commusoft's auth endpoint to obtain an API token, and stores that token. Your password is not retained.

1. Dashboard → Integrations → Commusoft card → Connect.
2. In the connect modal, enter:
   • Client ID — the subdomain of your Commusoft URL (for example acme if your Commusoft URL is acme.commusoft.co.uk).
   • Username — your Commusoft sign-in email.
   • Password — your Commusoft sign-in password.
3. Click Connect. TrainAR validates the credentials with Commusoft in real time.
4. Once validated, the card shows Connected and an initial job sync runs.
5. (Optional) Open settings to enable Import + Writeback.

Sync model

Commusoft does not send webhooks to TrainAR. Instead, TrainAR polls Commusoft every 15 minutes for new and changed jobs. This means there's up to a 15-minute delay between a change in Commusoft and the corresponding update in TrainAR.

If you need an immediate sync (e.g. after dispatching a new urgent job), click Re-sync on the card — that runs an immediate pull.

Troubleshooting

Connection shows "Pending" or "Validation failed" after saving credentials. Commusoft rejected the credentials at validation time. Double-check:

• Client ID is the subdomain only — not the full URL.
• Username is the email you use to sign in, not a display name.
• Password is current (Commusoft sometimes expires passwords).

Jobs aren't syncing in. Open the card's sync history. If polling has been failing for a while, the most common cause is that the stored API token has expired — disconnect and reconnect with current credentials.

Writeback note is missing on a Commusoft job. Confirm Sync direction = Import + Writeback. The note can only post if TrainAR knows the Commusoft customer ID and job ID for that task — these are populated during sync. If you created the task in TrainAR before syncing started, writeback may fail; run a Re-sync to refresh the metadata.

Authentication "No Token found in Request" message. This is a known Commusoft quirk where their API sometimes rejects header-based auth and only accepts the token as a query parameter. TrainAR handles this automatically — you shouldn't see this error unless the token itself has expired.

Privacy

TrainAR receives the job-related fields needed for syncing (title, description, status, customer, dates) and the user list. Commusoft customer payment data and unrelated records are not pulled. Commusoft receives only the communication notes that writeback produces.

You can disconnect at any time. Existing tasks remain in TrainAR; polling and writeback stop immediately.