Create once, reuse everywhere with @globals
If you just need the essentials, follow this quick path:
- Choose what should be a global (shared constants, not contact data)
- Create the global in the @ Globals section
- Check “Uses” to audit where it’s referenced
- Reference it in flows as @globals.value_name
- Update centrally and retest affected flows
Globals reduce copy-paste errors and make updates safer—especially for URLs, IDs, and authorization strings used in webhooks.
Step-by-Step Process
Use globals for values that are:
- Repeated often (API authorization strings, constant URLs, organization name, shared IDs)
- Used across multiple flows (especially integrations and shared message content)
- Likely to change later (so you want one safe update point)
Avoid globals for:
- Contact-specific data (use
@contact/@fields) - Run-specific answers collected during a flow (use
@results)
- Go to your Flows page.
- Scroll to the @ Globals section.
- Open the Globals page.
- Click New global (or Create Global).
- Enter a Name (example:
api_key). - Enter a Value (example: an Authorization string your webhook will reuse).
- Click Create.
[CAPTURE: Globals page with “New global” / “Create Global” button.]
- On the Globals page, find the global you want to review.
- Click Uses next to it.
- Review every place it’s referenced (flows, broadcasts, campaigns).
This helps you:
- Audit dependencies
- Confirm updates won’t break something unexpectedly
[CAPTURE: “Uses” link next to a global variable.]
Once created, reference it in your flow as:
@globals.api_key(example)- Or generally:
@globals.value_name
Example use case (Airtable/webhooks):
- You create multiple Call Webhook actions.
- Instead of pasting the same authorization string each time, you reference
@globals.api_key. - When the value changes, you update the global once—every webhook is updated automatically.
[CAPTURE: Call Webhook node showing @globals.api_key used in a header (Authorization).]
- Go back to the Globals page (globals aren’t edited directly inside a flow).
- Update the global value.
- Check Uses to understand what will be affected.
- Test affected flows in the Simulator (especially for webhooks and integrations).
Common Issues & Quick Fixes
My global doesn’t appear in the variable list
Problem: You created a global, but you can’t find it while editing.
Fix:
- Confirm the global exists on the Globals page.
- Type
@globals.and use the auto-complete list. - Make sure you’re editing a field that supports variables (message text, headers, etc.).
The webhook still fails after switching to a global
Problem: The call fails even though you replaced a pasted value with @globals.*.
Fix:
- Confirm the global value is correct (no extra spaces, correct prefix like Bearer if required).
- If the global is used in a header, verify the header format matches your provider’s expected value.
- Test the flow in the Simulator and check webhook event logs for the exact error.
I tried to edit a global inside the flow, but can’t
Problem: You expected to update the global value from within a node.
Fix:
- Globals can only be edited from the Globals page (not within flows).
- Update the global centrally, then retest your flow.
Renaming a global breaks references
Problem: Flows that referenced the old name stop working or show blank values.
Fix:
- Avoid renaming globals once widely used.
- If you must rename, use the Uses list to update every reference.
- Retest each affected flow (Simulator + webhook events if applicable).