Unable to publish workflow

[terraxus]

Issue

Unable to publish workflow and the error I’m getting is not giving me any info on why

Error

There’s no visible errors on nodes, the workflow was tested through and through with mock data and I’ve gotten this error only now when I tried to publish the workflow

n8n info

Version 2.9.4

Cloud

Workflow

Posting only part of the flow as I was limited by the ticket char number

[A_A4]

Hi @terraxus

manual tests with zendesk trigger work fine because they just listen for events locally and don’t actually register anything with the live service. but when you hit publish, n8n tries to physically create the webhook and trigger rules inside your zendesk account via their api.

if you look closely at the json for your zendesk trigger node, your condition is missing pieces. it shows you have a value set to new, but there’s no field or operator attached to it.

just open your zendesk trigger node and fix that condition block. make sure you select an actual field (like status) and an operator to go along with that new value.
Good luck!

[terraxus]

Hey, thanks for the quick follow up. Could you elaborate on what you mean by “no operators attached to it”?

I created a new Zendesk trigger node, set it up the exact same way and now it’s working. The issue is, from the UI both trigger nodes look exactly the same - as if they’re fully set up and working.

TBH even looking at the JSON of both nodes the difference to me isn’t obvious. Could you help me understand what’s different/wrong?

Thanks again for the help

Old node

New, working node

[A_A4]

@terraxus
i have to correct myself. you’re 100% right ,the condition blocks are literally identical.
the real difference is at the very end of your JSON blocks.

look at the credentials object:

• old node: "credentials":{}
• new node: "credentials":{"zendeskApi":{"id":"yDBGaacw8ekSNOp4"...}}

your old node completely lost its connection to your zendesk account. when you clicked publish, n8n sent a blank authentication payload to zendesk, which instantly triggered the 400 bad request error.
glad you got it working!