Every CloudFlow trigger (scheduled, webhook, and system event) now automatically attaches a managed list of AWS accounts, Google Cloud projects and Azure subscriptions (e.g., "billing scopes"). All new and existing flows now expose  billingScopes - a structured variable containing all your billing scopes, grouped by provider. A companion billingScopesRowCount variable gives you the total count across all providers.

Why It Matters

Previously, if your flow needed to iterate over or reference your cloud billing accounts (e.g., to generate per-account reports, enforce policies across accounts, or conditionally branch based on which providers are active), you had to make separate API calls or hardcode account IDs. Now, this data is available out of the box as part of the trigger context; hence, no extra nodes are needed.

How It Works

When a CloudFlow executes, the trigger node automatically calls the DoiT Cloud Intelligence™ API and populates two new variables:

1. billingScopes: Contains three lists: amazon-web-services, google-cloud, and microsoft-azure. Each entry has id and name
2. billingScopesRowCount: Total number of billing scopes across all three providers

These variables are available for reference in any downstream node — use them in transformations, conditions, API call parameters, or code nodes just like any other trigger variable.

Example Use Cases

• Multi-account flows — loop through billingScopes["amazon-web-services"] to generate cost reports per AWS account.
• Provider-conditional logic — check billingScopesRowCount or the length of a specific provider's list to branch your flow based on which cloud providers are active.
• Dynamic API calls — use billing scope IDs as parameters when calling provider-specific APIs within your workflow.