Hi everyone,
Just a quick note the docs say that the changes
key is under data
for ticket update event , like this:
"data": {
"changes": { ... }
}
But when the event is actually triggered, the changes
key is under data.ticket
:
"data": {
"ticket": {
"changes": { ... }
}
}
This might help if you’re wondering why your code isn’t picking up the changes properly. Hope this saves someone some time!
1 Like
Hi Guys!
Now I tried this again but I can’t even seem to find the ‘changes’ key
console.log(Object.keys(args))
console.log(Object.keys(args.data))
console.log(Object.keys(args.data.ticket))
Thank you
Raviraj
(Raviraj Subramanian)
May 15, 2025, 7:57am
4
Hi Benny,
With your same code, I have tested a custom app on my testing account. I can find the changes
attribute on the payload at args.data.ticket.changes
.
Have you checked by changing any default fields? Change event will not be triggered for custom fields and tags.
Hi @Raviraj ,
Yes, we did tried to update the default fields like group.
And I’m pretty sure that updating other fields wouldn’t have triggered the event in the first place.
Here I have logged all the keys in side the ticket object, where the changes supposed to be.
Could you please take a look at it again?
Thank you.