The Set Location block allows you to configure the perceived geographical location and timezone of the AI agent’s browser. This is essential for interacting with websites that display different content, prices, or languages based on the visitor’s region, or for accessing content that is restricted to specific countries.

​
Purpose

Use the Set Location block to:
  • Access content that is only available in certain countries (geo-restricted content).
  • View the localized version of a website (e.g., see prices in a specific currency or content in a local language).
  • Ensure that search results or other operations are relevant to a specific geographic area.

​
Placement Rules

This block’s placement is critical. It must be executed before a browser session is initialized. There are two primary ways to use it:
  1. At the Start of a Workflow: Placing Set Location at the very beginning of a workflow (right after the “start” node) sets a global location for all subsequent browser sessions within that run.
  2. Before a New Session: In a multi-level workflow, you can place a Set Location block at the beginning of a specific row, right before a block like Open Websites. This allows you to have different parallel sessions running with different locations.

​
Configuration

The block offers two dropdown menus to configure the agent’s location.
  • Location: This dropdown allows you to select a country or a broad region (e.g., United States, Mexico, Europe). The default setting is Automatic, which uses the agent’s default server location.
  • Timezone (optional): This dropdown allows for more granular control by letting you select a specific timezone (e.g., America/Chicago (UTC-6), Europe/London (UTC+0)). This is useful if a website’s behavior depends on the user’s specific timezone in addition to their country.
Set Location block UI

The Set Location block configuration panel.

​
How It Works

When the Set Location block is executed, it modifies the browser-level settings for the AI agent’s subsequent session. When the agent then visits a website, it reports the specified location and timezone, causing the website to serve content as if the visit were originating from that region.

​
Example Scenario: Comparing International Pricing

Imagine you want to check the price of a flight on an airline’s website from two different locations.
  1. Create a Multi-Level Workflow: Use the Layout menu to create two parallel rows.
  2. Row 1 (US Location):
    • Start with a Set Location block and select United States.
    • Add an Open Websites block with the airline’s URL.
    • Add an Extract Data block to scrape the price_usd.
  3. Row 2 (European Location):
    • Start with a Set Location block and select Europe.
    • Add an Open Websites block with the same airline’s URL.
    • Add an Extract Data block to scrape the price_eur.
  4. Merge Results: Use a final Merge data block to combine the results into a single output.
  • Result: You get a structured comparison of prices as they appear to visitors from two different parts of the world.

​
Key Considerations

  • Browser-Level Setting: This block changes settings within the browser. It is not a VPN. Websites with highly sophisticated IP-based geo-blocking may still be able to determine the agent’s server origin.
  • Affects Subsequent Actions: The location is set for the entire browser session that follows the block. All Open Websites, Search on Google, and other browser-based actions will use this location until the session ends or a new one begins.