> ## Documentation Index
> Fetch the complete documentation index at: https://docs.unpod.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Flows & Journeys

> Durable communication workflows - versioned step sequences that entities traverse over hours or days.

Flows & Journeys are durable communication workflows. A **flow** is the plan: a
versioned sequence of steps - call, message, wait, branch, human approval,
exit. A **journey** is one entity's traversal of one flow. When a journey
starts, the plan is copied for that entity, so editing a flow never mutates
journeys already in flight.

The point of the split is time. A single call lasts minutes; a real outreach
sequence spans days. Journeys wait between steps - a fixed delay or smart
timing - branch on the [outcome](https://docs.unpod.ai/context/outcomes.md) of each step, and pause
for a human to approve the next move. When the person replies on any channel,
the inbound reply reaches the running journey as a signal and stops or branches
it. Your agent never calls someone who already answered yesterday's email.

> [!NOTE]
>
> Journey flows are campaign step sequences, a different concept from
> SuperDialog's conversation-graph flows, which drive turns inside a single
> conversation. See [SuperDialog](https://docs.unpod.ai/superdialog/introduction.md) for that engine.

## The primitives

| Primitive | What it is | Where it lives today |
| - | - | - |
| Flows | The versioned step sequence - the plan | In build (journey engine) |
| Steps | One unit in the sequence: a call, a message, a wait, a branch, an approval, an exit | Call steps run as tasks - [Make Call task](https://docs.unpod.ai/api/execution/task-make-call-overview.md) |
| Journeys | One entity's traversal of one flow, with the plan copied per entity | In build; step executions surface as [runs](https://docs.unpod.ai/api/execution/runs-overview.md) |
| Waits | The gap between steps - a fixed duration or smart timing | In build |
| Signals | External input a running journey reacts to: an inbound reply, a human approval, a cancel | In build |

Tasks are the unit of work inside Execution. A call step does not reimplement
calling - it dispatches a task to the
[Calling Engine](https://docs.unpod.ai/telephony/concepts/calling-engine.md) unchanged, the same
[Make Call task](https://docs.unpod.ai/api/execution/task-make-call-overview.md) you can dispatch
directly today. The journey adds the before and after: when to place the call,
and what its outcome means for the next step.

## On the spine

A journey is attached to one entity. It reads the entity's
[context](https://docs.unpod.ai/context/overview.md) when choosing a branch, dispatches
interactions through the Talk layer as tasks, and consumes the structured
[outcome](https://docs.unpod.ai/context/outcomes.md) each interaction produces to decide the next
step. Every journey transition - started, step completed, waiting, signaled,
exited - emits an [event](https://docs.unpod.ai/core-engine/events.md), so the rest of your system can
react without polling.

## What stays hidden

The workflow engine underneath - Temporal-style durable execution, timer
persistence, retry semantics, replay - is deliberately not exposed. You define
flows in terms of steps, waits, and signals; how a journey survives a restart
or holds a three-day timer is Unpod's problem, not a queue you operate.

## Status

**In build.** The journey engine - waits, outcome branching, and human
approval steps - is shipping in the open. Call steps are real today: dispatch
them as [tasks](https://docs.unpod.ai/api/execution/task-make-call-overview.md) and inspect
[runs](https://docs.unpod.ai/api/execution/runs-overview.md). Approval steps ship with the journey
engine alongside [Teams & Policies](https://docs.unpod.ai/context/teams-policies.md).

## Go deeper

> [card] [Outcomes](https://docs.unpod.ai/context/outcomes.md)
>
> The structured results journeys branch on.

> [card] [Agent Workforce](https://docs.unpod.ai/agent-studio/agent-workforce.md)
>
> The workers that execute call and action steps.

> [card] [Events](https://docs.unpod.ai/core-engine/events.md)
>
> Every journey transition, emitted once.

> [card] [Make Call task](https://docs.unpod.ai/api/execution/task-make-call-overview.md)
>
> Dispatch a call as a task today.

> [card] [Runs API](https://docs.unpod.ai/api/execution/runs-overview.md)
>
> Inspect task executions.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.