Skip to main content
Suites are collections of related flows that help you organize your flows and run them together efficiently. Think of suites as folders that group flows by feature, user journey, or any other logical grouping.

​
What is a Suite?

A Suite is a container that groups multiple flows together. Suites provide:
  • Organization: Keep related flows together (e.g., “Login Flows”, “Checkout Flows”)
  • Batch Execution: Run all flows in a suite with one click
  • Shared Authentication: Set up authentication once for all flows in the suite

​
Creating a Suite

​
Step 1: Click “Create Suite”

Navigate to the Flows page and click the folder+ icon or Create Suite button.

​
Step 2: Enter Suite Details

Required:
  • Name: A descriptive name for your suite (e.g., “Authentication Flows”)
Optional:
  • Description: Additional context about what this suite tests
  • Suite Context: Extra context the AI agent should keep in mind for every flow in the suite
  • Auth Instructions: Shared authentication that runs once before all flows
  • Run flows in parallel: Give each flow its own session and run them concurrently

​
Step 3: Save

Click Create Suite to save. Your new suite appears in the Flows page.

​
Suite Context

Suite Context is plain-English background that’s injected into the AI agent’s prompt for every flow in the suite — alongside any app-level context. Use it for product knowledge, conventions, or constraints that apply to the entire suite (e.g., “this suite tests the membership signup journey only — ignore marketing banners and cookie prompts”). Unlike Auth Instructions, Suite Context isn’t executed as a flow. It just gives the agent shared situational awareness so each flow doesn’t have to repeat the same background. Example Suite Context:
Use Suite Context for background the agent needs (“this app”, “this area”), and Auth Instructions for actions the agent must take before every flow (“log in as X”).

​
Auth Instructions (Setup Flow)

Auth Instructions are special setup instructions that run once at the beginning of the suite, before any flows execute. This is perfect for:
  • Logging in with test credentials
  • Accepting permissions or completing onboarding steps
  • Navigating to a specific section of the app
Example Auth Instructions:

​
Benefits of Auth Instructions

  • Write once, use many times: All flows in the suite start from an authenticated state
  • Faster execution: Authentication happens only once, not before every flow
  • Easier maintenance: Update login credentials in one place

​
Suite Variables

Suite variables let you override environment variables for all flows in the suite. They take precedence over environment-level values, so you can customize configuration per suite without changing your environment settings. How to set them:
  1. Edit your suite
  2. Expand the Advanced dropdown
  3. Add key-value pairs (e.g., TEST_EMAIL = suite-user@example.com)
Flow-level variables can further override suite variables for individual flows. See Variables for the full precedence hierarchy.

​
Running Flows in Parallel

Expand Advanced while creating or editing a dashboard-managed suite, then enable Run flows in parallel. Each flow runs in its own device or browser session. Auth Instructions and suite setup/teardown hooks run independently in each session. Parallel mode is useful when flows do not depend on state or variables produced by earlier flows. Leave it off when flows must share a session or execute in order.
As you scale parallel testing, give each session its own account or isolated data to avoid conflicts. See Making Suites, Parallelizable, Isolated, and Repeatable for guidance.
API clients can optionally send parallelize_flows when launching a suite to override its saved setting for that request. Explicit true or false takes precedence; when the field is omitted or null, Autosana uses the suite’s saved Run flows in parallel setting.

​
Adding Flows to a Suite

​
Method 1: Create Flow in Suite

  1. Expand your suite in the Flows page
  2. Click Create Flow inside the suite
  3. Write your flow instructions
  4. The flow is automatically added to the suite

​
Method 2: Add Existing Flows

  1. Expand your suite
  2. Click Add Existing Flows
  3. Check the flows you want to include
  4. Click Add Flows

​
Method 3: Attach from Flow

  1. Click the three dots (⋯) next to any flow
  2. Select Attach to Suite
  3. Check the suites you want to add the flow to
  4. Click Save

​
Managing Suite Contents

​
Reordering Flows

Change the order flows run in:
  1. Expand your suite
  2. Drag and drop flows using the handle icon (⋮⋮)
  3. Release to set the new order
Flows execute in the order they appear in the suite.

​
Removing Flows from Suite

  1. Expand the suite
  2. Click the three dots (⋯) next to the flow
  3. Select Remove from Suite
Removing a flow from a suite doesn’t delete the flow—it just removes the relationship. The flow remains in your Flows list.

​
Deleting a Suite

To delete a suite:
  1. Find the suite in the Flows page
  2. Click the trash icon on the suite card
  3. Confirm deletion in the dialog
Deleting a suite does not delete the flows inside it. All flows are preserved and remain available in your workspace. Flows that belong to other suites stay attached to those suites.

​
Running a Suite

​
Running All Flows

  1. Find your suite in the Flows page
  2. Click Run Suite
  3. Select your app
  4. Choose target device (iPhone/iPad for iOS)
  5. Click Run Suite
The suite executes as follows:
  1. Auth Instructions run first (if configured)
  2. Each flow runs, starting from an authenticated state
With Run flows in parallel enabled, each flow gets an independent session and its own Auth Instructions and hooks. On the Runs page, those sessions appear together in the same batch while remaining separate runs.

​
Sharing Data Between Flows

When flows run sequentially in a suite, runtime variables from one flow automatically carry forward to the next. This includes values exported by hooks, variables set by the agent, and any per-flow or per-suite variable overrides. Parallel flows use independent sessions and cannot share runtime state with sibling flows. Use the ${env:KEY} syntax in later flow instructions to reference values from earlier flows.
${env:KEY} can only reference values that existed before the agent began running — it cannot reference values saved by the agent or exported by mid-flow hooks during execution. For those, use Get Variable instead.
Flow 1:
Flow 2 (runs after Flow 1):
Hooks in later flows also have access to these variables via standard environment variable access (e.g., os.environ.get("order_number") in Python).
See Variables for more details and examples of cross-flow data sharing.

​
Best Practices

Set Up Auth InstructionsIf your flows require authentication, use Auth Instructions instead of repeating login steps in every flow.
On the flow run viewer: Shift+arrow switches flows in a suite; Shift+Ctrl+arrow (Mac: Shift+⌘+arrow) switches suite runs.

​
Next Steps