Global Workflow Updated Trigger

Emits an item whenever any workflow in the n8n instance has been updated.
Join our community

Overview

This node is a trigger that emits an item whenever any workflow in the n8n instance has been updated. It periodically checks the n8n REST API for workflow updates, filtering out workflows by name using a regex if specified, and emits details about updated workflows. This is useful for monitoring changes across all workflows in an n8n instance, enabling automation or notifications based on workflow updates.

Use Case Examples

  1. Automatically trigger downstream processes or notifications when any workflow in the n8n instance is updated.
  2. Monitor workflow changes to maintain version control or audit logs.
  3. Integrate with external systems to sync workflow updates.

Properties

Name Meaning
n8n Base URL Internal base URL for the n8n REST API, e.g., http://localhost:5678 inside Docker.
Interval (seconds) How often to check for workflow updates, in seconds. Minimum 2 seconds, maximum 3600 seconds.
Exclude by Name (Regex) Regular expression to exclude workflows by name from triggering. Workflows matching this regex are ignored.
Emit Full Workflow JSON If enabled, includes the full workflow object in the output for each updated workflow.
Request Timeout (ms) Maximum wait time in milliseconds for each REST API call. Minimum 1000 ms, maximum 60000 ms.
Max Workflows per Cycle Limits how many updated workflows are emitted per polling cycle. 0 means unlimited. Minimum 1, maximum 10000.

Output

JSON

  • json
    • id - ID of the updated workflow.
    • name - Name of the updated workflow.
    • updatedAt - Timestamp when the workflow was last updated.
    • workflow - Full workflow object if 'Emit Full Workflow JSON' is enabled.

Dependencies

  • Requires access to the n8n REST API, optionally using an API key credential for authentication.

Troubleshooting

  • Ensure the 'n8n Base URL' is correctly set to the internal URL of the n8n instance, especially when running inside Docker.
  • Check that the API credentials (if used) are valid and have permission to access workflows.
  • If no workflows are emitted, verify the 'Exclude by Name (Regex)' setting is not filtering out all workflows.
  • Adjust 'Interval (seconds)' to balance between timely updates and API rate limits.
  • Increase 'Request Timeout (ms)' if the API calls frequently time out due to network latency or server load.

Links

Discussion