Workflows & automation
Mirakash runs on an event bus, and Workflows is how you program it. Build automations on a visual node graph: trigger on any event, branch on conditions, wait on timers, and fan out to actions — call a tool, hand off to another agent, escalate to a human, or fire a webhook.
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.
The flow, end to end
Trigger
An event hits the bus — a call starts, an intent is detected, a tool returns, an SLA breaches.
Evaluate
The dispatcher drains the event and evaluates each workflow's trigger and enrollment filter.
Branch
Condition nodes route the run; timer nodes hold it until the wait elapses.
Act
Action nodes execute — call a tool, hand off, transfer to a human — and often emit new events.
What's in the box
Event-driven triggers
Start a workflow on any platform event — a call started, an intent detected, a tool result, a case escalated.
Node-graph builder
Compose triggers, conditions, delays, and actions on a visual canvas. No code.
Conditional branching
All / any / not condition trees route each run down the right path.
Timers & delays
Wait seconds or days between steps; sweep timers advance runs on schedule.
Rich action set
Call a tool, hand off to another agent, transfer to a human, send a message, or fire a signed webhook.
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.
- ✓Durable event bus + polling dispatcher — no lost events
- ✓Tools, handoffs, escalations, and webhooks on one rail
- ✓Actions emit events, so workflows chain without glue code
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.
- ✓Trigger on any event; an enrollment filter scopes what enters
- ✓All / any / not condition trees route each path
- ✓Delays and timer sweeps advance runs on schedule
Realtime voice pipeline
Sub-second STT→LLM→TTS with barge-in, on ~11 pluggable provider adapters or native Gemini Live.
Learn moreTelephony & numbers
Provision phone numbers in one click across three account models — inbound, outbound, encrypted at rest.
Learn moreAPI & connectors
Server actions and an API, real env-gated connectors, {{VAR}} interpolation, and agent tools that call your endpoints.
Learn moreReady to put an AI agent on every call?
Book a walkthrough and see the voice pipeline, telephony, workflows, QA, and human handoff working together — on one platform.