Job.created webhook no longer firing

Developer General
1

i have had a workflow that was working to create jobs from an addon app that would then fire the job.created webhook to run a a script on my financing software. but since my recent switch to sm8 15 or servicem8 next it looks like the api job creation stopped firing the webhook job. created

2

My Zapier zaps are still firing on new job creation

3

Hi Hayden,
job.created is a documented event for a new job created in the system. We’d start by checking the subscription’s status and callback responses.

  1. Request GET https://api.servicem8.com/webhook_subscriptions?status=all and find your subscription with type: "event" and event: "job.created". Using status=all includes inactive subscriptions, which the default listing excludes.
  2. Check active, last_failure_reason and last_failure_at. These show whether the subscription is active and its most recent recorded delivery failure, if any. Save any failure details before reactivating, as successful reactivation clears the stored failure snapshot.
  3. Check your callback logs. Event webhook callbacks must return a successful 2xx response within 10 seconds. Repeated delivery failures, including timeouts, can automatically deactivate the subscription.
    Please email support@servicem8.com with an example job UUID, its creation timestamp, the subscription status and any relevant API response or callback logs so we can investigate this specific failure. Don’t include API keys or secrets.
    Thanks,
    Cody
4

Hi Jim, thanks for the data point about your Zaps firing on new jobs. Hayden, checking your subscription status and callback logs, as described above, is the best next step.

Thanks,
Cody

5

I habe checked and recreated. The webhook fires on job creation via the servicem8 dashboard and phone app. But shortly after switching to next (unlikely the issue just a timing thing) but i think maybe something in any update surround8ng thr new release might have broken something or changed a requirement.

-Event hook is active
-It fire when job created via normal means
-It fails to fire at all on creation via api either from my app or even the try it section of the docs
-Recreating the hook has no effect.
-using job object hook and listening for changes on uuid, customer and created by staff, does fire and 8ve updated my code to have that as a fall bacl untill the even hook is back up.

6

Hi Hayden,
The distinction you’ve found between dashboard/app creation and API creation is the key detail to include in the support report, especially your reproduction using the API reference’s Try It feature.
job.created is the event for a new job created in the system. Your object-webhook fallback has different semantics: it notifies you when subscribed fields change, rather than representing a specific business event. Its payload contains the job UUID and changed field names, not their values; use resource_url to retrieve the job before deciding whether to run the financing workflow.
Please email support@servicem8.com with an example API-created job UUID, the request timestamp and timezone, a sanitised request body and response, your event subscription details, and relevant callback logs. Include that dashboard/app creation triggers the event and recreating the subscription hasn’t changed the result. Don’t include API keys, tokens, secrets or customer personal information.
We’ll confirm whether API-created jobs have any additional event-triggering requirements with the team.
Thanks,
Cody

7

Im aware of all of that. The object webhook onky exists because i built it after the event hook began failing from api job creation. Ive built about 5 addons now, so i am very familliar with a lot of the api including things that ate mislabeld or inconsistent acfross the api docs (minor things here or tgere that may have not been updates. Lime the response requirement of the eventResponse object used to not be properly outlined in the docs and defaulted to a response type in the examples not working for the addons at the time.

I was using my job creation addon and webhook successfully for months. But the i switched to next/15 and it broke at that time/shortly thereafter. So i tested to see if the object uodate hooks still functioned and built a handler to pare either the objeft or the event regardless to make sure nothing is missed.

Nothing had chenged other than that, and there is not any response. There is no indication of the job.created being fired at all when the job is created via api. The job gets created and the objeft hook fires perfectly but there is not any indication that job.created fired at all. Not error in the webhook record. It is active and shows no faulures or null responses it hust does not fire for jobs created via the api as it did a few weeks back before switching. For now it is a non issue as i was able to just build out a dupe check and have the endpoint handle both event and object hooks.