Resources · Make integration

ServiceM8 Make integrationAutomate ServiceM8 with Make.

Can a new ServiceM8 job or client start work in your other tools on its own? Yes: the ServiceM8 Make integration gives you 16 modules, 3 of them instant triggers. This guide is for field service teams new to Make, and it walks you from the connection to a first working scenario.

Try the ServiceM8 integration on Make See the 16 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the ServiceM8 Make integration let you automate?

The ServiceM8 Make integration links your ServiceM8 account to Make, a visual tool where you chain apps together without writing code. ServiceM8 tells Make the moment a job, a client or a form response appears, and Make can then create, read, update or delete clients and jobs for you.

Every new client gets a job straight away. Watch New Client fires when someone is added in ServiceM8, and Create a Job opens the first job for them, so nobody has to retype the details.

Status changes reach the rest of the team. Watch Jobs reacts when a job is created or its status changes. Add Get a Client to pull the customer record, then post the update in your chat tool or log it in a sheet.

Completed forms turn into follow-up. Watch Form Response fires when a form is filled in, provided the forms add-on is active in your ServiceM8 account. From there, Update a Job or Create a Job Contact keeps the file current.

One honest limit: Make's own documentation for ServiceM8 is marked as limited, because little public information exists about the app. Test each module with real data before you rely on it. If a module you need is missing, Make an API Call reaches the rest of the ServiceM8 API. Weighing the two tools? The n8n vs Make comparison lays out the criteria, and the Make pricing guide explains how operations are counted.

Connect

How do you connect ServiceM8 to Make?

01
Add a ServiceM8 module
In your scenario, add any ServiceM8 module and click Create a connection. A connection is your ServiceM8 account linked to Make once, then reused by every ServiceM8 module you add later.
02
Name it and authorize Make
Give the connection a name if you like, for example the company account it belongs to. Then authorize Make on the ServiceM8 page that opens, or paste the key ServiceM8 gives you if that is what the window asks for.
03
Save and check the lists
Click Save. Back in the module, Make can now read your ServiceM8 data, so the fields offer real values to pick from instead of empty boxes. That is the sign the link works.

First scenario

Build your first scenario: a job for every new client

GoalWhen a new client is created in ServiceM8, Make opens a job for that client.

01
Create the scenario
On the Scenarios page, create a new scenario and click the big +. A scenario is the automation you build: a chain of modules, each one a single brick of work.
02
Pick the trigger
Search for ServiceM8, choose Watch New Client and select your connection. It is an instant trigger: ServiceM8 calls Make through a webhook as soon as a client is added.
03
Add Create a Job
Click the + on the right of the trigger, pick Create a Job, and map the client data from the first module into the job fields Make shows you.
04
Test with Run once
Click Run once, add a test client in ServiceM8, then open each module to read the bundles it received. A bundle is one item passed along, here one client.
05
Switch it on
Once the job looks right in ServiceM8, turn the scenario on. From then on each new client produces a job, and every module run counts as one operation on your Make plan.

Triggers

Which ServiceM8 events can start a scenario?

3 modules start a scenario when something happens in ServiceM8. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by ServiceM8 as soon as it happens.

ServiceM81Watch Form Response

Watch Form Response

Instant trigger

In Make“Triggers when a form is completed. Requires the forms add-on to be enabled in your ServiceM8 account.”

You get every completed ServiceM8 form delivered into Make, so the answers a technician or customer entered can feed the next steps without anyone copying them over.

How it fires

instant, ServiceM8 calls Make through a webhook as soon as the form is completed.

When to use it

pick it when a filled-in form should update a job, alert a manager or land in a shared record.

Watch out

it only works when the forms add-on is enabled in your ServiceM8 account; without it, nothing reaches Make.

ServiceM82Watch Jobs

Watch Jobs

Instant trigger

In Make“Triggers when a new job is created or a job's status is updated.”

This trigger hands Make a job bundle whenever a job is created in ServiceM8 and again whenever its status changes, so one module covers both the start and the progress of your work.

How it fires

instant, ServiceM8 calls Make through a webhook as soon as it happens.

When to use it

choose it to warn the office when a job moves on, or to copy job progress into a reporting sheet.

Watch out

a single job can fire several times as its status moves, so add a filter if you only care about one status.

ServiceM83Watch New Client

Watch New Client

Instant trigger

In Make“Triggers when a new client is created.”

Each client you add in ServiceM8 starts your scenario with that client's record, ready to be copied into a CRM, a mailing list or a new job.

How it fires

instant, ServiceM8 calls Make through a webhook as soon as the client is created.

When to use it

it fits onboarding flows, where a fresh customer should get a welcome message or an opening job without delay.

Watch out

its official description only mentions new clients, so do not count on it to report changes made to an existing client.

Modules

What can Make do inside ServiceM8?

ServiceM8 gives you 13 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

ServiceM81

Create a Client

Action

In Make“Creates a new client.”

Adds a customer to ServiceM8 from data that arrives elsewhere, such as a website form or a booking tool, so the office stops keying in names by hand.

When to use it

when leads are captured outside ServiceM8 and must become clients before any job is planned.

Watch out

run List Clients first if duplicates worry you, since creating twice gives two records.

ServiceM82

Create a Job

Action

In Make“Creates a new job.”

Opens a new job in ServiceM8 for you, which is the core of most field service automations: a request comes in and the work exists straight away.

When to use it

after Watch New Client, or when a quote accepted in another tool should become scheduled work.

Watch out

map the client from an earlier module so the job is not left without a customer.

ServiceM83

Create a Job Contact

Action

In Make“Creates a new job contact.”

Attaches a contact person to a job, which helps when the one who lets the technician in is not the account holder, a tenant or a site manager for example.

When to use it

right after Create a Job, when the request carried an on-site contact name.

Watch out

the job must already exist, so place this module after the one that creates or finds it.

ServiceM84

Delete a Client

Action

In Make“Deletes a specific client by id.”

Removes a specific client from ServiceM8 by its ID, handy for cleaning up test records or entries a scenario created by mistake.

When to use it

when an upstream tool marks a contact as deleted and ServiceM8 should follow.

Watch out

treat the deletion as final: nothing in Make's documentation mentions a way back, so test on a dummy client and add a filter before this module.

ServiceM85

Delete a Job

Action

In Make“Removes the selected job from the list.”

Takes the selected job off your ServiceM8 list, useful when a booking is cancelled upstream and the job should not stay on anyone's schedule.

When to use it

for cancellations coming from a booking page or a form, matched to the right job first.

Watch out

treat it as final, since no restore step is documented: make sure the job reference is correct and run it on a test job before switching the scenario on.

ServiceM86

Get a Client

Action

In Make“Gets information about the selected customer.”

Fetches the full record of one customer, so later modules can use details that the trigger did not carry, like contact data for a message.

When to use it

after Watch Jobs, when the job alone does not tell you enough about who it is for.

Watch out

it needs the client's ID, mapped from an earlier module; it returns one client, not a list.

ServiceM87

Get a Job

Action

In Make“Gets information about a specific job.”

Reads everything ServiceM8 holds on one job, which lets a scenario act on the latest state rather than on whatever an older bundle said.

When to use it

before updating or reporting on a job, to work from fresh data.

Watch out

point it at one job ID; to go through many jobs, List Jobs is the better start.

ServiceM88

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Reaches any endpoint of the ServiceM8 API with the connection you already set up, covering what the 15 other modules leave out.

When to use it

when the operation you need has no dedicated module and the ServiceM8 API offers it.

Watch out

you write the request yourself, and since Make's documentation for ServiceM8 is limited, test every request with Run once before building on it.

ServiceM89

Update a Client

Action

In Make“Updates work data for a specific client by id.”

Changes the stored details of one client by ID, so a new phone number or address captured elsewhere lands in ServiceM8 without a manual edit.

When to use it

when your CRM or a customer portal is where people correct their own details.

Watch out

find the right client first with Get a Client or List Clients; the wrong ID overwrites someone else.

ServiceM810

Update a Job

Action

In Make“Updates information about a specific job.”

Edits an existing job, so information gathered after booking, from a form or a message, ends up on the job the technician opens.

When to use it

after Watch Form Response, to write the answers back onto the matching job.

Watch out

it acts on one specific job, so map the job reference from an earlier module rather than typing it.

ServiceM811

List Clients

In Make“Provides a list of all customers.”

Returns your whole ServiceM8 customer list, one bundle per client, which is the base for exports, checks for duplicates or bulk syncs.

When to use it

when a sheet or CRM should mirror every client, not just the new ones.

Watch out

each client becomes its own bundle, and every module placed after it runs once per client, which adds up in operations.

ServiceM812

List Jobs

In Make“Returns the entire list of jobs.”

Pulls the complete list of jobs out of ServiceM8, giving you raw material for a workload report or a backlog review.

When to use it

for a one-off export or a summary built with an aggregator, a Make tool that merges bundles into one.

Watch out

it can return zero, one or many jobs, and each job triggers the next modules separately.

ServiceM813

Search Job Contacts

In Make“Searches job contacts by given criteria.”

Looks up job contacts that match the criteria you set, so you can check whether a person is already attached before adding them again.

When to use it

just before Create a Job Contact, to avoid stacking the same contact on a job.

Watch out

a search may find nothing; add a filter so the scenario handles an empty result instead of failing later.

Need help

Need help automating ServiceM8 with Make?

A person reads every message.

FAQ

ServiceM8 and Make: common questions

01Is the ServiceM8 Make integration free?

Yes, ServiceM8 is a standard app in Make, available from the Free plan. That plan allows 2 active scenarios, runs of up to 5 minutes, files up to 5 MB and 512 MB of data transfer, with at least 15 minutes between two scheduled runs. Paid plans (Core, Pro, Teams, Enterprise) lift the active scenario cap and allow runs of up to 40 minutes. Usage is counted in operations, one per module run on one bundle. Your ServiceM8 subscription is a separate matter.

02What do you need to connect ServiceM8 to Make?

A ServiceM8 account and a Make account. Add any ServiceM8 module, click Create a connection, name it if you wish, authorize Make on the ServiceM8 page or paste the key it provides, then click Save. Make's documentation for ServiceM8 lists no specific prerequisites. One exception applies to forms: Watch Form Response needs the forms add-on enabled in your ServiceM8 account, otherwise no response ever reaches Make. Once saved, the same connection serves every ServiceM8 module in your scenarios.

03Do the ServiceM8 triggers in Make work in real time?

Yes. All 3 ServiceM8 triggers are instant: Watch Form Response, Watch Jobs and Watch New Client. ServiceM8 calls Make through a webhook as soon as the event happens, so the scenario does not wait for a polling interval like the default 15 minutes of scheduled triggers. You still need to switch the scenario on, and each run uses operations on your plan. Test with Run once first to see the bundle each trigger delivers.

04What if a ServiceM8 module is missing in Make?

Use Make an API Call. It calls any endpoint of the ServiceM8 API with the connection you already have, so you are not limited to the 10 actions and 3 searches listed. Keep in mind that Make's documentation for ServiceM8 is marked as limited, since little public information exists about the app, so test each request with Run once and read what comes back before activating. If the call fails, the error Make shows in the module usually points to the part of the request to fix.

05Should you use Make or n8n for ServiceM8?

It depends on the criteria that matter to your team, not on a winner. On the Make side the facts are clear: 16 ServiceM8 modules, 3 instant triggers, a visual editor and a Free plan to start. The same app may also have an n8n node, which is worth checking. Compare the modules each tool offers for the jobs and clients you handle, and how each counts usage, before you commit.

Add a ServiceM8 module

Name it and authorize Make

Save and check the lists

Create the scenario

Pick the trigger

Add Create a Job

Test with Run once

Switch it on

Need help automating ServiceM8 with Make?