Bright Data provides the world's #1 web data platform with Web Unlocker for bypassing anti-bot systems, SERP API for search engine data, and pre-made scrapers for popular websites. Collect any web data at scale.
Bright Data provides the world's #1 web data platform with Web Unlocker for bypassing anti-bot systems, SERP API for search engine data, and pre-made scrapers for popular websites. Collect any web data at scale. On Nagent, Bright Data is exposed as a fully-configurable ai web scraping integration that any agent can call — 10 actions, and API key authentication. No code is required to wire Bright Data into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Bright Data to automate the kinds of tasks ai web scraping teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire Bright Data into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against Bright Data, with input parameters and output schema. Drop these into any step of an agent built in Helix.
BRIGHTDATA_CRAWL_APITool to trigger an asynchronous site crawl job to extract content across multiple pages or entire domains. Returns a snapshot_id required by BRIGHTDATA_GET_SNAPSHOT_STATUS (poll until complete) and BRIGHTDATA_GET_SNAPSHOT_RESULTS (call only after completion; querying early yields empty or partial data). Use when you need to start a crawl for a given dataset and list of URLs. Large crawls can produce very large payloads — fetch results incrementally.
Input parameters
List of objects containing URLs or other parameters required by the crawler. Supports scope configuration fields such as depth limits, includePaths, and excludePaths to prevent over-crawling large sites, which increases cost and runtime.
Your dataset ID.
Whether to include an errors report with the results.
Pipe-separated list of output fields to include (e.g., 'url\\|about.updated_on').
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BRIGHTDATA_DATASET_LISTTool to list all available pre-made scrapers (datasets) from Bright Data's marketplace. Use when you need to browse available data sources for structured scraping.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BRIGHTDATA_FILTER_DATASETTool to apply custom filter criteria to a marketplace dataset (BETA). Use after selecting a dataset to generate a filtered snapshot.
Input parameters
Optional list of file paths to CSV or JSON files containing filter values.
Filter criteria object. Basic filter: {"name": "field_name", "operator": "=", "value": "search_term"}. Combine filters: {"operator": "and", "filters": \[{...}, {...}\]}. Supported operators: '=', '!=', '<', '<=', '>', '>=', 'in', 'not_in', 'includes', 'not_includes', 'array_includes', 'not_array_includes', 'is_null', 'is_not_null'. Max nesting depth: 3.
ID of the dataset to filter.
Optional maximum number of records to include in the snapshot, must be >= 1.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BRIGHTDATA_GET_LIST_OF_AVAILABLE_CITIESTool to get available static network cities for a given country. Use when you need to configure static proxy endpoints after selecting a country.
Input parameters
ISO 3166-1 alpha-2 country code to list available cities for.
Type of static proxy pool. 'dc' for datacenter, 'static_res' for residential.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BRIGHTDATA_GET_LIST_OF_AVAILABLE_COUNTRIESTool to list available countries and their ISO 3166-1 alpha-2 codes. Use when you need to configure zones with valid country codes before provisioning proxies.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BRIGHTDATA_GET_SNAPSHOT_RESULTSTool to retrieve the scraped data from a completed crawl job by snapshot ID. Only call after confirming the job is complete via BRIGHTDATA_GET_SNAPSHOT_STATUS — querying before completion yields empty or partial data. Use after triggering a crawl or filtering a dataset to download the collected data.
Input parameters
Which batch part to download (starts from 1). Use with 'batch_size' parameter.
Desired output format. Options: json, csv, ndjson (newline-delimited JSON), or jsonl (JSON Lines).
Whether to compress the result using gzip.
Divide snapshot into batches of this size (minimum 1000 records). Use with 'part' parameter. For large snapshots, always paginate using both `batch_size` and `part` together; skipping pagination can silently drop records or exceed response limits.
Identifier of the snapshot to fetch results for. This is the snapshot_id returned by the Trigger Site Crawl (CRAWL_API) action, typically in the format 's_xxxxxxxxxxxxx'. IDs expire after some time; stale or invalid IDs return empty or error responses.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BRIGHTDATA_GET_SNAPSHOT_STATUSTool to check the processing status of a crawl job using snapshot ID. Call before attempting to download results to ensure data collection is complete.
Input parameters
Identifier of the snapshot to check. This is the snapshot_id returned by the Trigger Site Crawl (CRAWL_API) action, typically in the format 's_xxxxxxxxxxxxx'.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BRIGHTDATA_LIST_WEB_UNLOCKER_ZONESTool to list your configured Web Unlocker zones and proxy endpoints. Use to view available zones for web scraping and bot protection bypass.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BRIGHTDATA_SERP_SEARCHTool to perform SERP (Search Engine Results Page) searches across different search engines using Bright Data's SERP Scrape API. Use when you need to retrieve search results, trending topics, or competitive analysis data. This action submits an asynchronous request and returns a response ID for tracking.
Input parameters
Zone identifier for your SERP API product configuration. This is a required parameter that must be obtained from your Bright Data dashboard under 'Proxies & Scraping Infrastructure'. Each user has their own unique zone name.
Response format. 'json' returns structured data, 'raw' returns HTML string.
HTTP method for the request.
Two-letter ISO country code for proxy location and localized search results.
The search query keywords to execute.
Additional data transformation. 'markdown' converts HTML to clean markdown, 'screenshot' captures a PNG image.
Search engine to use for the query. Supported values: google, bing, yahoo, duckduckgo, yandex.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BRIGHTDATA_WEB_UNLOCKERTool to bypass bot detection, captcha, and other anti-scraping measures to extract content from websites. Use when you need to scrape websites that block automated access or require JavaScript rendering. Some responses may still contain CAPTCHA challenge pages or incomplete HTML; inspect the response before retrying, and avoid aggressive retry loops.
Input parameters
The URL of the website to unlock and scrape.
Web Unlocker zone name (required, non-empty). Call BRIGHTDATA_LIST_WEB_UNLOCKER_ZONES first to get available zones.
Response format - 'raw' returns HTML content as string, 'json' returns structured data.
ISO 3166-1 alpha-2 country code for the proxy location (e.g., 'us', 'gb', 'de').
Set to 'markdown' to convert page content to markdown format.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 34 agents privately built on Nagent that already use Bright Data.
Build on Nagent
Connect Bright Data to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find Bright Data, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Bright Data is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Bright Data is connected, you configure its 10 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Bright Data steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a Bright Data event fires, the agent kicks off automatically.
Every Bright Data action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While Bright Data ships with 10 pre-built ai web scraping actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Bright Data together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Bright Data-based workflows tailored to your business.