CloudFlow — Variables for repeatable, low-friction automations

CloudFlow now supports workflow-level variables.

• Global variables sit in one central file and are visible to every CloudFlow in the org.
• Local variables live inside a single flow and override globals for that flow only.

Here is why this is important:

• Eliminate hard-coded values: Replace literals (account IDs, regions, bucket names) with named parameters. Edit once, redeploy, and every pipeline inherits the new value, no wide-scale manual search-and-replace.
• Promote safely across environments: Ship the same CloudFlow file from dev → staging → prod by swapping variable sets instead of editing the flow itself, which reduces config drift.
• Constrain blast radius: Keep experimental or high-risk values quarantined with local variables, while global variables let you roll out org-wide changes.
• Reduce manual error: Fewer touch points mean fewer typos, missing regions, or mis-tagged resources—improving reliability and cost-allocation accuracy.
• Speed up multi-region replication: Clone a flow, update the region variable list, and publish. The deployment logic stays intact; only the parameter set changes.
• Automate cost governance: Tie spend thresholds, budgets, or anomaly detectors to variables. When account structures evolve, you update the variable once, and all alerts/remediations inherit the new scope automatically.

To learn more about variables and how to create them, check out our Help documentation or raise a ticket with the DoiT support team.