Fail to capture data sent through Webhook in Zendesk
I am using Webhook to get data from Zendesk to Zapier. The Webhook in my Zendesk is linked to a trigger, which I have tested to be effective. And to test the Webhook, I have
1) done the “test Webhook” from the Webhook setup page directly;
2) created a new ticket to perform the action that can trigger this Webhook
In the Activity Log of the Webhook, I found both tests successful. However, only data from “test Webhook” was successfully sent to my Zap. I cannot see data from the ticket I created.
Below is a screenshot of the activity log of my Webhook triggered by the ticket. It shows as successful and also documented the data that are supposed to be sent to my Zap. Does anyone know what causes this trouble?
Page 1 / 1
After testing, I believe it has something to do with the playload. Here is the playload I’m using:
When I use this playload, it fails to send any data to Zapier. But when I copy the playload from “test Webhook” to the trigger (this is where I write the playload and decide what data to send through the Webhook), I can successfully send data to Zapier. Here is the test playload from “test Webhook:
{ "custom": "payload" }
or this one:
{ "ticket": { "id": 35436, "priority": "high", "status": "open", "subject": "Help, my printer is on fire!", "description": "The fire is very colorful.", "tags": i "enterprise", "other_tag" ] } }
Then I tried to gradually replace the test playload with the actual data fields I need to send to see which one causes the problem. I was stuck on brand name. However, I copied the placeholder of brand name from Zendesk directly, and it is not a custom field. I don’t understand why it doesn’t work. Can anyone help me?
Hi @Emma_YUN
Issue is likely related to field values not being surrounded in double quotes. e.g. “XXX”
Do for these:
status
brand name
grievance category
If the ID value is not a number, then also do for: id
Thanks Troy! My problem has been resolved, and the point you raised is indeed one issue of my original playload. For any future user’s reference, here is my new playload for Zendesk that works fine:
Make sure you are using the right form of placeholders based on the type of the data field. You may refer to Zendesk’s guidelines on placeholders of different data fields
Thanks so much @Emma_YUN for following up here to share how you got it solved. I’ll go ahead and mark your latest reply as the best answer, since it’ll be super useful for anyone running into the same issue.
And want to give a shout out to @Troy Tessalone for helping to point you in the right direction!
Seems like you’ve got things sorted for now, but please do reach back out if you need help with anything else at all.