Resources · Make integration

ServiceWorks Make integrationAutomate ServiceWorks with Make.

Your customer list in ServiceWorks can feed your other tools on its own. The ServiceWorks Make integration gives you 4 modules: one trigger and three actions, all about customers. This page shows you how to link your account, build a first scenario and pick the right module.

Try the ServiceWorks integration on MakeSee the 4 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the ServiceWorks Make integration do?

The ServiceWorks Make integration links your ServiceWorks account to Make so customer records can move between ServiceWorks and your other apps without copy and paste. You build a scenario, which is the automation itself: a chain of modules, each module being one step such as a trigger or an action.

Keep a second tool in sync. Put Watch Customers at the start of a scenario and let Make pick up customer records from ServiceWorks on the scenario's schedule, then pass each one to the next module, for example a spreadsheet or a mailing list app.

Stop typing new customers twice. When a contact form, a booking tool or a sales app already holds the details, Create a Customer writes them into ServiceWorks for you.

Fix records from the outside. Update a Customer changes an existing customer when the source of truth lives elsewhere, and Make an API Call reaches the parts of the ServiceWorks API that the three named modules leave aside, with the same connection.

Be aware of one gap: Make says it cannot offer complete documentation for ServiceWorks because too little public information exists about the app. Expect to discover field names inside the editor rather than in a guide. The Make troubleshooting page helps when a run fails, and Make training covers the editor from scratch. ServiceWorks may also have an n8n node; the n8n vs Make comparison lays out how the two tools differ.

Connect

How do you connect ServiceWorks to Make?

  1. 01

    Add a ServiceWorks module

    In a scenario, search for ServiceWorks, choose any of its modules, then click Create a connection. A connection is your ServiceWorks account linked to Make once and reused by every ServiceWorks module afterwards.

  2. 02

    Name the connection

    Giving it a name is optional, but a clear label such as the account owner or the company helps later if you link more than one ServiceWorks account to the same Make workspace.

  3. 03

    Authorize and save

    Either approve Make on the ServiceWorks page that opens, or paste the key ServiceWorks gives you, depending on what the window asks for. Then click Save and the module is ready to fill.

First scenario

Your first scenario with ServiceWorks

GoalWhen another app receives a new customer, Make creates that customer in ServiceWorks.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the big + to place the first module on the canvas.

  2. 02

    Start from your other app

    Pick the trigger of the app where new customers first appear, such as your web form or booking tool, and link that account. Its output is what ServiceWorks will receive.

  3. 03

    Add Create a Customer

    Click the + on the right of that trigger, search for ServiceWorks, choose Create a Customer and link your account with Create a connection. Map the name and contact data from the first module.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario a single time; open each module's bubble to read the bundles it got, then check the new customer in ServiceWorks.

  5. 05

    Schedule and switch on

    Set the schedule on the first module (every 15 minutes by default, the minimum on the Free plan) and switch the scenario on so it keeps running.

Triggers

Which trigger starts a ServiceWorks scenario?

1 module starts a scenario when something happens in ServiceWorks. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by ServiceWorks as soon as it happens.

ServiceWorks1Watch Customers

Watch Customers

triggerIn the docs only

Watch Customers gives your scenario a starting point inside ServiceWorks: each customer record it picks up becomes a bundle, one item that flows to the next module. Make lists it without an official description, so read the first bundles carefully to see exactly which customers it returns.

How it fires
scheduled. Make checks the app on the scenario's schedule, never the moment a customer changes.
When to use it
whenever another tool needs to learn about ServiceWorks customers without anyone exporting a file.
Watch out
on the Free plan the shortest gap between two checks is 15 minutes.
Modules

What can ServiceWorks modules do in Make?

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

ServiceWorks1

Create a Customer

ActionIn the docs only

Create a Customer adds a new customer to ServiceWorks from data another module already holds, so nobody retypes names and contact details by hand.

When to use it
a lead fills a web form or books through a scheduling app, and ServiceWorks should get the record straight away.
Watch out
the module creates a new record every time it runs, so feeding it the same person twice gives you two customers.
ServiceWorks2

Make an API Call

ActionIn the docs only

Make an API Call lets you call any endpoint of the ServiceWorks API from your scenario, reusing the connection you already set up, so you reach what the named modules do not cover.

When to use it
you need something beyond customers and know which endpoint does it.
Watch out
you write the request yourself, and Make's limited ServiceWorks documentation will not tell you the endpoints.
ServiceWorks3

Update a Customer

ActionIn the docs only

Update a Customer changes a customer that already exists in ServiceWorks, which keeps a single clean record instead of a pile of duplicates.

When to use it
a client changes details in your billing or sales tool and ServiceWorks must follow.
Watch out
pair it with Watch Customers only after checking that your updates will not be picked up again and restart the loop.
Need help

Need help automating ServiceWorks with Make?

A person reads every message.

FAQ

ServiceWorks and Make: common questions

01Is the ServiceWorks Make integration free?
Yes, ServiceWorks is a standard app in Make, so it works on the Free plan. That plan has limits: 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution at most per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute and remove the cap on active scenarios. Each module run on one bundle counts as one operation on your plan.
02What do you need to connect ServiceWorks to Make?
A ServiceWorks account and a Make account. Make's documentation for ServiceWorks lists no prerequisites and no specific steps, so you follow the generic path: add a ServiceWorks module, click Create a connection, optionally name it, authorize Make on the ServiceWorks page or paste the key the app gives you, then click Save. The same connection then serves every ServiceWorks module in your scenarios, including Make an API Call. Keep one connection per ServiceWorks account to stay organized.
03Does the ServiceWorks trigger in Make react in real time?
No. Watch Customers is a scheduled trigger, marked with a clock badge in the editor. Make checks ServiceWorks each time the scenario's schedule comes around rather than being called by the app. A new scenario runs every 15 minutes by default, which is also the shortest gap on the Free plan; paid plans go down to 1 minute. In practice, a customer added in ServiceWorks reaches your scenario at the next scheduled check, not the second it is saved.
04What if a ServiceWorks module you need is missing in Make?
Use Make an API Call. It sends a request to any endpoint of the ServiceWorks API with the connection you already have, so anything beyond the three customer modules stays reachable. The catch is that Make flags its ServiceWorks documentation as limited, because little public information exists on the app. You will need the ServiceWorks API reference, or someone on their side, to know which endpoint to call. Test each request with Run once before switching the scenario on.
05Should you use Make or n8n for ServiceWorks?
It depends on the tool your team already runs. On Make, ServiceWorks has 4 ready modules centered on customers, a visual editor and a Free plan to test with. The same app often has an n8n node too, so compare the modules each side offers for your use case before choosing. Whichever you pick, check first that the customer fields you rely on are exposed, since the Make documentation for this app is incomplete.
Same platform

Other docs you might need on this stack.

Browse all integrations