Integration
ServiceM8 with Zapier and Make: what each can do, and where they run out
Zapier's ServiceM8 app has five triggers (New Job, Job Completed, Job Queued, New Client, New Form Response), all marked instant, and two actions: Create Job and Create Client. Make's ServiceM8 app adds updates, lookups, deletes and a Make an API Call module, but its three Watch triggers run on your scenario schedule, every 15 minutes on the free plan.
Last checked 25 Sep 2026 against the sources listed at the end of this page.
What syncs, and when
| What | Direction | When | Notes |
|---|---|---|---|
| New Job | ServiceM8 to Zapier | Instant, per Zapier's app page | Optional filter by job category. Make's equivalent is Watch Jobs, which also fires on status changes. |
| Job Completed | ServiceM8 to Zapier | Instant, per Zapier's app page | Fires when a job's status changes to Completed. Optional job category filter. |
| Job Queued | ServiceM8 to Zapier | Instant, per Zapier's app page | Fires when a job is put in a chosen queue. Zapier only; Make has no queue trigger. |
| New Client | ServiceM8 to Zapier or Make | Zapier instant; Make on schedule (Watch New Client) | Fires on client creation only, not edits. |
| New Form Response | ServiceM8 to Zapier or Make | Zapier instant; Make on schedule (Watch Form Response) | Needs the Forms add-on. Zapier lets you choose the form and optionally the staff member. |
| Create Job | Zapier or Make to ServiceM8 | When your Zap or scenario runs | Zapier requires a status and accepts client, job and billing address, description, PO number, work completed and contacts. No category, badge or source field. |
| Create Client | Zapier or Make to ServiceM8 | When your Zap or scenario runs | Zapier requires a name; address, billing address and primary contact details are optional. |
| Update, get, list, delete (jobs, clients, job contacts) | Make to ServiceM8 | When your scenario runs | Make only. Zapier's ServiceM8 app lists no update or search actions. |
| Make an API Call | Make to ServiceM8 | When your scenario runs | Reaches any ServiceM8 REST endpoint with your connection, such as notes, badges or job materials. Needs you to read the API reference. |
What does not sync
- Invoice, quote and payment events. Neither app offers a trigger for invoice paid, quote accepted or quote sent; ServiceM8's own webhooks cover these but need a developer application.
- Updates to existing jobs from Zapier. Its ServiceM8 app can only create jobs and clients.
- Searches in Zapier, so a Zap cannot check whether a client already exists before creating one.
- Job categories, badges and custom fields on Zapier's Create Job.
- Two way sync. Every Zap or scenario is a one way recipe you build and maintain.
Set it up
- Write down the one event and the one result you want, for example 'job completed, add a row to the warranty sheet'. Pick Zapier if a listed trigger and Create Job or Create Client covers it; pick Make if you need to update or look up records.
- Connect ServiceM8 inside Zapier or Make using a ServiceM8 login with the permissions the automation needs.
- Build with a test job in ServiceM8, not a live customer's job.
- On Make, set the scenario schedule. On the free plan the shortest interval is 15 minutes; paid plans go down to 1 minute.
- Turn on error notifications, and put one person in charge of checking the task or credit history each month.
- Note in ServiceM8 (a job template or the office manual) which automations exist, so nobody duplicates them by hand.
Zapier: instant, but narrow
Zapier's ServiceM8 app is small. Five triggers, two actions, no searches, and it is not a premium app, so it works on Zapier's free plan. Zapier marks all five triggers as instant, which means a Zap runs moments after the job is created or completed rather than waiting for Zapier's polling cycle. That makes it good at one direction of work: something happens in ServiceM8, tell another system. Add completed jobs to a spreadsheet, email the office manager when an incident report form is submitted, push new clients into a mailing list.
It is weaker the other way. Create Job can make a job from a web form or a CRM deal, but it cannot set a job category or badge, cannot update a job later, and cannot first check whether the customer already exists, so repeat customers become duplicate clients unless you clean up by hand.
Make: more reach, on a timer
Make's ServiceM8 app has sixteen modules: three Watch triggers, create, get, list, update and delete for jobs and clients, job contact modules and Make an API Call. With updates and lookups you can build what Zapier cannot, such as finding a client by email before creating a job, or changing a job's status when something happens elsewhere. Make an API Call reaches the rest of the ServiceM8 API.
Make's documentation does not mark its ServiceM8 triggers as instant, and Make runs non instant triggers on the scenario's schedule. The free plan's shortest interval is 15 minutes; paid plans allow 1 minute. Make's own page for the ServiceM8 app also notes that its documentation is limited, so expect to test each module yourself.
What they cost, and when custom is cheaper
Zapier counts one task for every successful action step; triggers are free. The free plan covers 100 tasks a month and two step Zaps. Professional starts at US$19.99 a month billed yearly (US$29.99 monthly) for 750 tasks. Make's free plan gives 1,000 credits and two active scenarios; its paid Make plan is listed from US$9 a month for 5,000 credits. Prices are from each vendor's pricing page on 25 September 2026.
A private ServiceM8 add on is a one off build rather than a monthly fee. ServiceM8 can host simple function add ons itself, and public developer applications get ServiceM8's webhook events, including job completed, invoice paid and quote accepted, which neither connector exposes. Our own rule of thumb, not a vendor figure: once you are paying for a Zapier or Make plan every month for automations that also need lookups, updates or invoice events, a small private add on usually costs less over two years and breaks less often.
Sources
- Zapier's ServiceM8 integration has triggers Job Completed, Job Queued, New Client, New Form Response and New Job, and actions Create Client and Create Job; each trigger is labelled Instant and the app is not premium. Zapier, checked 25 Sep 2026.
- Zapier's Create Job requires status; Create Client requires name. Zapier, checked 25 Sep 2026.
- Make's ServiceM8 app includes Watch Form Response, Watch Jobs and Watch New Client triggers, create, get, list, update and delete modules for clients and jobs, job contact modules and Make an API Call; Make notes its documentation for the app is limited. Make, checked 25 Sep 2026.
- In Make, a polling trigger checks for new data based on the scenario's schedule; instant triggers are marked with a lightning icon and an instant tag. Make Help Center, checked 25 Sep 2026.
- Make's Free plan has 1,000 credits a month, 2 active scenarios and a 15 minute minimum interval; the Make plan is listed at $9 a month for 5,000 credits with a 1 minute minimum interval. Make, checked 25 Sep 2026.
- Zapier's Free plan includes 100 tasks a month and two step Zaps with a 15 minute update time; Professional 750 tasks is $29.99 a month billed monthly or $19.99 a month billed annually, with multi step Zaps and premium apps. Zapier, checked 25 Sep 2026.
- In Zapier, triggers never use tasks; each successful action step uses a task. Zapier Help Center, checked 25 Sep 2026.
- ServiceM8 event webhooks include job.completed, job.invoice_paid, job.quote_accepted, job.quote_sent and inbox.message_received; callbacks must respond within 10 seconds. ServiceM8 Developer, checked 25 Sep 2026.
- Private integrations use an API key; public OAuth applications add webhooks and deeper platform features. Simple Function add-ons are hosted by ServiceM8. ServiceM8 Developer, checked 25 Sep 2026.