Global variables for workflows

Introduce global-level variables that can be defined once and used across all workflows. These variables would store values such as notification email addresses, API keys, or shared configuration data, eliminating repetitive setup and reducing maintenance effort.

Use Case: Currently, users must redefine shared values (e.g., notification recipients, webhook URLs, constants) within each individual workflow or use workarounds like the generic “Config Data” authentication type. This approach is error-prone, difficult to maintain, and scales poorly when managing many workflows. With global variables, users—especially administrators—can define and update values centrally. Any workflows referencing these variables automatically use the latest version, ensuring consistency across the system.

Key Goals:

• Allow users (likely admins) to define and manage global variables in a dedicated UI or configuration section.
• Enable workflows to reference these global variables seamlessly (e.g., via a variable selector or templating syntax).
• Ensure updates to a global variable propagate automatically to all dependent workflows.
• Support secure storage for sensitive values (e.g., API keys, tokens).
• Provide visibility and structure when editing, avoiding the “black box” experience of current Config Data storage.

Implementation Considerations:

Option 1: Enhance the existing “Config Data” authentication type to support structured, user-friendly editing and partial updates.

Option 2: Introduce a new Global Configuration UI, available to admins, for defining and organizing global variables by type or namespace.

Ensure backward compatibility with current workflows using Config Data.

User Value: This feature simplifies workflow management, reduces errors caused by inconsistent or duplicated configuration, and saves significant time when updating shared values. It increases reliability and maintainability across large-scale workflow deployments.