Shared state
Hold values that multiple components need to read or update.
Variables component
Variables for customer-owned automation.
Use Variables when several components need to share the same values or when data changes during execution.
Store, update, and pass values through a workflow as the automation progresses.
Variables
Component
VariablesStore, update, and pass reusable values between workflow steps.
CX
CXFabric Flow
Rules, credentials, validation, audit
SettingsInputs and options
LogsRun history and output
Next stepConnector, component, or approval
What this component unlocks
Use Variables as a visible flow step.
The docs describe Variables as containers for storing and manipulating data such as text, numbers, dates, and objects inside a flow. A Variables component can hold multiple variables, and each variable can optionally have a default value. Variables can be updated dynamically, used throughout the flow, and used to pass or transform data between workflow steps.
Dynamic updates
Change variable values as the workflow collects, parses, and transforms data.
Multiple variables
Create several named values inside one Variables component and review them later from the canvas tooltip.
Use cases
Where Variables fits in automation.
These examples show how this component can become part of production workflows across customer-owned systems and environments.
Customer ID storage
Use Variables as part of a governed CXFabric workflow that keeps configuration, credentials, logs, and handoffs visible.
- Collect the approved input
- Apply customer-specific rules
- Pass a clear result to the next step
Retry counter
Use Variables as part of a governed CXFabric workflow that keeps configuration, credentials, logs, and handoffs visible.
- Collect the approved input
- Apply customer-specific rules
- Pass a clear result to the next step
Temporary token
Use Variables as part of a governed CXFabric workflow that keeps configuration, credentials, logs, and handoffs visible.
- Collect the approved input
- Apply customer-specific rules
- Pass a clear result to the next step
Parsed field reuse
Use Variables as part of a governed CXFabric workflow that keeps configuration, credentials, logs, and handoffs visible.
- Collect the approved input
- Apply customer-specific rules
- Pass a clear result to the next step
Status tracking
Use Variables as part of a governed CXFabric workflow that keeps configuration, credentials, logs, and handoffs visible.
- Collect the approved input
- Apply customer-specific rules
- Pass a clear result to the next step
Dynamic message data
Use Variables as part of a governed CXFabric workflow that keeps configuration, credentials, logs, and handoffs visible.
- Collect the approved input
- Apply customer-specific rules
- Pass a clear result to the next step
Configuration surface
Practical options builders expect to use.
The exact fields can vary by deployment and product version, but each page gives customers a clear view of the component's intended role.
Add Variables to canvas
Expose this behavior as a reusable, logged, credential-aware step inside a CXFabric flow.
Open component settings
Expose this behavior as a reusable, logged, credential-aware step inside a CXFabric flow.
Create first variable
Expose this behavior as a reusable, logged, credential-aware step inside a CXFabric flow.
Set optional default value
Expose this behavior as a reusable, logged, credential-aware step inside a CXFabric flow.
Add additional variables
Expose this behavior as a reusable, logged, credential-aware step inside a CXFabric flow.
Submit settings
Expose this behavior as a reusable, logged, credential-aware step inside a CXFabric flow.
Execute and review logs
Expose this behavior as a reusable, logged, credential-aware step inside a CXFabric flow.
Implementation notes
Design the step with operations in mind.
Components should be easy for builders to configure and easy for operators to understand after the workflow is live.
Current CXFabric docs
Use descriptive variable names
Use descriptive variable names.
CXFabric approachMake the behavior explicit in the workflow so operators can see what happens before and after this component runs.
Variables can hold strings, numbers, objects, and other workflow data
Variables can hold strings, numbers, objects, and other workflow data.
CXFabric approachMake the behavior explicit in the workflow so operators can see what happens before and after this component runs.
Keep variable purpose clear so future editors understand how data moves through the flow
Keep variable purpose clear so future editors understand how data moves through the flow.
CXFabric approachMake the behavior explicit in the workflow so operators can see what happens before and after this component runs.
Workflow patterns
Reusable patterns for Variables.
These are concept patterns that can be adapted to a customer's systems, policies, credentials, and deployment model.
Variables in a customer intake flow
Start with an event, use Variables, then route the result to CRM, ticketing, or a customer-owned system.
Variables with approval and audit
Add validation, human approval, and logging around the component before downstream actions execute.
Variables in a private runtime
Deploy the component inside a customer-owned environment with credentials and logs governed by the customer.
Variables plus custom connector
Combine the component with packaged connectors or custom APIs when the process needs reusable system logic.
Component planning
Need Variables inside a customer workflow?
We can scope the workflow, component configuration, credentials, deployment model, and handoff path before buildout begins.