Page 1 of 1

[Relased]Webhook event not being triggered

Posted: Sun Jul 25, 2021 10:12 pm
by Alex
When I change a job status from the "Edit Job" interface the "job.updated" event is being sent and the webhook works as expected, but when a job status is assigned from the "With selected" mass update tool in the Pending job list view it doesn't trigger any webhook events.

Please fix that.

Re: Webhook event not being triggered

Posted: Sun Jul 25, 2021 11:35 pm
by robbertcha
Hi Alex,

We will look into it and get back to you with any update on the issue here, thank you

Re: Webhook event not being triggered

Posted: Sat Jul 31, 2021 5:23 pm
by Alex
robbertcha wrote: ↑Sun Jul 25, 2021 11:35 pm Hi Alex,

We will look into it and get back to you with any update on the issue here, thank you
Any updates on the issue?
It's really important guys! This problem makes webhooks a very questionable solution.

Re: Webhook event not being triggered

Posted: Sun Aug 01, 2021 11:07 pm
by robbertcha
Hi Alex,

The feature has been done and will be published in the coming release, do you mind to tell us your build via private message & we will inform you when you build is updated, thank you

Re: Webhook event not being triggered

Posted: Mon Aug 09, 2021 10:43 am
by Alex
The problem doesn't seem to be fixed. Have you updated the build already?

Re: Webhook event not being triggered

Posted: Mon Aug 09, 2021 11:44 pm
by robbertcha
Hi

Since the release of version 21.3.3 (9 Aug 2021), new job status webhook triggers have been introduced, which means for the action on UI where you can update status for multiple jobs would only trigger Job Status trigger. The nz sandbox has been upgraded to the latest version.

The status trigger has also been introduced for leads and quotes.

Re: Webhook event not being triggered

Posted: Tue Aug 10, 2021 5:11 pm
by Alex
Yes, the new webhook works and it will do for my case.
Much appreciate your help.

On a side note, the new webhook seems a little bit ad-hoc solution as I suspect changing other job properties with the mass update tool won't trigger the job change webhook either and you would have to create a new webhook for every other property you can update from there.
As a user of the API, I'd prefer one "job.updated" event having some information about the fields that were updated, no matter what way these fields were updated.