For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Dashboard
User GuideDeveloper GuidesAPI Reference
User GuideDeveloper GuidesAPI Reference
  • Getting Started
    • What is Runtype?
    • Creating your account
    • Platform Keys vs. BYOK
    • Understanding the Runtype UI
    • Quickstart: Social Media Post Generator
    • Quickstart: From Agent to Chat Widget
  • Dashboard
    • What is the Dashboard?
    • Daily Executions
  • Playground
    • What is the Playground?
  • Products & Surfaces
    • What are Products?
    • What are Surfaces?
    • Creating a Product
    • Setting up a Chat Surface
    • Setting up an API Surface
    • Setting up an MCP Surface
    • Setting up an A2A Surface
    • Setting up a Slack Surface
  • Flows
    • What are Flows?
    • Creating and Editing Flows
    • Flow step types overview
    • Agent and Flow Templates
  • Agents
    • What are Agents?
    • Creating and configuring Agents
    • Agent tools
  • Records
    • What are Records?
    • Creating and managing records
  • Tools
    • What are Tools?
    • Built-in Tools
    • Creating custom tools
    • Creating external tools
  • Evals
    • What are Evals?
    • Running an Eval
  • Schedules
    • What are Schedules?
  • Logs
    • What are Logs?
  • Integrations
    • Connecting AI model providers
  • Settings
    • What's in Settings?
    • Available AI models
  • Troubleshooting & FAQ
    • FAQ
    • Rate Limits and Usage
    • Managing Runtype with Claude
Dashboard
LogoLogo
On this page
  • Create a Flow
  • Add steps
  • How steps work together
  • Reorder steps
  • Enable or disable steps
  • Edit a step
  • Delete a step
  • Test your Flow
  • Save and publish
  • Generate a Flow with AI
  • Error handling
  • Environment selector
  • Next steps
Flows

Creating and Editing Flows

Was this page helpful?
Previous

Flow step types overview

Next
Built with

Build AI-powered workflows by creating Flows that process data, call AI models, and take actions automatically. If you are new to the feature, start with What are Flows? for a quick overview.

Create a Flow

  1. In the sidebar, click Flows.
  2. Click Create Flow.
  3. In the Create New Flow panel, choose one of the available creation options.
  4. The Flow editor opens. Click the Flow name at the top to rename it.

You can also create a Flow from a Product when adding a Capability. It opens the same editor.

Add steps

Steps are the building blocks of your Flow. Each step performs a specific action, such as calling an AI model, fetching data, making API requests, or running code. For a broader map of what is available, see Flow step types overview.

  1. Click the + button between steps, or at the top for your first step.
  2. Browse or search step types in the dialog that appears.
  3. Configure the step in the step card that appears.

Use the search bar in the Add Step dialog to quickly find the step type you need. If your search narrows to a single result, press Enter to add it.

How steps work together

Steps execute sequentially from top to bottom. To pass data between steps, reference an earlier step’s output variable with double curly braces, such as {{summary_result}} or {{ticket_analysis.category}}.

System and Record variables like {{_record.metadata.field}} are also available.

Reorder steps

Drag steps in the left sidebar to change execution order. The Flow runs from top to bottom in the order shown.

Enable or disable steps

Use the enable or disable button in the sidebar to turn individual steps on or off. Disabled steps are skipped during execution, which is useful for testing or temporarily removing a step without deleting it.

Edit a step

Click any step in the sidebar or the main editor to select it, then update its configuration in the step card. Click Save in the toolbar when you’re done.

Delete a step

Click the trash icon on a step in the sidebar to remove it. If other steps reference the deleted step’s output variable, update those references.

Test your Flow

  1. Click the Run button in the toolbar.
  2. The Run Flow sheet opens with several tabs.
  3. Enter your test input and run the Flow.

Results show step-by-step execution details, including input, output, and timing for each step. Click any step in the results to see its full details.

You can test a Flow before saving it. The editor uses your current unsaved steps, which is helpful for rapid iteration.

Save and publish

The toolbar shows Create for new Flows or Save for existing ones. Save your work frequently as you build.

To make a Flow the live version used by your Products:

  1. Click the chevron next to Save to open the dropdown.
  2. Click Publish, or Save & Publish if you have unsaved changes.

From the same dropdown, you can also view past versions or open Conversations for Flows with Agent steps.

Published versions are locked. Any further edits create a new draft automatically.

Generate a Flow with AI

Click the Generate button in the toolbar to have AI help you create or modify your Flow’s steps. Describe what you want your Flow to do, and Runtype generates the steps for you.

Error handling

Each step has configurable error handling. Click the error handling icon on a step card to choose what happens if that step fails.

  • Continue on error skips the failed step and continues running the rest of the Flow.
  • Stop on error halts the entire Flow immediately.
  • Use fallbacks tries alternative approaches before giving up, such as retrying with a different model or calling a different Flow.

Fallbacks are especially useful for AI steps. You can set a backup model so your Flow keeps running if a specific model is unavailable.

Environment selector

The footer of the Flow editor includes an environment selector where you can switch between Development and Production. Use Development while building and testing, then switch to Production when your Flow is ready for real usage.

Next steps

  • Flow step types overview to learn which steps you can add.
  • Quickstart: From Flow to Live Surface to deploy a Flow in a Product.