Skip to main content
New to building conversational flows? Check out our Pipecat Flows guide first.
Pipecat Flows is an add-on framework for Pipecat that allows you to build structured conversations in your AI applications. It enables you to define conversation paths while handling the complexities of state management and LLM interactions.

Installation

Pipecat Flows

To use Pipecat Flows, install the required dependency:
pip install pipecat-ai-flows

Pipecat Dependencies

For fresh installations, you’ll need to install Pipecat with depdencies for your Transport, STT, LLM, and TTS providers. For example, to use Daily, OpenAI, Deepgram, Cartesia, and Silero:
pip install "pipecat-ai[daily,openai,deepgram,cartesia,silero]"

Reference Pages

Function Types

Node Functions

Execute operations within a single conversation state without switching nodes. Return (FlowResult, None).

Edge Functions

Create transitions between conversation states, optionally processing data first. Return (FlowResult, NodeConfig).

Direct Functions

Functions passed directly to NodeConfig with automatic metadata extraction from signatures and docstrings. See flows_direct_function and FlowsDirectFunction.

LLM Provider Support

Pipecat Flows automatically handles format differences between providers:
ProviderFormat SupportInstallation
OpenAIFunction callingpip install "pipecat-ai[openai]"
OpenAI-compatibleFunction callingProvider-specific (see below)
AnthropicNative toolspip install "pipecat-ai[anthropic]"
Google GeminiFunction declarationspip install "pipecat-ai[google]"
AWS BedrockAnthropic-compatiblepip install "pipecat-ai[aws]"
Any LLM service that extends OpenAILLMService is automatically supported. This includes services like Groq, Together, Cerebras, DeepSeek, and others that use the OpenAI-compatible API format.

Additional Notes

  • State Management: Use flow_manager.state dictionary for persistent conversation data
  • Automatic Function Call Registration and Validation: All functions are automatically registered and validated at run-time
  • Provider Compatibility: Format differences handled automatically via adapter system