Got it. We’ll add your +1 for jobmaterial, companycontact, asset, and joballocation object webhooks, plus the request that creation-time field values don’t also trigger change-style webhook handling, to the SDK/API wishlist.
On the reliability side, the current webhook docs say 4xx/5xx delivery errors are retried for up to 72 hours before the webhook is automatically cancelled, and the API reference notes that repeated failed deliveries, including timeouts, can make a subscription inactive automatically.
For debugging this today, GET /webhook_subscriptions supports status=inactive or status=all, and inactive subscriptions can include last_failure_reason and last_failure_at to help identify the last recorded failure.
We’ll also capture the broader reliability-layer feedback, including clearer visibility when a subscription is deactivated and better handling around duplicate deliveries or re-deliveries.
What: Forms and Templates - it would be good if we could properly push both forms and document templates programatically via the API
Why: while there is some support for both forms and templates, the current API does not allow us to properly push/update and link forms with their corresponding docx templates. This means there is a final step required to do it via the ServiceM8 UI.
How: this will help to install and maintain custom forms and templates (inc quotes and invoices) for clients where we have them directly into their ServiceM8 systems via API key or OAuth.
Supporting the x-impersonate-uuid header when using an API key would be very helpful for synchronising messages and notes between systems using a private integration. Without this, any messages coming from the external application will appear as if they’re from the API key user.
What - Notification access for us to display.
Why / How - We run two way direct sms for booking with our ai agent and it would be handy for it to show up in notifications like 2 way sm8 sms works.
We’re using the ServiceM8 MCP connector with Claude to create jobs automatically from our recurring client schedule as service m8 recurring feature is to limited It’s working well, but there’s one real gap - create_job only takes company name, address, description, and template, so there’s no way to add materials or pricing to a job through it.
What’s interesting is this isn’t actually a limitation of the API itself - we can already read full job material data via jobmaterial.json, we use it for cost reporting today. The connector just doesn’t expose a way to write to that same endpoint.
In practice this means we can copy a job’s description automatically when creating a new one, but then have to manually re-enter every line item and price afterward - which cancels out most of the time we’re trying to save.
Would love to see something like add_job_material added so we can copy a previous job’s full details, including pricing, in one step rather than a separate manual billing pass every time. Guessing this would help anyone else building on the connector who needs to create genuinely complete jobs, not just bare-bones ones.