The Bright Data Partner connector is developed and maintained by Bright Data. Customer support is handled through the Boomi Support Portal, where tickets are triaged to Bright Data.
Supported objects
The connector supports the following object types, each accessed via the Execute action:| Object | Description |
|---|---|
| Dataset | Access marketplace datasets with filtering and snapshot retrieval |
| Scraper | Submit web scraping jobs and retrieve results asynchronously |
| Unlocker | Access protected web content via proxy and unblocking services |
| SERP | Retrieve search engine results pages from Google, Bing, and others |
Prerequisites
Before you begin, ensure you have:- A valid Bright Data account
- An API token generated from the Bright Data Control Panel with permissions for the services you intend to use
Connect your Bright Data account
Open the Connection configuration
In your Boomi process, add a new Bright Data Partner connector component and navigate to the Connection tab.
Set the Base URL
Enter the Bright Data API base URL:Customize this value only if you need to point to a different endpoint, such as for testing or regional deployments.
Enter your API Token
Paste your Bright Data API token into the API Token field. The connector uses this token for Bearer authentication.
Configure an operation
Each operation defines how the connector interacts with a specific Bright Data object. Create a separate operation component for each action/object combination your integration requires. All object types use the Execute action.Options tab fields
| Field | Description |
|---|---|
| Connector action | Set to Execute for all Bright Data operations |
| Object | Import using the Import button. Choose Dataset, Scraper, Unlocker, or SERP |
| Request profile | A flexible XML/XSD schema that accepts dynamic content structures |
| Response profile | A JSON profile returned by the connector |
| Tracking direction | Select Input Documents or Output Documents |
| Error behavior | Enable to handle failed operations in your process rather than only reporting them |
| Request Payload | Optional document-level override for the request. Accepts JSON, URL query style, or newline-separated key=value pairs |
Object-specific behavior
Dataset
The connector operates in one of two modes depending on whether asnapshot_id is present:
- Mode A (Filter): No
snapshot_idprovided. Filters marketplace datasets based on your query parameters. - Mode B (Snapshot): A
snapshot_idstarting withsnap_is provided. The connector polls every 10 seconds, up to 25 retries, until the snapshot is ready.
Scraper
- Mode A (Trigger): No
snapshot_idprovided. Submits a new scraping job and returns asnapshot_id. - Mode B (Snapshot): A
snapshot_idstarting withs_is provided. The connector polls for completion and downloads results.
Unlocker
Requires aurl parameter to bypass website restrictions. Supports method, country, and body parameters.
SERP
Requiresengine and query parameters. Supports multiple engines in a single request using a comma-separated list.
The connector returns all data in JSON format. If the underlying API returns non-JSON content such as HTML or CSV, the connector wraps the raw content in a JSON structure for consistent processing in Boomi.