Zendesk Trigger workflow intermittently fails activation with Cannot read properties of undefined (reading 'toString')

[nikolabreljak]

Describe the problem/error/question

Our workflow using a zendeskTrigger node intermittently loses its activation. The workflow shows as "active" with a red warning triangle, but the trigger stops firing. No failed executions appear in the execution history because the trigger itself is dead.

Re-activating the workflow (toggle off, toggle on) immediately fixes the issue, but it recurs unpredictably, sometimes daily, sometimes after a few days. The workflow configuration has not changed between working and broken states (confirmed by comparing exported JSON).

The Zendesk Trigger node is configured correctly (Resource: Ticket, Field: Status, Operation: Changed To, Value: New). The issue appears to be related to webhook re-registration during n8n cloud platform restarts or deploys.

What is the error message (if any)?

Problem activating workflow
The following error occurred on workflow activation:
Cannot read properties of undefined (reading 'toString')

Please share your workflow/screenshots/recording

Minimal reproduction: any workflow with a zendeskTrigger (typeVersion 1) node configured with a condition (e.g., status changed to "new"). The issue is intermittent and appears to occur during platform-side re-activation, not during manual activation.

Exported trigger node config:

{
  "parameters": {
    "options": {
      "fields": ["ticket.id"]
    },
    "conditions": {
      "all": [
        {
          "operation": "value",
          "value": "new"
        }
      ]
    }
  },
  "type": "n8n-nodes-base.zendeskTrigger",
  "typeVersion": 1
}

Note: the exported JSON does not include a field key in the condition, but the UI shows it correctly as "Status". This serialization gap may be related to the bug, as the re-activation code path may not be resolving the field the same way the UI does.

Share the output returned by the last node

N/A. No executions are produced when the activation fails. The trigger simply stops firing.

[n8n-assistant]

Hey @nikolabreljak,

Thank you for reaching out! We’ve received your issue and are looking into it. To help us track this internally, we’ve created a Linear ticket with the reference: "GHC-7422".

We’ll keep you updated as we make progress, but if you have any additional details or context to share, feel free to add them here - it’s always helpful!

Thanks for your patience and for bringing this to our attention.

---

For INTERNAL use only: GHC-7422