Topic-based execution
Start flows from the Redis topics that matter to the customer environment.
Redis Trigger
Redis Trigger for customer-owned automation.
Use the Redis Trigger when a Redis client publishes an event that should start a workflow.
Start flows from Redis topic events and event-based runtime state.
Redis Trigger
Trigger
Redis TriggerStart workflows from external events, schedules, realtime signals, and API calls.
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 Trigger as a visible flow step.
The docs describe Redis triggers as event-based flow execution. When a Redis client sends an event to a monitored topic, the flow begins executing through an automatically generated endpoint URL.
Realtime runtime signals
Turn cache, queue, or application events into workflow runs.
Generated connection endpoint
Connect Redis clients to a CXFabric-managed endpoint for monitored events.
Use cases
Where Redis Trigger fits in automation.
These examples show how this component can become part of production workflows across customer-owned systems and environments.
Realtime application event
Use Redis Trigger 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 handoff
Use Redis Trigger 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
Cache invalidation workflow
Use Redis Trigger 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 state change
Use Redis Trigger 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
Internal service signal
Use Redis Trigger 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
Operational alert
Use Redis Trigger 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.
Configure monitored topic
Expose this behavior as a reusable, logged, credential-aware step inside a CXFabric flow.
Connect Redis client
Expose this behavior as a reusable, logged, credential-aware step inside a CXFabric flow.
Receive event payload
Expose this behavior as a reusable, logged, credential-aware step inside a CXFabric flow.
Route by event body
Expose this behavior as a reusable, logged, credential-aware step inside a CXFabric flow.
Trigger downstream flow
Expose this behavior as a reusable, logged, credential-aware step inside a CXFabric flow.
Log event processing
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
Name topics clearly
Name topics clearly.
CXFabric approachMake the behavior explicit in the workflow so operators can see what happens before and after this component runs.
Design for retries and duplicate events
Design for retries and duplicate events.
CXFabric approachMake the behavior explicit in the workflow so operators can see what happens before and after this component runs.
Keep payload schemas stable across producers
Keep payload schemas stable across producers.
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 Trigger.
These are concept patterns that can be adapted to a customer's systems, policies, credentials, and deployment model.
Redis Trigger in a customer intake flow
Start with an event, use Redis Trigger, then route the result to CRM, ticketing, or a customer-owned system.
Redis Trigger with approval and audit
Add validation, human approval, and logging around the component before downstream actions execute.
Redis Trigger in a private runtime
Deploy the component inside a customer-owned environment with credentials and logs governed by the customer.
Redis Trigger plus custom connector
Combine the component with packaged connectors or custom APIs when the process needs reusable system logic.
Component planning
Need Redis Trigger inside a customer workflow?
We can scope the workflow, component configuration, credentials, deployment model, and handoff path before buildout begins.