Concepts

Nodes

Nodes are the building blocks of every flow. Each node has a specific role and configurable properties.

Node categories

Category	Purpose	Examples
Agent	Handle conversation segments	Main Agent, Agent
Provider	Supply AI services to the flow	LLM, TTS, STT
Action	Execute side effects during a call	End Call

Publishing a flow requires, among other checks: one Main Agent node (the initial node), one LLM provider, one TTS provider, one STT provider, a role message and task message on every agent, unique agent and function names, and transition targets that exist. See Testing & Publishing for the full list.

Edges

Edges are the connections between nodes. They define how data and conversation flow through the graph.

Agent → Agent: Transition edges. The conversation transfers from one agent to another when a defined condition is met.
Provider → Agent: Service edges. Connect an LLM, TTS, or STT provider to the agents that use it.
Agent → Action: Trigger edges. Actions fire during or after an agent's conversation turn.

Draw an edge by dragging from a node's output handle to another node's input handle.

You don't have to start from an empty canvas — the Assistant can build a complete draft flow from a description, or propose edits to the flow you have open.

Flow lifecycle

Every flow moves through a defined set of states:

DRAFT ⇄ TESTING → PUBLISHED → ARCHIVED
  ↑                               |
  +-------------------------------+
  
DRAFT → PUBLISHED (direct publish, skipping test)

State	Editable	Callable	Assignable to numbers
DRAFT	Yes	No	No
TESTING	Yes	Test calls only	No
PUBLISHED	No	Yes	Yes
ARCHIVED	No	No	No

State transitions

Transition	Description
Draft → Testing	Enable test calls on this flow
Draft → Published	Publish directly, skipping the testing phase
Testing → Draft	Revert to draft for further editing
Testing → Published	Validation runs. If it passes, the flow is published as an immutable snapshot
Published → Archived	Retire the flow. Removes it from active use and unassigns all phone numbers
Archived → Draft	Reactivate the flow for editing

A published flow cannot be edited. To make changes, create a new version from the published flow — this starts a new draft with the same configuration.

Versioning

Each time you publish a flow, Talkif creates a new version. Previous versions are preserved and accessible in the version history.

Published versions are immutable — they cannot be modified
You can view any previous version's configuration
Creating a new version from a published flow copies all nodes, edges, and configuration into a new draft
Phone numbers follow the latest published version by default — publishing a new version immediately serves calls to connected phones
Phones can be pinned to a specific version. When the pinned version is republished, pinned phones auto-bump to the new version in the same transaction