n8n trigger - When a new workflow is published -> not working

[Diward]

Describe the problem/error/question

The n8n node trigger for "Workflow Published" or "Published Workflow Update" does not work properly. It is only triggered by itself (when the wf with the trigger is published), but it does not triggers when other wf are published.

What is the error message (if any)?

N/A

core

• n8nVersion: 2.1.0
• platform: docker (self-hosted)
• nodeJsVersion: 22.21.1
• nodeEnv: production
• database: postgres
• executionMode: regular
• concurrency: -1
• license: enterprise (production)

Generated at: 2025-12-17T15:37:37.249Z}

[n8n-assistant]

Hey @Diward,

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-5953".

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-5953

[dev-kinsukghosh]

@Diward need workflow and how reproduce
#triage:in-progress

[Diward]

Workflow:

{
"nodes": [
{
"parameters": {
"events": [
"activate",
"update"
]
},
"type": "n8n-nodes-base.n8nTrigger",
"typeVersion": 1,
"position": [
-16,
144
],
"id": "60481d93-c399-4a9c-af45-0564315c18bc",
"name": "n8n Trigger"
}
],
"connections": {},
"pinData": {},
"meta": {
"templateCredsSetupCompleted": true,
"instanceId": "df568310e94a46c5fdb11c5a0ee691216347c3a8211d7a8ccb20e74eac18933b"
}
}

Reproduce:

1. Publish the WF. You will se an execution that appears after the execution. It just that thisWF triggered itself, because this trigger is setted up to avtivate when any WF is published (the WF id showing on the execution is itself id).
2. Go to any other WF and publish it.
3. Check the WF (the one I shared), and there is no new executions triggered.

[luka-mimi]

I’ve run into this issue as well. The n8n trigger only supports triggering when the current workflow is activated. I think this is very likely a bug—otherwise, there’s no point in a workflow listening to and triggering itself.

[dev-kinsukghosh]

this bug check out same for me it not working the only execution is of itself
#triage:complete

[dev-kinsukghosh]

also @Diward as u are a enterprise user can create high priory ticket if urgent