Runtime state
Read or write short-lived state that other services or flow steps can use.
Redis component
Redis for customer-owned automation.
Use Redis when a workflow needs quick shared state or coordination with Redis-backed systems.
Interact with Redis for fast runtime state, lookup data, and workflow coordination.
Redis
Component
RedisReach databases, transfer files, and coordinate runtime state inside customer environments.
CX
CXFabric Flow
Rules, credentials, validation, audit
SettingsInputs and options
LogsRun history and output
Next stepConnector, component, or approval
What this component unlocks
Use Redis as a visible flow step.
Redis appears in the CXFabric component docs as both a trigger family and a component entry. Use the Redis component for workflow operations against Redis, and Redis Trigger when Redis events should start a flow.
Fast lookup
Use Redis-backed values to enrich decisions without hitting heavier systems.
Coordination
Coordinate workflow behavior around keys, topics, or cached data.
Use cases
Where Redis fits in automation.
These examples show how this component can become part of production workflows across customer-owned systems and environments.
Session lookup
Use Redis 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
Runtime cache
Use Redis 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 marker
Use Redis 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
Queue coordination
Use Redis 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
Feature flag lookup
Use Redis 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
Stateful routing
Use Redis 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.
Select Redis credential
Expose this behavior as a reusable, logged, credential-aware step inside a CXFabric flow.
Read value
Expose this behavior as a reusable, logged, credential-aware step inside a CXFabric flow.
Write value
Expose this behavior as a reusable, logged, credential-aware step inside a CXFabric flow.
Update state
Expose this behavior as a reusable, logged, credential-aware step inside a CXFabric flow.
Coordinate with event topic
Expose this behavior as a reusable, logged, credential-aware step inside a CXFabric flow.
Log Redis operation
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
Separate Redis Trigger and Redis Component usage
Separate Redis Trigger and Redis Component usage.
CXFabric approachMake the behavior explicit in the workflow so operators can see what happens before and after this component runs.
Plan key naming and expiration
Plan key naming and expiration.
CXFabric approachMake the behavior explicit in the workflow so operators can see what happens before and after this component runs.
Avoid storing sensitive data without customer approval
Avoid storing sensitive data without customer approval.
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 Redis.
These are concept patterns that can be adapted to a customer's systems, policies, credentials, and deployment model.
Redis in a customer intake flow
Start with an event, use Redis, then route the result to CRM, ticketing, or a customer-owned system.
Redis with approval and audit
Add validation, human approval, and logging around the component before downstream actions execute.
Redis in a private runtime
Deploy the component inside a customer-owned environment with credentials and logs governed by the customer.
Redis plus custom connector
Combine the component with packaged connectors or custom APIs when the process needs reusable system logic.
Component planning
Need Redis inside a customer workflow?
We can scope the workflow, component configuration, credentials, deployment model, and handoff path before buildout begins.