Workflow Engine
Event-driven. Visual builder. Cross-product automation.
Automate your streaming operations. React to events, schedule tasks, and chain WAVE products into workflows — visually or in code.
Automate everything
If it happens on WAVE, you can automate the response. Event-driven workflows that connect every product.
Event-driven triggers
React to 40+ stream events: stream start, viewer milestone, quality drop, recording complete. Chain multiple actions per trigger.
Conditional logic
If/else branching based on stream metadata, viewer count, time of day, or custom conditions. Route workflows dynamically.
Retry and recovery
Automatic retry with exponential backoff. Dead letter queues for failed steps. Manual replay of any workflow run from any step.
Scheduled operations
Cron-style scheduling for recurring tasks. Schedule stream starts, recording cleanup, report generation, and CDN cache purges.
Visual workflow builder
Drag-and-drop workflow designer. Connect triggers, conditions, and actions visually. Real-time preview of workflow execution path.
Cross-product orchestration
Chain any WAVE product in a workflow. Start a stream, enable captions, notify Slack, clip highlights, and archive — all automated.
Technical specifications
Three steps to automation
Choose a trigger
Select from 40+ events or define a schedule. Stream started, viewer count reached, quality degraded — pick your trigger.
Build your workflow
Add actions, conditions, and delays using the visual builder or TypeScript SDK. Chain WAVE products and external APIs.
Deploy and monitor
Activate the workflow. Monitor runs in real-time. Debug failures with step-by-step execution logs and replay.
Built for operational automation
Frequently asked questions
What events can trigger a workflow?
Any WAVE platform event: stream.started, stream.ended, viewer.milestone (100, 1K, 10K), quality.degraded, recording.complete, billing.threshold, and 30+ more. Custom webhook events from external systems are also supported.
How does the workflow engine handle failures?
Each step has configurable retry policy (count, backoff strategy, timeout). Failed steps go to a dead letter queue with full context. You can replay any run from any step. Alerting via Slack, email, or PagerDuty on persistent failures.
Can workflows call external APIs?
Yes. HTTP action steps can call any REST API with configurable headers, auth, and payload templates. Response data flows into subsequent steps. Rate limiting and circuit breakers protect external endpoints.
Is there a visual builder or is it code-only?
Both. The visual builder supports drag-and-drop workflow creation for non-developers. Developers can define workflows in TypeScript using the WAVE Workflow SDK with full type safety and version control.
Automate your streaming ops
Start building workflows. Free tier includes 1000 runs per month.