Skip to main content

Flow Editor

The Flow Editor provides a comprehensive interface for building and modifying flows. This guide covers the editor's features and how to construct effective flows.

Opening the Editor​

Access the Flow Editor by:

  • Creating a new flow (click New on the Flows page)
  • Editing an existing flow (click Edit on a flow's detail page)
  • Opening a draft generated from Chat

Editor Layout​

The editor has several views accessible via tabs:

TabPurpose
Container ViewPrimary editing interface with drag-drop organization
Graph ViewVisual flow diagram showing step relationships
VariablesConfigure input and output variables
Test RunValidate the flow with sample data

Container View​

The Container View is the main editing interface, organized into sections:

Flow Metadata​

At the top, configure basic information:

  • Title — Descriptive name for the flow
  • Description — What this flow does and when to use it
  • Symptoms — Observable conditions that trigger this flow

Triage Section​

Triage steps investigate the incident to identify the root cause.

Adding a Triage Step:

  1. Click Add Triage Step
  2. Enter a description (the diagnostic question or action)
  3. Configure the automation type:
    • Automated — Executed by a tool
    • Manual — Requires human input
    • Semi-automated — Tool-assisted with human confirmation
  4. For automated steps, configure tool invocation

Configuring Tool Invocation:

  1. Select a tool from available integrations
  2. Provide instructions for the AI
  3. Specify required context
  4. Define expected output handling

Root Causes​

Root causes represent the problems this flow can diagnose.

Adding a Root Cause:

  1. Click Add Root Cause
  2. Enter a descriptive name
  3. Add any relevant details

Root causes are linked to triage outcomes and remediation steps.

Outcomes​

Outcomes connect triage results to root causes.

Adding an Outcome:

  1. Click Add Outcome
  2. Describe the outcome condition
  3. Map to one or more root causes
  4. Specify which remediation path to follow

Remediation Section​

Remediation steps resolve the identified root cause.

Adding a Remediation Step:

  1. Click Add Remediation Step
  2. Enter a description (the resolution action)
  3. Configure automation type
  4. For automated steps, configure tool invocation
  5. Link to applicable root causes

Graph View​

The Graph View provides visual representation of the flow structure:

  • Flow Logic View — Shows step sequence and branching
  • Context Flow View — Shows data dependencies between steps

Use Graph View to:

  • Understand the overall flow structure
  • Identify missing connections
  • Visualize complex branching logic

Variables Tab​

Variables allow data to pass into, through, and out of the flow.

Input Variables​

Input variables are provided when the flow starts.

Adding an Input Variable:

  1. Click Add Input Variable
  2. Enter a name (used to reference the variable)
  3. Select a type (text, number, boolean, etc.)
  4. Mark as required or optional
  5. Add a description and default value if applicable

Output Variables​

Output variables capture results for use after the flow completes.

Adding an Output Variable:

  1. Click Add Output Variable
  2. Enter a name
  3. Select a type
  4. Specify which step produces this output

Using Variables in Steps​

Reference variables in step configurations using the variable name. The editor provides autocomplete for available variables.

Variables can pass data between steps:

  • Triage step output → Remediation step input
  • Input variable → Any step
  • Any step → Output variable

Test Run Tab​

Validate your flow before publishing using Test Run.

Running a Test​

  1. Go to the Test Run tab
  2. Provide values for required input variables
  3. Click Start Test
  4. Watch execution progress
  5. Review results

Test Mode Behavior​

In test mode:

  • Tools execute normally (be cautious with destructive actions)
  • Results are recorded but not counted in flow metrics
  • You can step through manually or let it run automatically

Debugging​

If a test fails:

  • Review the step that failed
  • Check tool execution logs
  • Verify variable values
  • Adjust step configuration and retest

Step Configuration Details​

Automation Types​

TypeBehavior
Fully AutomatedTool executes without user intervention
Semi-AutomatedTool executes with user confirmation
ManualUser performs the action and reports results
Information OnlyDisplays information, no action required

Tool Selection​

When configuring automated steps:

  1. Select Tool — Choose from available tools in your outposts
  2. Instructions — Tell the AI how to use the tool
  3. Context Requirements — Specify what information the tool needs
  4. Output Handling — Define how to interpret results

Manual Step Modes​

Manual steps can be configured for different interaction styles:

  • Question — Ask the user a question, expect an answer
  • Confirmation — Ask the user to confirm before proceeding
  • Action — Instruct the user to perform an action and report completion
  • Information — Display information to the user

Best Practices​

Start Simple

Begin with a minimal flow and add complexity incrementally. A working simple flow is better than a broken complex one.

Use Clear Descriptions

Write step descriptions that make sense to someone unfamiliar with the flow. Future users (including future you) will thank you.

Test Thoroughly

Run multiple test scenarios, including edge cases and failure modes.

Use Variables for Flexibility

Instead of hardcoding values, use variables. This makes flows reusable across different contexts.

Document Root Causes

Clear root cause descriptions help users understand what was found and why specific remediation was chosen.

  • Flows — Flow concepts and lifecycle
  • Runs — Monitor flow executions
  • Chat — Generate flows from conversation