Skip to main content
Transitions define how your workflow moves from one node to the next. They represent the routing logic of your automation and determine which path the agent follows under different conditions. Asteroid provides three types of transitions, each designed for a different kind of decision-making.

AI Transition

Chosen by AI based on the agent’s analysis of the page and task context

Selector Transition

Jumps to the next node the moment a specific element appears

Outcome Success

Used by nodes that deterministically signal successful completion

​
Types of Transitions

​
AI Transitions

AI Transitions are the most flexible and expressive transition type. They allow AI nodes to choose the next step based on reasoning, context, and analysis of the current browser state. When to use:
  • When the next step depends on page content or semantic understanding
  • When multiple paths are possible and the AI must choose intelligently
  • For workflows requiring reasoning, interpretation, or decisions based on extracted information
Example:

​
Selector Transitions

Selector Transitions are deterministic. They activate immediately when a specific selector becomes visible or present on the page. When to use:
  • When waiting for a specific UI element to appear
  • As a guardrail for navigation changes or modal detection
  • For flows that require deterministic, event-driven branching
Use carefully: Selector transitions should be used sparingly, only when you are 100% certain about the structure and stability of the target element. Example selector: 
button:has-text("Submit")

​
Outcome Success Transitions

Outcome Success transitions are used after deterministic nodes, such as Playwright or API nodes, that explicitly return either a success or failure. When to use:
  • For successful API responses (200–299)
  • When Playwright scripts complete without errors
  • Any deterministic node that returns a clear “success” state
Critical: URL and Playwright Node RequirementsURL and Playwright nodes can ONLY use Outcome Success transitions. These nodes must be connected to the next node using an Outcome Success transition type. No other transition types are valid for these nodes.
  • If a URL or Playwright node doesn’t have an Outcome Success transition, it won’t work properly
  • These nodes cannot use AI Transitions or Selector Transitions
  • Always ensure URL and Playwright nodes have at least one Outcome Success transition connecting them to the next step in your workflow

​
Best Practices

​
Choosing the Right Transition

Use the appropriate transition type for each decision point:
  • AI Transitions: For dynamic routing based on page content, extracted information, or reasoning.
  • Selector Transitions: For immediate, deterministic reactions to UI events. Use cautiously, only when element type, structure, and behavior are known and stable.
  • Outcome Success Transitions: For deterministic steps with clearly defined success states (API calls, Playwright scripts).

​
Failure Transitions

Critical: AI Task Node Failure PathsAll AI Task nodes must have a connection to an Output node via a failure path. This is essential for proper error handling and workflow completion.
  • Every AI Task node should have at least one transition (typically an AI Transition) that connects to an Output node configured for failure scenarios
  • Without a failure path, your workflow may not properly handle errors, unexpected conditions, or edge cases
  • This ensures that unexpected conditions, missing elements, or interpretation errors are surfaced correctly in your workflow