Overview

Retrieves the results from a previously initiated browser operator session, including any data extracted, screenshots captured, and summaries generated.

Use Cases

  • Data Collection: Obtain structured data collected from web sources.
  • Research Compilation: Gather the results of automated web research tasks.
  • Process Verification: Review screenshots and logs from automated web processes.
  • Content Aggregation: Collect and process information from multiple web sources.

Configuration Fields

Browser Operator Session

  • Description: The browser operator session details obtained from the ‘Start Browser Operator’ action.
  • Example: "" (typically passed directly from the output of the Start Browser Operator action)
  • Required: Yes

Output Variable Name

  • Description: Assign a variable name to store the comprehensive results from the browser operator session.
  • Example: “browser_operator_results” or “research_findings”
  • Validation: Only letters, numbers, and underscores (_) are allowed in variable names.
  • Required: Yes

Result Contents

The browser operator results typically include:

  1. Results: A textual summary of the findings or actions taken
  2. GIF: Animated capture of the entire browser session
  3. Execution Time: Total duration of the session in milliseconds
  4. Thoughts: Step-by-step reasoning trail showing how the operator navigated and made decisions, including:
    • Evaluation of previous goals
    • Memory (what the operator remembers)
    • Next goals
    • Page summaries
  5. Session Details: IDs, URLs, and other metadata about the session

How It Works

This action:

  1. Checks the status of the specified browser operator session
  2. If completed, collects all results and formats them for use in subsequent workflow steps
  3. If still in progress, can optionally wait for completion or return interim results

Beta Feature

This action is currently in beta. While fully functional, it may undergo changes based on user feedback.

Usage Notes

  • For complex tasks, the browser operator may take several minutes to complete
  • Results can be used directly in downstream workflow actions
  • Screenshots are stored securely and accessible via URLs in the results
  • Extracted data structure will vary based on the nature of the original prompt