Resources · Make integration

Browse AI Make integrationAutomate Browse AI with Make.

What happens to the website data once Browse AI has collected it? The Browse AI Make integration gives you 3 modules: 1 instant trigger and 2 actions. This guide is for teams that scrape or monitor sites, and it walks you from connection to a first working scenario.

Try the Browse AI integration on MakeSee the 3 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Browse AI Make integration let you automate?

The Browse AI Make integration links your Browse AI account to Make, a no-code tool where you build a scenario, meaning an automation made of chained modules. Each module is one brick: here, a trigger that reacts when a Browse AI task finishes, an action that runs a task, and a module that reaches the rest of the Browse AI API.

Extracted data lands where your team works. Watch Task Execution Finished fires the moment Browse AI completes a task, so the scraped result can move straight into a spreadsheet, a CRM or a chat channel handled by another app's module in the same scenario.

Tasks start from events, not from a login. Run a Task lets any other app kick off an extraction: a new lead in your CRM, a form submission, a row added to a table. The scenario decides when Browse AI works, and nobody opens the dashboard to press start.

Anything else in the API stays reachable. Make an API Call reuses the same connection to reach any endpoint of the Browse AI API that the two other modules do not cover.

The Make documentation lists no numeric limit for this app, so plan around your Make plan instead: the Make pricing page explains how operations are counted. If you want to weigh another automation tool first, the n8n vs Make comparison sets out the criteria, and the Make training covers scenario building from the basics.

Connect

How do you connect Browse AI to Make?

  1. 01

    Add a Browse AI module

    You need a Browse AI account first. In your scenario, add any Browse AI module and click Create a connection. A connection is your Browse AI account linked to Make once, then reused by every Browse AI module.

  2. 02

    Name the connection and save

    The Connection name field is optional, but a clear name helps when several people or accounts share the same Make organization. Click Save once it is filled in.

  3. 03

    Confirm access in Browse AI

    If Browse AI asks you to authenticate, sign in and confirm the access it requests. The connection then appears in the module, ready for the Run a Task and Make an API Call modules too.

First scenario

Your first scenario with Browse AI

GoalWhen a new record appears in another app, Make starts a Browse AI task with Run a Task.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + to add the first module. This one belongs to the app where your trigger event happens, such as your CRM.

  2. 02

    Set up the starting module

    Pick the module of that other app that reacts to the event you care about, connect its account and fill in its fields. Make lists what it can read once the connection exists.

  3. 03

    Add Run a Task

    Click the + on the right of the first module, search for Browse AI and choose Run a Task. Connect your account, then map data from the first module into the fields Make displays.

  4. 04

    Test with Run once

    Click Run once to execute the scenario one time. Each module shows the bundles it received, a bundle being one item passed from module to module, so you can check the task really started.

  5. 05

    Schedule and switch on

    Set the schedule on the first module, every 15 minutes by default, then switch the scenario on. To pick up the results, build a second scenario that starts with Watch Task Execution Finished.

Triggers

What starts a Browse AI scenario?

1 module starts a scenario when something happens in Browse AI. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Browse AI as soon as it happens.

Browse AI1Watch Task Execution Finished

Watch Task Execution Finished

Instant trigger

In Make“Triggers when task is finished.”

This trigger hands you the result of a Browse AI task as soon as the task finishes, so the extracted data can move to the next module without anyone checking the dashboard.

How it fires
instant, Browse AI calls Make through a webhook as soon as the task is done, with no schedule to wait for.
When to use it
a price or listing extraction whose rows should reach a sheet or a sales channel the moment they exist.
Watch out
add the module with Create a webhook before Create a connection, otherwise the trigger never receives anything.
Modules

What can the Browse AI modules do?

Browse AI gives you 2 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Browse AI1

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

With this module you reach any endpoint of the Browse AI API from your scenario, using the connection you already created, without handling authentication yourself.

When to use it
you need a Browse AI feature that neither Run a Task nor the finished-task trigger covers.
Watch out
you build the request yourself, so keep the Browse AI API reference open while filling it in.
Browse AI2

Run a Task

Action

In Make“Runs a task.”

Run a Task starts a Browse AI extraction from inside a scenario, so another app decides when the website gets read instead of someone launching it by hand.

When to use it
a new company lands in your CRM and you want its website data collected right away.
Watch out
Run a Task starts the extraction; to act the moment it finishes, the module made for that is Watch Task Execution Finished, at the start of its own scenario.
Need help

Need help automating Browse AI with Make?

A person reads every message.

FAQ

Browse AI and Make: frequent questions

01Is the Browse AI Make integration free?
Yes, on the Make side. Browse AI is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans bring the interval down to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Every module run counts as an operation, the unit Make charges against your plan. Your Browse AI subscription is a separate matter, handled on the Browse AI side.
02What do you need to connect Browse AI to Make?
A Browse AI account and a Make account. Add a Browse AI module to a scenario, click Create a connection, give the connection a name if you like and click Save. If Browse AI asks you to authenticate, sign in and confirm the access. For the trigger Watch Task Execution Finished, which is an instant module, click Create a webhook first and create the connection from there. The same connection then serves Run a Task and Make an API Call, so you only link the account once.
03Does the Browse AI trigger fire in real time?
Yes. Watch Task Execution Finished is an instant trigger: Browse AI calls Make through a webhook as soon as a task finishes, so the scenario starts on that event and does not wait for the 15 minute default schedule. That is different from scheduled triggers, which Make polls at a regular interval and which show a clock badge in the editor. Here the module shows a lightning badge. Scenarios that start with another app and then use Run a Task follow the schedule of their own first module instead.
04What if a Browse AI module is missing in Make?
Use Make an API Call. It sends a request to any endpoint of the Browse AI API with the connection you already have, which covers what Run a Task and the finished-task trigger leave out. You write the request yourself, so the Browse AI API reference is the document to keep open. The Make documentation gives no numeric limit for this app, so the constraints you meet are those of your Make plan, such as the run interval and the execution time per scenario run.
05Should you use Make or n8n for Browse AI?
It depends on your team and your stack more than on Browse AI. On Make, the app offers 3 modules, including an instant trigger, and Make an API Call fills the gaps with the same connection. The same app often has an n8n node too, so check what it offers before you choose. Then compare how each tool counts usage, which one your team already knows, and where your other apps are covered. There is no ranking to give between the two for this app, only criteria to apply to your own case.
Same platform

Other docs you might need on this stack.

Browse all integrations