Platforms

A platform represents a website or web application your automations interact with. Platforms are defined at the workspace level and shared across agents and tasks.

Creating a platform

Open Platforms in your workspace sidebar and click New platform.

Handler naming

Handlers are the bridge between your task scripts and configured platforms. Rules:

• Use lowercase letters, numbers, and underscores
• Must be unique within the workspace
• Referenced directly in DSL — no declaration needed in scripts

Example: a platform with handler customer_portal is used as:

flow {
  in customer_portal {
    click { css "#submit" }
  }
}

Platform linkage in tasks

When you create a task, link it to the platforms it uses. This:

• Validates that referenced handlers exist
• Shows which sites a task touches in the UI
• Helps the runtime prepare the correct browser context

A single task can span multiple platforms:

flow {
  in login_portal {
    // authenticate
  }
  in crm {
    // extract data
  }
}

Platforms vs. agent configuration

Platforms define what sites exist. Agent-platform bindings define how an agent accesses them — credentials, captcha settings, and concurrency limits. See Agents and Credentials.

Best practices

• Use descriptive handler names that match the site's purpose (billing_portal, vendor_login) rather than generic names (site1).
• Set the URL to the page agents should land on first — usually a login or dashboard page.
• Keep metadata for team notes or external system IDs your integrations need to correlate.