// SERVICEM8 + AUTOMATIONS
A ServiceM8 webhook not firing usually means one of three things: the subscription was cancelled, the job was created a way your trigger does not catch, or the login behind the connection changed. Nothing errors, so nobody notices. We build every ServiceM8 automation with three guards: a dedicated Web Blend user for the connection, an alert when a flow goes quiet, and a register that replays what was missed.
Updated October 2026 · ServiceM8 Bronze Partner
// CHECKS TO RUN FIRST
You are not the only one. The ServiceM8 community has threads from owners whose webhook subscriptions disappeared with no logs, no errors and no notice. Run these before you pay anyone, us included.
List your webhook subscriptions through the ServiceM8 API with status=all, which returns inactive ones as well. ServiceM8 retries a failing webhook for up to 72 hours, then cancels it. If your receiving end was down or erroring for longer than that, the subscription is gone and has to be set up again.
Make and Zapier users have reported their trigger catching most jobs but missing some: jobs that started as a phone call, or jobs created automatically after an online purchase. If only some jobs fail, compare how those jobs were made before you rebuild anything.
A version change can move how jobs are created. One owner on the ServiceM8 community reported API-created jobs no longer triggering their job-created webhook after moving to ServiceM8 15. Note the date your flow went quiet and check what changed around it.
If the connection was made with a staff member’s login, a password change or a removed user can end it. So can a deleted API key. Nothing in ServiceM8 warns you when that happens.
Most ServiceM8 jobs start life as a Quote. If your flow should run when a job becomes a Work Order, a “new job” trigger fires at the wrong time. It needs to watch for the status change instead.
If those all check out, email ServiceM8 support with the callback URL, the job numbers and the times, so they can trace it on their side.
// HOW WE STOP IT
We create a dedicated user in every client’s ServiceM8, with the Web Blend business name, a webblend.au email and only the rights it needs. Every connection runs through it. A staff password change or a deleted user cannot break it. You know it is there, and you leave it alone.
Error alerts only fire when something runs and fails. A webhook that stops produces nothing to fail. So we watch for silence: if a flow goes quiet for longer than it normally does, we are alerted, and we set that window from your normal volume.
Every action is logged in a Google Sheet, for example who has been asked for a review. Failures are listed, and a catch-up automation replays each one once.
// NOT ONLY SERVICEM8
Same fix: an alert when it goes quiet, then we upload the missing data so the account catches up. If your automations go well beyond ServiceM8, see automation monitoring for small business.
// WHAT YOU GET
Automation Rescue + Watch: $490 + GST to fix what is broken and set up monitoring, then $49/month + GST. Watch covers Make and n8n, including self-hosted n8n and automations we did not build. Zapier is covered with a Zapier add-on, $29/month + GST, or we move your Zaps to Make or n8n instead.
Not sure what is connected at all? The ServiceM8 health check ($350 + GST) lists every integration and where it drops data. Building a new connection rather than fixing one? See ServiceM8 integrations and the ServiceM8 GoHighLevel integration. For the do-it-yourself version, our guide on how to connect ServiceM8 to GoHighLevel covers the setup.
Get my automation fixed// PRIMARY SOURCES
// QUESTIONS
Tell us which automation went quiet and roughly when. We will tell you what probably broke before you spend anything.
Get my automation fixedBecause nothing ran. An error alert needs a run that fails. A subscription that went inactive, a trigger that skips some kinds of job, or a connection whose login changed produces no run at all, so there is nothing to fail and nothing to alert on.
Users in the Make and Zapier communities have reported triggers missing jobs created outside the usual path, such as phone calls turned into jobs or jobs created after an online purchase. Check which jobs fail and how they were created before rebuilding.
ServiceM8’s developer documentation says a webhook that gets an error response is retried for up to 72 hours, then cancelled. After that the subscription has to be created again.
No. We set up our own user in your account, with only the rights the automation needs. It sits in your staff list where you can see it. Leave it in place: removing it stops the automations that run through it.
ServiceM8’s paid plans are priced by plan, not per user, so adding our user does not change what your plan costs.
We fix it in place, on our own connection, and add the Zapier add-on so it is watched ($29/month + GST on top of the monthly watch). If you would rather have everything in one place, we can move your Zaps to Make or n8n instead, quoted before we start.
Automation Rescue + Watch is $490 + GST to find what broke, fix it and set up monitoring, then $49/month + GST for the silence alerts, the register and catch-up replays. It covers Make and n8n, including self-hosted n8n and automations we did not build. Watching Zapier is $29/month + GST extra.
// READY WHEN YOU ARE
Tell us which automation went quiet and roughly when. We will come back with what probably broke. Fixing it and watching it is $490 + GST, then $49/month + GST.
Get my automation fixed