STEP 1
Connect Bright Data and Currents
Save credentials in WEXTL once. We store them encrypted and reuse the authorization across every workflow [3]. No coding or API skills required.
Bright Data and Currents Integration
Keep Bright Data and Currents in sync by integrating their events and actions. When developer tools events happen in Bright Data, update the Currents automatically - without any line of code in visual workflow builder.
3-day trialCancel anytimeUp to 10 minutes quick set up
- GDPR
- Data Encryption
- 2FA
- Local Data Region
Learn about Bright Data and Currents
Detailed info you need to know about Bright Data and Currents integrations in WEXTL. Explore which modules apps support and how you connect them.
Bright Data
Web scraping, data collection, and proxy infrastructure for accessing blocked websites and curated marketplace datasets. [5]
How to connect Bright Data to Currents
Set up your Bright Data and Currents integration in 3 simple steps [2] — no coding required. Up to 10 minutes setup.
STEP 2
Build a workflow
Paste selected Bright Data and Currents nodes onto the canvas [4], or describe what you want and WEXTL wires the flow together with AI Builder.
STEP 3
Map your data
Choose which fields need to sync between Bright Data and Currents. Use filters or leverage a JS custom code step in between — everything is on the canvas.
How does the integration between Bright Data and Currents work in WEXTL?
WEXTL exposes actions and triggers for Bright Data and Currents that help you connect apps and automate repetitive tasks [1]. A trigger is an event that happens, an action — a step that performs when the event has occurred.
Bright Data triggersCurrents actions
Bright Data modules
- Watch Collection CompletionTriggers when Bright Data delivers the results of a Trigger Collection job to this node's inbound URL.
- Add ZoneCreates a new Bright Data zone (SERP, Scraping Browser, Residential, Mobile, ISP, or Datacenter proxy). Requires Admin or Ops role.
- Cancel SnapshotCancel Snapshots a running or paused Web Scraper snapshot.
- Cancel Studio JobPermanently stops a Scraper Studio job. The job moves to canceled and cannot be resumed.
- Crawl (Studio)Runs a synchronous real-time Scraper Studio scrape, holding the request open until it finishes or the timeout is reached.
- Delete ZonePermanently removes a Bright Data zone. Requires Admin or Ops role.
- Deliver Marketplace SnapshotShips a completed Marketplace Dataset API snapshot to a webhook, S3, GCS, Azure, Ali OSS, or other supported destination.
- Deliver SnapshotShips a completed Web Scraper snapshot to a webhook, S3, GCS, Azure, SFTP, or Snowflake destination.
- Download Marketplace SnapshotDownloads the records from a completed Marketplace Dataset API snapshot, optionally by part for large results.
- Download SnapshotDownloads the records from a completed Web Scraper snapshot, optionally by part for large results.
- Filter Marketplace DatasetRuns an async filter job (snapshot-based) against any of Bright Data's 250+ Marketplace datasets and returns a snapshot_id to download once the job completes. Same filter/operator syntax as Search.
- Get Customer BalanceReads your account's current credit balance.
- Get Dataset MetadataReturns field names, types, and descriptions for a Marketplace dataset — use this to discover filterable field names before calling Search or Filter.
- Get Delivery Destination SchemaReturns the exact fields and credentials Bright Data requires to configure a specific delivery destination type (S3, SFTP, GCS, webhook, and others).
- Get Marketplace Snapshot MetadataReturns status and size metadata for a Marketplace Dataset API snapshot (from Filter Marketplace Dataset, Trigger Collection, or a dataset subscription).
- Get Marketplace Snapshot PartsReturns the number of delivery parts for a Marketplace Dataset API snapshot — call before Download Marketplace Snapshot for a large result.
- Get Snapshot InputReturns the input array a snapshot was triggered with.
- Get Snapshot LogReturns the job log for a snapshot.
- Get Snapshot PartsReturns the number of delivery parts and per-part metadata for a snapshot.
- Get Studio DatasetDownloads the records produced by a Scraper Studio batch collection.
- Get Studio Job ErrorsReturns per-input error details for a Scraper Studio batch job.
- Get Studio Job LogReturns job metadata for a Scraper Studio job: status, input/output counts, failures, and run timestamps.
- Get Studio Job ResultFetches the result of a real-time Scraper Studio scrape by response ID.
- Get View Delivery SettingsRetrieves the current delivery configuration for a Marketplace dataset view — destination, credentials, filename, compression and batch size.
- Get Zone ConfigReads the configuration of a single zone.
- List Active ZonesLists the currently active zones in your account.
- List All ZonesLists every zone in your account, including inactive ones.
- List CountriesLists the country codes available for proxy targeting on your account.
- List Delivery Destination TypesLists the delivery destination types Bright Data supports for dataset view delivery (webhook, S3, GCS, Azure, and others).
- List Marketplace DatasetsLists every Bright Data Marketplace dataset available on your account, with id, name, and record count.
- List ScrapersLists the Web Scraper scrapers available in your account.
- List SnapshotsLists your Web Scraper collection snapshots, optionally filtered by dataset or status.
- List Studio JobsLists Scraper Studio jobs in a date range, optionally filtered to one scraper.
- List Studio ScrapersLists the Scraper Studio scrapers in your account, with active status and output schema.
- List ViewsLists your Marketplace dataset views — saved, filtered subscriptions that deliver fresh records to a destination on a recurring schedule.
- Make an API CallPerforms an arbitrary authorized API call to the Bright Data API.
- Monitor DeliveryPolls the status of a Deliver Snapshot job until it completes.
- Monitor Job ProgressReads the status and progress of an async collection job.
- Pause SnapshotPause Snapshots a running or paused Web Scraper snapshot.
- Pause Studio JobTemporarily stops a running Scraper Studio job. The job moves to paused and can be resumed later.
- Rerun SnapshotReruns a Web Scraper snapshot, returning a new snapshot ID.
- Rerun Studio JobStarts a new run from an existing Scraper Studio job, either in full or failed-inputs-only, returning a new collection ID.
- Resume SnapshotResumes a paused Web Scraper snapshot.
- Scrape URL (Sync)Runs a real-time synchronous scrape for a supported dataset and returns records inline, or falls through to a pending snapshot if the 60-second vendor timeout is hit.
- Search Marketplace DatasetRuns a real-time, Elasticsearch-powered filter query against a Bright Data Marketplace dataset and returns matching records inline with sub-second latency (up to 1,000 per call). Alpha — 3 LinkedIn datasets only.
- Send SERP SearchFetches structured Google/Bing/Yandex/DuckDuckGo search results through Bright Data's SERP API.
- Send Web RequestFetches a URL through Bright Data's Web Unlocker, bypassing anti-bot protection and CAPTCHAs.
- Trigger Collection (Async)Starts an asynchronous Web Scraper collection job and returns a snapshot ID to monitor and download later.
- Trigger Studio Scraper (Batch)Starts an asynchronous batch collection for a Scraper Studio scraper and returns a collection ID.
- Trigger Studio Scraper (Real-time)Starts an asynchronous real-time Scraper Studio scrape and returns a response ID to fetch the result later.
Currents modules
- Cancel RunCancels a run that is still in progress.
- Cancel Run by GitHub CICancels a run identified by its GitHub Actions workflow run.
- Create ActionCreates a new action that quarantines, skips, or tags matching tests.
- Create Jira IssueCreates a Jira issue from a test in a run and links it back.
- Delete ActionArchives an action so it stops applying to tests.
- Delete Project TermDeletes a tag term from a project's filter list.
- Delete RunDeletes a run and all of its associated data.
- Disable ActionDisables an action without archiving it.
- Enable ActionEnables an action that is currently disabled.
- Find RunReturns the most recent completed run matching the criteria.
- Generate Test SignatureComputes the stable signature for a test from its project, spec file, and title.
- Get ActionReturns a single action by its identifier.
- Get Affected Test ExecutionsRetrieves the executions of one affected test in a date range.
- Get InstanceReturns a single spec-file instance with its test results.
- Get ProjectReturns a single project by its identifier.
- Get Project InsightsReturns aggregated run and test metrics for a project.
- Get RunReturns a single run with its groups and spec results.
- Get Test Failure ContextReturns structured failure context for a run, a spec file, or a single test.
- Get Test ResultsRetrieves the historical executions of one test signature.
- Get WebhookReturns a single webhook by its identifier.
- Link Jira IssueLinks an existing Jira issue to a test in a run.
- List Action Test ExecutionsRetrieves the test executions where one action was applied.
- List ActionsRetrieves the actions configured for a project.
- List Affected TestsRetrieves the tests affected by actions in a date range.
- List ErrorsRetrieves errors from the Errors Explorer for a project.
- List Jira Issue TypesRetrieves the Jira issue types available for a Jira project.
- List Jira ProjectsRetrieves the Jira projects available to the connected Jira integration.
- List Project RunsRetrieves the test runs recorded for a project.
- List Project TermsRetrieves the filter terms of one kind recorded for a project.
- List ProjectsRetrieves the projects in your Currents organization.
- List Pull RequestsRetrieves the pull requests with run activity for a project.
- List Spec FilesRetrieves spec files from the Spec Files Explorer for a project.
- List TestsRetrieves tests from the Tests Explorer for a project.
- List WebhooksRetrieves the webhooks configured for a project.
- Make an API CallPerforms an arbitrary authorized API call.
- Reset RunResets failed spec files in a run so they can run again.
- Update ActionUpdates an existing action.
- Update WebhookUpdates the URL, events, headers, or label of a webhook.
- Watch EventsTriggers when a test run starts, finishes, times out, or is cancelled.
Explore alternative integrations
There are other apps [9] supported by WEXTL that can be paired with Bright Data and Currents integrations. Pick any from the list below if the current combination isn't the one you need.
Frequently asked questions
Common questions about connecting Bright Data and Currents.
Connect your Bright Data and Currents accounts once, pick a trigger in one app and an action in the other, then map the fields so data flows automatically between them. [3]
Example: when Bright Data's "Watch Collection Completion" fires, WEXTL can "Cancel Run" in Currents. Bright Data has 1 trigger (including Watch Collection Completion); Currents has 38 actions (including Cancel Run, Cancel Run by GitHub CI, and Create Action). Add filters and transforms between steps when you need them. [1]
Yes — the integration works in both directions. Use each app's triggers to start a workflow and the other app's actions to update it. [2]
No. Bright Data-to-Currents automations are built visually on the canvas. You can optionally add custom JavaScript with Functions when you need advanced logic. [4]
Yes. Trigger-based automations start the moment Bright Data (or Currents) fires a new event — webhook-backed apps run within seconds, and polling-only apps re-check on a schedule you control. [7]
A first automation typically takes 5–10 minutes: connect each app's credential once, drop a trigger + action onto the canvas, map the fields, and turn the workflow on.
You can build your Bright Data + Currents automation on a 3-day trial with every feature unlocked. Cancel anytime. For your protection, a small deposit is charged to your card when your trial starts. It counts toward your first payment and is non-refundable. [8]
References
List of sources used to gather information about the Bright Data and Currents integration.
- Bright Data and Currents integration source code, module specs and credentials implementation.
- Our Bright Data and Currents integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official vendor API documentation for Bright Data and Currents — used to verify field meanings, authentication flows, and anything our own specs don't fully capture.
- WEXTL® visual workflow builder, anonymized data from our technical support team.
- Bright Data integration information
- Currents integration information
- WEXTL® Scheduling
- WEXTL® Pricing and Trial
- WEXTL® Apps Library