Docs
Webhooks
Webhooks
Trigger workflows from external events and notify downstream systems when workflows complete.
Webhooks allow external systems to trigger workflows in Cascades and receive workflow updates when execution completes.
They are commonly used to connect operational systems without requiring direct API integrations.
Inbound webhooks
External platforms can trigger workflows by sending events into Cascades.
Common sources include:
- CRM platforms
- internal systems
Common triggers include:
- deployment events
- subscription updates
- incident alerts
- onboarding workflows
- operational events
Outbound webhooks
Cascades can notify external systems when workflows complete.
Examples:
- incident systems
- customer platforms
- internal APIs
- compliance systems
These notifications can include:
- workflow status
- execution metadata
- proof references
- failure details
Security
Webhook integrations should use:
- signing secrets
- authentication validation
- replay protection
- least privilege access controls
Reliability
Webhook-triggered workflows benefit from:
- retries
- queue workers
- failure recovery
- execution visibility
See Queue Workers for execution scaling guidance.
Getting started
Use the Quickstart and API Reference to configure webhook integrations.