Start from real support events
Workflows can react to configured message, visitor, ticket, schedule, or manual events and evaluate bounded conditions before taking action.
- Event and manual triggers
- Business-hours conditions
- Versioned published workflows
Route, respond, and connect
Actions can assign work, send a configured response, request AI assistance, create a ticket, delay safely, or call a validated webhook.
- Conversation routing
- Ticket and message actions
- SSRF-protected webhooks
Keep delayed work durable
Delayed and retried executions live in PostgreSQL with claim, retry, and recovery behavior. Redis coordinates workers but is not the source of workflow correctness.
- Durable execution records
- Bounded retry behavior
- Reviewable failures and history
Related ZoeRelay capabilities
Frequently asked questions
Do automations continue after a server restart?
Durable workflow state is stored in PostgreSQL so delayed and retryable work can be recovered by the worker.
Can a workflow call an external API?
Yes, through validated webhook actions that keep private, link-local, and metadata destinations blocked.
Can automation create human follow-up?
Yes. Workflows can assign a conversation, request handoff, or create a ticket for an operator.