Page 1 of 1

Feature Request : job.updated webhook

Posted: Tue Mar 02, 2021 11:34 pm
by rish
Hi ,

Can we get the the job status as a part of the response of the job.updated webhook ? Since there is no job data in the webhook besides the jobID , we have to fetch the job data seperately through the jobs api. This causes a delay in getting the job info and by the time we get the response the status has moved on to the next state.

For eg. we change status as follows - 1 => 2 => 3 => 4 (quickly within a few seconds)

The webhooks for status 2,3 and 4 all reflect that job status has been changed to status 4. To solve this , if we get the stauses with every webhook , we can get the correct status for the time when the webhook was triggered.

Re: Feature Request : job.updated webhook

Posted: Mon Mar 15, 2021 11:04 pm
by bgur
Would be great if the job updated webhook just specified exactly what had changed.

Something like:

Code: Select all

{
   "property": "stage",
   "changedFrom": "pending",
   "changedTo": "progress"
}

Re: Feature Request : job.updated webhook

Posted: Mon May 24, 2021 11:40 am
by michelle
Managing status changes the way the webhooks work at present is nigh on impossible. Split second changes by admin mean a lot of information is missed particularly when an engineer completes the work and then admin moves it on. Really hurts the KPI reporting so hopefully getting this information in the webhook will alleviate this. Also waiting on more informative webhooks generally for the webhooks as the job.updated webhook triggers even for small changes on the notes or job description.