Callback clarity
Make event callbacks easy to recognize in the workflow design.
Webhook trigger
Webhook for customer-owned automation.
Use the Webhook trigger when a vendor or customer system calls CXFabric after an event happens.
Start flows from HTTP callback events and make callback-driven automation explicit.
Webhook
Trigger
WebhookStart 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 Webhook as a visible flow step.
The CXFabric docs describe the Webhook trigger as behaving like a REST trigger with the same configuration options. Choosing Webhook makes the HTTP callback pattern explicit for flow developers and operators.
REST-style controls
Use security, header, CORS, and response behavior similar to REST triggers.
Event intake
Capture payloads from vendor systems and route them into parsing, validation, and downstream actions.
Use cases
Where Webhook fits in automation.
These examples show how this component can become part of production workflows across customer-owned systems and environments.
Booking event
Use Webhook 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
Payment update
Use Webhook 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
Ticket status change
Use Webhook 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
Order event
Use Webhook 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
Message delivery status
Use Webhook 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
Vendor callback
Use Webhook 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.
Receive callback payload
Expose this behavior as a reusable, logged, credential-aware step inside a CXFabric flow.
Validate headers or token
Expose this behavior as a reusable, logged, credential-aware step inside a CXFabric flow.
Parse event body
Expose this behavior as a reusable, logged, credential-aware step inside a CXFabric flow.
Acknowledge sender
Expose this behavior as a reusable, logged, credential-aware step inside a CXFabric flow.
Route by event type
Expose this behavior as a reusable, logged, credential-aware step inside a CXFabric flow.
Log callback outcome
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
Validate signatures where vendors support them
Validate signatures where vendors support them.
CXFabric approachMake the behavior explicit in the workflow so operators can see what happens before and after this component runs.
Log source event IDs to prevent duplicate processing
Log source event IDs to prevent duplicate processing.
CXFabric approachMake the behavior explicit in the workflow so operators can see what happens before and after this component runs.
Return fast acknowledgements for systems with strict webhook timeouts
Return fast acknowledgements for systems with strict webhook timeouts.
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 Webhook.
These are concept patterns that can be adapted to a customer's systems, policies, credentials, and deployment model.
Webhook in a customer intake flow
Start with an event, use Webhook, then route the result to CRM, ticketing, or a customer-owned system.
Webhook with approval and audit
Add validation, human approval, and logging around the component before downstream actions execute.
Webhook in a private runtime
Deploy the component inside a customer-owned environment with credentials and logs governed by the customer.
Webhook plus custom connector
Combine the component with packaged connectors or custom APIs when the process needs reusable system logic.
Component planning
Need Webhook inside a customer workflow?
We can scope the workflow, component configuration, credentials, deployment model, and handoff path before buildout begins.