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
    • MCP authentication
    • Authenticating with product API keys
    • Embedding the chat widget (script tag)
    • Embedding the chat widget (React)
    • Surface orchestration modes
    • Product views
    • Adding Capabilities to a product
    • Connecting external agents
    • How A2A works
    • Connecting to Cursor / VS Code
    • Connecting to Claude Desktop
    • Scoping API keys to capabilities
    • Auto-generated OpenAPI spec
    • Calling your API endpoints
    • Client tokens and domain restrictions
    • AI-powered theme generation
    • Widget theming and customization
    • Product versioning and status
  • Flows
    • What are Flows?
    • Creating and Editing Flows
    • Flow step types overview
    • Agent and Flow Templates
    • Using prompt steps
    • Using transform-data steps
    • Using conditional steps
    • Using fetch-url and api-call steps
    • Using record steps (upsert/retrieve)
    • Flow variables and templates
    • Flow versioning and publishing
    • Running flows in batch
    • Handling batch failures
    • Debugging flows
  • Agents
    • What are Agents?
    • Creating and configuring Agents
    • Agent tools
  • Records
    • What are Records?
    • Creating and managing records
    • Using records in flows
    • Filtering and searching records
  • Tools
    • What are Tools?
    • Built-in Tools
    • Creating custom tools
    • Creating external tools
    • Runtime tools
  • Evals
    • What are Evals?
    • Running an Eval
    • Interpreting eval results
  • Schedules
    • What are Schedules?
    • Automating batch processing
  • Logs
    • What are Logs?
    • Working with Logs
  • Integrations
    • Connecting AI model providers
    • Slack integration
    • Google Workspace integration
    • GitHub integration
    • Linear integration
    • Weaviate (vector search)
    • Firecrawl (web scraping)
    • Exa (web search)
  • Settings
    • What's in Settings?
    • Available AI models
    • What are Organizations?
    • Managing AI models
    • Managing API keys
    • Billing and plans
    • Usage data
    • Team members and permissions
    • Appearance and preferences
    • Integrations (PostHog, Weaviate, Daytona)
  • Troubleshooting & FAQ
    • FAQ
    • Rate Limits and Usage
    • Managing Runtype with Claude
    • Flow execution failures
    • Common errors and solutions
    • Authentication issues
Dashboard
LogoLogo
On this page
  • Add a prompt step
  • Writing prompts
  • Using template variables
  • Model selection
  • Parameters
  • Temperature
  • Max tokens
  • System prompt
  • Accessing output
  • Error handling
  • Best practices
  • Next steps
Flows

Using prompt steps

Was this page helpful?
Previous

Using transform-data steps

Next
Built with

Prompt steps call AI models to generate text, analyze data, or answer questions. They’re the core building block of AI workflows.

Add a prompt step

  1. In the Flow editor, click Add Step
  2. Select Prompt
  3. Configure:
    • Name: Descriptive label (e.g., “Generate summary”)
    • Model: Select an AI model
    • Prompt: Write your prompt text
  4. Click Save Step

Writing prompts

Use natural language to instruct the AI. Be specific about what you want:

Weak:

Summarize this.

Better:

Summarize the following customer email in 2-3 sentences.
Focus on the main request and any urgency indicators.
Email: {{email_text}}

Using template variables

Reference Flow inputs and previous step outputs with {{variable}} syntax:

You are a customer support Agent for {{company}}.
Customer message: {{customer_message}}
Customer tier: {{customer_data.tier}}
Previous interactions: {{customer_data.interaction_count}}
Provide a helpful, professional response.

Variable names come from the inputs field when triggering the Flow or from the outputVariable field of previous steps.

Model selection

Different models have different strengths. Use the routed model format (e.g., claude-sonnet-4-6, gpt-5-mini, gemini-3-flash) so your Flows stay current as models are updated. Choose based on task complexity, speed requirements, and cost.

Parameters

Fine-tune model behavior:

Temperature

Controls randomness (0-2):

  • 0-0.3: Deterministic, consistent (good for classification, extraction)
  • 0.7: Balanced (default for most tasks)
  • 0.9-1.0: Creative, varied (good for content generation)
  • 1.0-2.0: Highly creative (use with caution, can produce less coherent output)

Max tokens

Limits response length. Set conservatively to control costs.

System prompt

Optional instructions that set the AI’s behavior for the entire conversation. Use for role definition or global rules.

Test prompts in the Playground before adding to Flows. This lets you iterate quickly without running the entire Flow each time.

Accessing output

Each prompt step has an outputVariable in its configuration. Reference that variable in later steps:

{{summary_result}}

If the prompt returns JSON (responseFormat: json), access specific properties with dot notation:

{{extract_data.customerName}}
{{extract_data.orderAmount}}

The variable name comes from the step’s outputVariable field, not the step name.

Error handling

Prompt steps can fail if:

  • API quota exceeded
  • Model rate limits hit
  • Invalid API keys
  • Prompt too long for model context

Configure retry behavior in Flow settings or add conditional steps to handle errors.

Best practices

  • Be specific: Clear instructions produce better results
  • Provide examples: Show the AI what you want with examples
  • Structure output: Ask for JSON or specific formats when needed
  • Keep context concise: Don’t include unnecessary information in prompts
  • Test variations: Use Evals to compare different prompts and models

Next steps

  • Flow variables and templates for advanced variable usage
  • Using transform-data steps to process AI outputs
  • Running an Eval to test prompt variations