Zendesk Trigger does not trigger after update
Bug Description
I update N8N today to the latest Version and the Zendesk Trigger does not trigger anymore, but i do not remember from what Version i updated.
To Reproduce
- Install Zendesk Trigger
- Do something in Zendesk
- Tigger should trigger but does not anymore
Expected behavior
Zendesk trigger should run based on condition
Operating System
Ubuntu
n8n Version
1.85.4
Node.js Version
22
Database
SQLite (default)
Execution mode
main (default)
Hey @danielehrhardt,
We have created an internal ticket to look into this which we will be tracking as "GHC-1465"
Similar Ticket: https://github.com/n8n-io/n8n/issues/13329
Hey @danielehrhardt
The Zendesk trigger is webhook based and we rely on Zendesk to send us the date so in theory an update to just n8n shouldn't impact anything.
Have you checked the webhook url to see if it matches what is in Zendesk
Hey @danielehrhardt
The Zendesk trigger is webhook based and we rely on Zendesk to send us the date so in theory an update to just n8n shouldn't impact anything.
Have you checked the webhook url to see if it matches what is in Zendesk
@Joffcom If i start "Test workflow" it works and i get data, but if i enable the workflow then nothing happens anymore. So i guess the webhook in theory works.
Hey @danielehrhardt
Does Zendesk show any errors for the webhook it has been a while since I have checked out the Zendesk admin portal.
Hey @danielehrhardt
Does Zendesk show any errors for the webhook it has been a while since I have checked out the Zendesk admin portal.
Looks like it's not creating the Webhook without test
Somewhere in the activation loop, it tries to remove the webhook and trigger entry from zendesk and after create them again.
The issue is somewhere in this process, the webhook gets successfully deleted but the trigger entry does not and is linked to an none existing webhook afterwords.
Looks like I missed the reply to this, Looking at the activation loop it is the same process for test and production. I have just given this a go on 1.97 though and it appears to be working now.
Can you upgrade and if you are still seeing issues let me know.
lgtm. Thanks! :)
I updated to version 1.98.0, but the issue persists. The application started normally and the webhook was created as expected. However, when I disabled and then re-enabled the workflow, the webhook was not set up again. I also tried restarting the deployment and collected the following logs:
Permissions 0644 for n8n settings file /home/node/.n8n/config are too wide. This is ignored for now, but in the future n8n will attempt to change the permissions automatically. To automatically enforce correct permissions now set N8N_ENFORCE_SETTINGS_FILE_PERMISSIONS=true (recommended), or turn this check off set N8N_ENFORCE_SETTINGS_FILE_PERMISSIONS=false.
User settings loaded from: /home/node/.n8n/config
Initializing n8n process
n8n ready on ::, port 5678
n8n Task Broker ready on 127.0.0.1, port 5679
[license SDK] Skipping renewal on init because renewal is not due yet or cert is not initialized
Registered runner "JS Task Runner" (3pqPbQ3RTz_Pts9TvPtUl)
Version: 1.98.0
Locale: pt-BR
Start Active Workflows:
Bad request - please check your parameters
400 - ""
Issue on initial workflow activation try of "Envio de ticket para o Discord" (ID: yUisxOOK3EkbYmsd) (startup)
Editor is now accessible via:
https://my-address.com
Try to activate workflow "Envio de ticket para o Discord" (yUisxOOK3EkbYmsd)
Activation of workflow "Envio de ticket para o Discord" (yUisxOOK3EkbYmsd) was successful!
After restarting the deployment, on the first activation of the workflow it failed, but then it succeeded—still, the webhook was not set. Interestingly, if I use test mode, the webhook works as expected.
Today I noticed that something that works to reactivate the webhook is to add 2 other Zendesk nodes and save. After that, the webhook is consistently created. Then, just delete the two oldest ones and keep only the last one. Saving the file after that still keeps the webhook active and working. But if I rename the node and save, it stops working again.