Resources · Make integration

Bright Data Make integrationAutomate Bright Data with Make.

Need web data to land in your tools without a script to babysit? The Bright Data Make integration gives you 8 action modules: Web Unlocker, dataset filters and snapshot downloads. This page shows how to connect your API key and build a first working scenario.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Bright Data Make integration do for you?

The Bright Data Make integration links your Bright Data account to Make, a visual tool where you chain apps into a scenario (the automation you build, block by block). Each block is a module. Bright Data brings 8 of them, all actions: they run when an earlier step asks, so the scenario starts from another app or from Make's clock.

Unblock pages for a research team. A marketer drops a competitor URL into a spreadsheet. Make picks up that row and passes it to Run a Web Unlocker, and the result flows into the next app you choose. No one copies pages by hand.

Feed a filtered dataset to your analysts. Bright Data keeps large collections of public web records, called datasets. Filter a Dataset keeps only the records that match your filter and saves them as a snapshot: an extract you can read later. Get a Snapshot Metadata reads its details, then Download a Snapshot Content or Get a Snapshot Part brings the data into Make so you can hand it to a database or an AI step.

Reach the rest of the API. Anything the listed modules skip goes through Make an API Call, with the same connection.

A caution worth knowing: the official Make doc for this app says it was AI-generated from Bright Data's own documentation and may contain mistakes, so double-check key settings with Bright Data. If a run fails, the Make troubleshooting guide helps you read the error. The same app also exists in n8n, see the Bright Data n8n integration, and the Make training covers the editor from scratch.

Connect

How do you connect your Bright Data account to Make?

  1. 01

    Generate an API key in Bright Data

    You need an active Bright Data account first. Open Account settings, go to the API keys section, click Generate, then copy the key shown in the window. Keep it at hand for the next step.

  2. 02

    Add a Bright Data module in Make

    In your scenario, add any Bright Data module and click Create a connection. A connection is your Bright Data account linked to Make once, then reused by every Bright Data module you add later.

  3. 03

    Paste the key and save

    The Connection name field is optional, but a clear name helps when you manage several accounts. Paste the API key you copied, or follow the on-screen instructions, and confirm. Make then shows the module fields.

First scenario

Your first scenario: unblock a page when a new URL shows up

GoalWhen a new URL lands in another app, such as a spreadsheet, Make sends it to Bright Data's Web Unlocker.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the +. Bright Data has no trigger, so the first module comes from the app where your URLs live.

  2. 02

    Set the starting module

    Pick the module of that other app that watches new rows or records, connect its account, and choose the list Make should read. Each new row becomes a bundle, one item passed to the next module.

  3. 03

    Add Run a Web Unlocker

    Click the + on the right, search Bright Data, pick Run a Web Unlocker and use the connection you created. Map the data of the previous module into its fields.

  4. 04

    Test with Run once

    Add a test row, then click Run once. Make runs the scenario one time and shows the bundles each module received, so you can check what Bright Data sent back.

  5. 05

    Schedule and switch on

    Open the clock on the first module. A new scenario checks every 15 minutes by default. Adjust it, then switch the scenario on. Add a module after the unlocker to store the result.

Modules

What each Bright Data module does

Bright Data gives you 8 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Bright Data1

Download a Snapshot Content

Action

In MakeDownloads a snapshot content.

This one pulls the data held in a Bright Data snapshot into your scenario, so the next module can store it, split it or send it to an AI step.

When to use it
Filter a Dataset has created a snapshot and you want all of it in one go.
Watch out
on the Free plan Make handles files up to 5 MB, so a large snapshot may need Get a Snapshot Part instead.
Bright Data2

Filter a Dataset

Action

In MakeCreates a dataset snapshot based on a provided filter.

Here you describe the records you want from a Bright Data dataset, and the module creates a snapshot that matches your filter. It is the starting point of every snapshot flow on this page.

When to use it
a sales team asks for only the companies in one region, not the full dataset.
Watch out
this module creates the snapshot; reading it takes another module after it.
Bright Data3

Get a Snapshot Metadata

Action

In MakeGets snapshot metadata.

Rather than the data itself, this module returns the details Bright Data keeps about a snapshot. It is a light step to place between creating a snapshot and downloading it.

When to use it
you want to check a snapshot before spending operations, the units Make counts on your plan, on a download.
Watch out
the returned fields are not documented here, so run it once and read the bundle.
Bright Data4

Get a Snapshot Part

Action

In MakeGets a snapshot part.

Some snapshots are easier to handle in pieces. This module fetches one part of a snapshot, so you handle the data in smaller pieces.

When to use it
the full download is too heavy for your plan, or you want to process a snapshot in stages.
Watch out
each part fetched counts as its own operation on your Make plan.
Bright Data5

Make an API Call

Action

In MakePerforms an arbitrary authorized API call.

Your safety net. It calls any endpoint of the Bright Data API with the connection you already set up, so you are never stuck with only the listed modules.

When to use it
you need a Bright Data feature that none of the other seven modules covers.
Watch out
you write the request yourself, so keep the Bright Data API documentation open while you fill it in.
Bright Data6

Run a Web Unlocker

Action

In MakeRuns a web unlocker.

Some sites block automated visitors. Web Unlocker is the Bright Data service Make's directory presents as the way past those anti-bot blocks: give it a page, it returns the result to the next module.

When to use it
a URL arrives from a form, a sheet or a CRM and you want the page behind it without opening a browser.
Watch out
test with Run once on a single URL before the scenario runs on a whole list.
Bright Data7

Scrape Facebook (deprecated)

ActionIn the docs only

Make still lists this Facebook scraping module, but it carries the deprecated label and no official description. Make does not say why.

When to use it
only to keep an existing scenario running while you plan its replacement.
Watch out
for a new build, prefer Make an API Call or the snapshot modules, which are not flagged.
Bright Data8

Scrape Instagram (deprecated)

ActionIn the docs only

The Instagram twin of the Facebook module, also marked deprecated in Make and shipped without a description. Make gives no reason for the label.

When to use it
you inherited a scenario that already relies on it and need to understand it.
Watch out
start nothing new on it; rebuild the step with a module that is not flagged as deprecated.
Need help

Need help automating Bright Data with Make?

A person reads every message.

FAQ

Questions people ask next

01Is the Bright Data Make integration free?
On the Make side, yes. Bright Data is a standard app, available from the Free plan, which allows 2 active scenarios, a 15-minute minimum between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans lower the interval to 1 minute and remove the cap on active scenarios. You still need an active Bright Data account, and its subscription is handled on the Bright Data side, not in Make.
02What does it take to connect Bright Data to Make?
You need an active Bright Data account and a valid API key or proxy credentials. To get the key, open Account settings in Bright Data, go to API keys, click Generate and copy the key from the window. In Make, add any Bright Data module, click Create a connection, give it a name if you like, and paste the key. That single connection then serves all 8 Bright Data modules in your scenarios.
03Can a Bright Data scenario start without a trigger?
Yes, even though Bright Data has no trigger module of its own. Two routes work. Start the scenario with a trigger from another app, such as a new row in a spreadsheet or a new record in a CRM, then add a Bright Data action after it. Or put any module first and use Make's scheduling, the clock on the first module, which runs a new scenario every 15 minutes by default. Either way, Bright Data acts when an earlier step hands it data.
04What if a Bright Data module is missing in Make?
Use Make an API Call. It reaches any endpoint of the Bright Data API with the connection you already created, so a missing feature does not force you to leave Make. Keep one thing in mind: the Make doc for this app warns that it was AI-generated from Bright Data's documentation and may contain mistakes. When a setting matters, confirm it with Bright Data directly before you rely on it in production.
05Make or n8n for Bright Data: which one fits?
It depends on where your other automations already run. Bright Data is available in both tools, and in Make you get 8 modules, including Make an API Call for the rest of the API. If your team already builds in Make, keeping Bright Data there means one editor and one place to read errors. If your flows live in n8n, its Bright Data node is the natural fit. Test your own case in the tool you know before deciding.