Zendesk trigger failing

Questions
1

Zendesk Trigger node is throwing error. For the first time after creation of node it successfully listens to the trigger but after first time it starts throwing error.

What is the error message (if any)?

Problem running workflow "Bad request - please check your parameters Show Details Zendesk Trigger: 400 - “”
I checked the network tab and saw that the the condition object in parameters is being sent as empty object even though i selected option “all” with desired values of conditions.

Try executing the node up to 10 times. It will eventually fail forever. Creating a new trigger for zendesk will work again, then after about 10 executions it will fail.

image
image655×358 18.2 KB

2

Could you provide your workflow json so we can better understand your setup and context?

3

You already saw this post? It seems to be the same issue, and doesn’t seem to have ever been reproduced/answered. Just context that this doesn’t seem to be a “new” issue. There are also quite a few similar issues reported with the Zendesk trigger. This one has some info related to the webhook id that might give you something to investigate.

4

Yes saw that post. Not sure why you guys let the topics close so early so we can continue on ongoing issues.

Either way. I think to reprpoduce this you have to do trigger the trigger about 10 times or so not once per the other guys suggestion.

5

Where can i get you the workflow json from?

6

Ctl a on the workflow, ctl c on it, then paste into the field that appears when clicking the ‘</>’ button

7

Here’s the json

8

this is what I see

image
image982×1842 60.9 KB

9

Were you able to subscribe to that webhook url via zendesk?

What URL does it show? Is it a localhost:5678? That will not work, it needs to be a publicly accessible domain.

10

I am experiencing the same issue. We have a workflow that has been running for months, yesterday it stopped being triggered on new Zendesk tickets.

I checked the Zendesk webhook history, and it showed me that n8n started returning a 404 for the webhook URL (again, the workflow hasn’t been edited in months).

The 404 error mentioned something about the workflow being inactive, so I checked it, it was active. I tried to deactivate and then reactivate it, hoping toggling would reset its status, and now I cannot activate it. I get an error, simply “400 -” with no explanation.

I also cannot test execute the workflow, whenever start listening for a test trigger, I get the same “400 -” error right away.

There are a number of other unresolved posts in this forum about a “400 -” error with the Zendesk trigger, I really hope this one stays open until resolution.

Note, I do not have to try executing it 10 times before I get the error, it happens right away.

11

An update - after trying so many things: duplicating the workflow, making a new one from scratch with the same trigger/nodes, making a new connection token in Zendesk, and about 100 failed attempts to test the workflow executions, I just tried activating the original workflow, and it successfully activated. I sent a test webhook from Zendesk, and it executed successfully.

I had saved zero changes to the trigger, nodes, or credentials on that workflow, it just randomly started working again.

I burned 2 hours on this, I really hope that someone takes an interest in sorting out these Zendesk Trigger “400 -” issues, because it seems really impossible for users to debug.

12

I am having the same issue. It occurs after 10-20 test executions. The only way I can get it to work again is to remove the node and add it back again with an identical configuration. Had to do this 4 times already today. Any help appreciated.