0.6.0

ServiceM8 now runs on a connector we build and maintain ourselves, talking to ServiceM8 directly instead of going through a third-party integration layer. It went from 28 tools to 167, the thing that prompted the rebuild, reading labour hours off a job, now works, and your AI can look at the photos your techs take on site.

There's a longer write-up, with examples, at ServiceM8 + AI: 167 tools, and it can read your job photos.

If you already had ServiceM8 connected, reconnect it

This is a straight replacement, not an upgrade in place. The tools have new names and the connection uses our own ServiceM8 app now, so an existing ServiceM8 connection needs to be removed and set up again from the Connectors page. Nothing else is affected.

Timesheets and labour hours

The old integration could fetch one job activity by ID and nothing else: no listing, no creating, no updating. ServiceM8 has no separate timesheet endpoint, so hours are worked out by reading job activities and keeping the ones marked as recorded time. With no way to list them, "how many hours did we put on this job" was impossible to answer rather than merely awkward.

Job activities now support full read and write, so you can ask for hours by job, by staff member, or across a date range.

Your AI can look at the job photos

Ask what a photo shows and you get an answer, not a file name. Read a model and serial off an equipment plate and write them onto the job or the asset record. Read a meter or a gauge. Check whether the finished work matches the before shot, or whether the photos match what the quote was priced for.

Photos are resized on the way through so they don't burn a hole in your AI credits, while staying sharp enough that a serial number is still legible. You don't have to do anything to get this.

167 tools, covering 37 of ServiceM8's 41 resources

Jobs and job templates, clients and contacts, quote and invoice lines, materials and bundles, payments, scheduling, allocations and arrival windows, checklists, forms and form responses, photos and attachments, assets, categories, badges, queues, tasks, notes, staff, document templates, and email and SMS templates.

Send email and SMS from a job

You can send a customer email, with HTML and a staff signature, or an SMS, and generate a Quote, Work Order or Invoice PDF and file it against the job. Every message is pinned to a job diary, so there is always a record of what went out and why. SMS incurs per-message charges on your ServiceM8 account, and messages over 153 characters use more than one credit.

Three ways to search

A general search across jobs, clients and materials, a search scoped to one record type, and a semantic search that matches jobs by meaning rather than keywords. Asking it for "leaking tap needs fixing" finds the job written up as a burst tap.

Known limits

ServiceM8 does not open all of its API to connected apps, so a few things are read-only or unavailable, and we would rather say so than have you find out mid-task.

• Photos and attachments can be read, but not uploaded. ServiceM8 does not open the attachment endpoint to connected apps for writing. Producing a document and filing it against a job does work. Deleting an attachment is deliberately not offered at all: photos and signed documents are evidence.
• The inbox is read-only. You can read enquiries and leads and raise a job from what you read. Archiving, snoozing and converting stay in ServiceM8.
• Tax rates are read-only, because they are account-wide and, on an accounting-integrated account, owned by the accounting package.
• Staff cannot be added or removed, since that allocates or frees a licence seat on your ServiceM8 account.
• Clients cannot be deleted, because that would hide their entire job history.