Workflows & automation
Handling a call end-to-end is a hundred tiny branching decisions
Look up the account. Check the order. Route the refund. Escalate if the amount is high. Notify on a stalled case. Each step is trivial; hard-coding every branch into one agent is a tangle that never scales.
What's in the box.Each one in the product today.
- 01
Event-driven triggers
Start a workflow on any platform event — a call started, an intent detected, a tool result, a case escalated.
- 02
Node-graph builder
Compose triggers, conditions, delays, and actions on a visual canvas. No code.
- 03
Conditional branching
All / any / not condition trees route each run down the right path.
- 04
Timers & delays
Wait seconds or days between steps; sweep timers advance runs on schedule.
- 05
Rich action set
Call a tool, hand off to another agent, transfer to a human, send a message, or fire a signed webhook.
- 06
Enrollment filters
Scope which conversations enter a workflow so the right calls get the right path.
One event bus, drained by a dispatcher, powering everything
Every meaningful moment in a conversation emits an event onto the bus. A background dispatcher drains it, advances timers, and fans work out to nodes. Workflows, agent-to-agent handoff, human escalation, and webhook delivery are all consumers of the same rail.
- Bus
- durable
- Dispatcher
- polling
- WorkflowsIdle
- Agent hand-offIdle
- EscalationsIdle
- WebhooksIdle
- starting…
A visual node graph anyone on your team can reason about
Triggers, conditions, delays, and actions are nodes you wire together on a canvas — no code, no YAML. Condition nodes carry all/any/not trees, timer nodes hold a run for seconds or days, and an enrollment filter decides exactly which conversations ever enter the flow.
- Conversation
- C-2204
- Agent
- Admissions
- Trigger conversation.ended
- Filter agent = Admissions · phone
- Condition all(not booked, sentiment ≠ negative)
- Delay 1 day
- send_message WhatsApp · callback_confirmation
- starting…
Explore the platform.
It works with the rest of Mirakash. Here is what connects to it.
- Realtime voice pipelineSub-second STT→LLM→TTS with barge-in, on ~11 pluggable provider adapters or native Gemini Live.
- Telephony & numbersProvision phone numbers in one click across three account models — inbound, outbound, encrypted at rest.
- API & connectorsServer actions and an API, real env-gated connectors, {{VAR}} interpolation, and agent tools that call your endpoints.
- Use casesA real conversation for six desks, start to finish.
- SecurityRoles, redaction, retention and the audit trail.
- PricingPer minute or per resolution, and what each includes.