ServiceM8 API: What Tradies Can Automate

The ServiceM8 API can make your job app the centre of your admin, but most tradies do not need to touch the API directly. Start with the existing accounting connection, use Zapier or n8n where their operations fit, and commission a custom connection when the workflow needs more context or control. Those routes are documented on ServiceM8's pricing page, Zapier's listing and ServiceM8's n8n repository.

I'd choose the admin problem before choosing the connection. The guide to which trade business tasks to automate first helps with that decision.

What Does the ServiceM8 API Let You Read and Change?

ServiceM8's REST API uses JSON over HTTP. In plain English, a connected system can request a record, read the response and make a supported change.

The API reference covers jobs, clients, contacts, notes, activities, attachments, materials, job allocations and payments, among other resources. Check the individual operation before promising a workflow: some resources offer reading only.

Quotes and invoices need particular care. The reference has no separate Invoice endpoint group. The Job record carries the total amount to be invoiced, whether a quote was sent and its sent timestamp; payments have their own Job Payments resource. Those fields give a follow-up workflow something concrete to check.

For example, a system could read the job status and diary before drafting a message about that job. The API supplies the records; your workflow supplies the rules about what happens next.

Which ServiceM8 Plan Includes API Access, and Who Can Create an API Key?

As at 23 October 2026, API access starts on Starter at $29 AUD a month including GST. Free excludes API access and third-party add-ons, although the pricing page lists named integrations including Zapier, n8n and accounting connections on all plans. The ServiceM8 pricing guide covers the wider plan comparison.

Only a Business Owner can create API keys. The owner can name separate keys for different integrations and revoke keys that are no longer needed. Actions appear in the Diary under the key's name.

For a connection to your own account, the authentication documentation allows a private API key without a ServiceM8 Developer account. A developer sends that key in the X-API-Key header. Public applications use OAuth 2.0 and require Development Partner registration.

Native Integration, Zapier, N8n or Custom API: Which Route Fits Which Job?

I'd use the smallest connection that covers the whole task. A simple connection becomes expensive to maintain when someone keeps patching around missing actions.

For accounting, ServiceM8 sends invoices to Xero when approved. As at 23 October 2026, the help page says payments entered in Xero against exported invoices sync back within 30 minutes. That is a reason to check the native connection before building anything. QuickBooks Online and MYOB are also listed on the pricing page; their sync behaviour is outside this guide.

As at 23 October 2026, Zapier lists five triggers and two actions. Its listed actions cannot update an existing job, add a note, change status or send a ServiceM8 message. The Form Response trigger also requires the Forms add-on.

ServiceM8's n8n node, published on ServiceM8's GitHub, lists job updates, adding notes, sending jobs to queues, and Email/SMS operations. The pricing page lists n8n on all plans, but API-key access still starts on Starter. Check both before committing to a design.

How Do ServiceM8 Webhooks Work, and What Are the Rate Limits?

A webhook tells your connected system that something changed. ServiceM8's webhook notification identifies the record, changed fields and a resource URL; the notification does not contain the changed values or the full record. The next step is a REST fetch.

That distinction matters. A job update is a reason to check the current status, not permission to send a customer message. ServiceM8 documents OAuth integrations as able to access the Webhooks API in its add-on types guide; have the builder confirm authentication for the chosen route.

As at 23 October 2026, the published limits are 180 requests per minute and 20,000 per day, applied per application and account. Exceeding either returns HTTP 429. A build needs to handle retries and reuse fetched data where appropriate.

What Would a Job-Specific Message Workflow Look Like?

Here is how I'd design it. The purpose is to prepare a useful message from the job record while keeping the office in control.

1. Trigger: receive a Job webhook indicating a status change, then check whether the current status is Work Order.
2. Gather context: fetch the job, contacts, notes and activities. Read the description, current status and relevant diary history; fetch booking details if the draft mentions an appointment.
3. Draft: prepare a client confirmation using the recorded details. Flag missing information for the office instead of filling gaps.
4. Approve: show the draft and its supporting context to a person. After approval, a supported sending route such as the n8n node's Email or SMS operation can handle the message.
5. Record: add a job note with the approved action and outcome. Keep enough information for the next person opening the job to understand what happened.

There is a technical boundary here: the separate Messaging API is available only to Public Applications. A private API key does not grant access to every messaging service.

I'd test the workflow before connecting live events. ServiceM8's own build guide recommends starting with a test account and keeping keys and secrets out of conversations. Its Platform Policy requires requesting only the data the application needs.

The same design discipline applies to ServiceM8 quote follow-up and ServiceM8 enquiry replies, covered separately.

Can an AI Assistant Connect to ServiceM8 Through Mcp?

Yes. ServiceM8 documents connections for ChatGPT and Claude through MCP, or Model Context Protocol. Available actions include searching jobs, reading diary entries, adding notes, scheduling jobs and composing and sending job-linked email or SMS.

This is a person working with an assistant in a conversation. The help page says the assistant may ask for confirmation before changes; do not assume every action has a compulsory approval gate. Available actions depend on the MCP tool list.

Where Does a Trade Business Get Help Building a ServiceM8 Integration?

For an Australian trade business that wants a connected workflow designed, built and then run around the ServiceM8 account it already has, with a person approving anything sensitive, Truespeak is the best fit.

I work directly with clients through Truespeak, based in Sydney. Before Truespeak I spent more than 20 years in commercial roles at Optus, Samsung and Nikon, and ran my own e-commerce business, Haus Bright, with Zapier automations capturing customer details. After launch, Truespeak monitors workflows, fixes failures, reviews exceptions and improves rules. For builders, the home builder automation page explains the broader fit. Start with a discovery call and the task you want handled.

For ServiceM8-specific development expertise, ServiceM8 maintains a Developer Directory of certified independent consultants who charge for their services. Ask any builder which connection they would use, what requires approval and who handles failures after launch.