Getting started with QuoteCloud

Connect ServiceM8 to QuoteCloud, step by step

ServiceM8 connects to QuoteCloud through Zapier, one Zap per job. Here's the Work Order Zap from start to finish, the snags trades hit when testing, and where Make fits.

ServiceM8 connects to QuoteCloud through QuoteCloud's Zapier app, on Essentials and up. In Zapier, create a Zap, pick a trigger such as QuoteCloud's Document Signing Complete or ServiceM8's Job Queued, sign in to both apps, add the steps and map the fields. Test with a sample quote or job, check the result in the other app, then turn it on.

Last reviewed by the QuoteCloud team

Three illustrative Zap editor panels with sample data, taking turns at the front. Step 1: QuoteCloud's Document Signing Complete trigger; the test found WP-2214, signed by Leah and Marcus Odell. Step 2: ServiceM8's Create Job with Customer Name from Prepared for, Job Status Work Order, Job Address from the Job address data item and Job Description from the document title and reference; job 5184 created. The rest of Create Job: Purchase Order Number from the reference and the job contact's first name, email and mobile.

How do I connect ServiceM8 to QuoteCloud?

Through Zapier, one Zap per job. Here's the Work Order Zap; every recipe on this site is built the same way.

  1. Check your plans

    QuoteCloud's Zapier app is on Essentials and up. You also need a ServiceM8 account and a Zapier plan that covers the tasks your Zaps will run.

  2. Get the template ready

    Add the data items your Zaps will read or fill, such as Job address and ServiceM8 job number, to your job quote templates.

  3. Create a Zap, pick the trigger

    Choose the app the event happens in: QuoteCloud's Document Signing Complete, or ServiceM8's Job Queued or New Client.

  4. Sign in to both apps

    Zapier asks you to connect QuoteCloud and ServiceM8 the first time you use each. Use accounts that can see the documents and create jobs.

  5. Add steps, map fields

    Add ServiceM8's Create Job or QuoteCloud's Create Document, then map each field from the trigger's test data.

  6. Test, then turn it on

    Run the test, check the job or document in the other app, then switch the Zap on.

Step 1: the trigger, and its test data

Choose QuoteCloud, then Document Signing Complete. Zapier fetches a recently signed document as test data.

Check it has what you plan to map: the title, the reference, the recipient's name and email, and your Job address data item. If something's missing, sign a complete test quote that uses the template and load fresh data.

The full recipe: signed to Work Order
Zap editorWeirbrook Plumbing & Gas Illustration · sample data

1QuoteCloudTrigger

Document Signing Complete

Account
Weirbrook Plumbing & Gas (QuoteCloud)
Trigger event
Document Signing Complete

Test: Found a document: WP-2214, signed by Leah and Marcus Odell

Illustration with sample data, not Zapier’s screen.

Step 2: Create Job, mapped

Choose ServiceM8 and Create Job. Job Status is the one required field: set it to Work Order. Map the customer, job address, a description with the quote's reference, the purchase order number and the job contact. The numbers show which step each value comes from.

  • Leave Customer Name blank and ServiceM8 creates a new customer from the job contact details.
  • Create Job makes a new job every time: there's no update or search step in ServiceM8's Zapier app.
  • A Zap never ticks options or chooses content blocks in QuoteCloud documents.
Every field, mapped
Zap editorWeirbrook Plumbing & Gas Illustration · sample data

2ServiceM8Action

Create Job

Customer Name
1. Prepared for
Job Status
Work Order
Job Address
1. Job address (the data item)
Job Description
1. Document title · 1. Reference signed

Test: Job 5184 created at Work Order

Illustration with sample data, not Zapier’s screen.

Ready to build your first Zap?

QuoteCloud's Zapier app is on the Essentials plan and up. Start a free 14-day trial and build the Work Order Zap with a test quote.

What usually goes wrong, and the fix

The snags ServiceM8 teams hit while testing.

  • Blank job address

    The trigger's test data has no Job address. Sign a fresh test quote made from a template that has the data item, and load new test data.

  • Two jobs for one quote

    Two Zaps create jobs from the same quote, such as signing and deposit. Keep one trigger per kind of quote, or filter each Zap.

  • Duplicate clients

    Both client Zaps are on, or Customer Name differs from the existing client. Run one client direction; check how Customer Name matches in a test.

  • The original job didn't move

    Expected: ServiceM8's Zapier app can't update a job. How teams handle it.

  • Job Queued never fires

    The job went to a different queue, or a job category filter on the trigger doesn't match. Check the queue name in the trigger.

  • No email to send to

    ServiceM8's job trigger didn't carry the client's email. Leave the draft for the tech to address, or add the client with a client Zap first.

Can I connect ServiceM8 through Make instead?

Yes, if your team builds its own. Make is a bring-your-own route: you add a connection to QuoteCloud with Make's built-in OAuth, then call QuoteCloud's API or Zapier endpoints from a scenario, beside Make's ServiceM8 modules.

There's no ready-made QuoteCloud app or list of modules on Make, so you design each step yourself. Teams usually choose Make for what Zapier's ServiceM8 app can't do, such as updating the original job through ServiceM8's own API.

Before you start

  • Essentials for Zapier

    QuoteCloud's Zapier app and API, custom data items and payments are on Essentials and up.

  • A Zapier plan

    Zapier bills separately: choose a plan that covers the tasks your Zaps will run each month.

  • Test records only

    A test job, a test template and @example.com contacts, so nothing reaches a real client.

  • A queue or category

    Set up the ServiceM8 queue or job category that will start your proposals.

Set-up questions

Is there a ready-made QuoteCloud and ServiceM8 template on Zapier?

No. Both apps are on Zapier, so you build the Zap yourself from QuoteCloud's and ServiceM8's own triggers and actions. Each one is a trigger, one or two steps and the field mapping, which this site lists for each recipe.

Which ServiceM8 triggers and actions are on Zapier?

Triggers: New Job, Job Queued, Job Completed, New Client and New Form Response, which needs ServiceM8's Forms add-on. Actions: Create Job and Create Client. There are no ServiceM8 searches, so a Zap can't look up an existing job or client.

Do I need a developer to connect ServiceM8?

Not for Zapier: the recipes on this site need no code. You need someone who can map fields and test with sample jobs. A developer helps only if you build in Make or call ServiceM8's API, for example to update existing jobs.

How do I test without bothering real clients?

Use a test template, a test job and contacts at @example.com addresses, sign the test quote yourself, and check the job in ServiceM8 before you turn the Zap on. Delete or archive the test job afterwards.

More ServiceM8 questions

More on QuoteCloud and ServiceM8

Six use cases with the exact Zapier steps, when to quote where, the limits and the cost.

Your first Zap, this afternoon.

Start a free 14-day trial of QuoteCloud, connect ServiceM8 in Zapier and build the Work Order Zap with a test quote.