Resources · Make integration

Anchor Browser Agent Make integrationAutomate Anchor Browser Agent with Make.

Can a Make scenario drive a real browser for you? The Anchor Browser Agent Make integration gives you 15 modules: 14 actions and 1 search. This guide shows how to link your account, build a first scenario and pick the right module for each job.

Try the Anchor Browser Agent integration on MakeSee the 15 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Anchor Browser Agent Make integration do?

The Anchor Browser Agent Make integration lets a Make scenario (the automation you build in Make, a chain of modules) send browser work to Anchor Browser Agent. Each module is one brick of that chain. Here the bricks open pages, click, type, scroll, take screenshots and hand tasks to the agent, with no code on your side.

Read a page when a link shows up. A row lands in a sheet with a product URL. Navigate To URL opens it, then Get Webpage Content passes what the page shows to the next module, so a researcher stops copying text by hand.

Keep visual proof of a page. An account manager wants a picture of a landing page after each campaign change. Screenshot Webpage is the module named for that job, and the image can travel to your storage app in the same scenario.

Hand a whole errand to the agent. When you would rather describe the goal than script each click, Perform Web Task, Create Task and Run Task are the modules built around tasks. List Tasks brings back the tasks already there.

Be aware of one real limit: Make itself warns that its documentation for this app is incomplete, because little public information exists. The module names are known, and what each one does below is read from its name; their fields you discover in the editor. The app has no trigger, so something else has to start the scenario. If a need falls outside the list, Make an API Call reaches the rest of the app's API. For help with the editor, see the Make training or the Make troubleshooting guide; to weigh the two tools, read n8n vs Make.

Connect

How do you connect Anchor Browser Agent to Make?

  1. 01

    Add a module and open the connection

    In your scenario, add any Anchor Browser Agent module, then click Create a connection. A connection is your Anchor Browser Agent account linked to Make once and reused by every module of the app.

  2. 02

    Name it and authorize Make

    Give the connection a name if you like, which helps when you run several accounts. Then either authorize Make on the Anchor Browser Agent page that opens, or paste the key the app gives you, depending on what Make asks for.

  3. 03

    Save and check the module

    Click Save. The module now shows your connection and you can fill its fields. From here on, every other Anchor Browser Agent module in any scenario can pick the same connection from its list.

First scenario

Your first scenario with Anchor Browser Agent

GoalWhen another app hands your scenario a web address, Make opens it with Anchor Browser Agent and passes along what the page contains.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the +. Pick the trigger of the app that holds your links, for example a sheet or a form, since Anchor Browser Agent has none.

  2. 02

    Add Navigate To URL

    Click the + on the right of that first module, search Anchor Browser Agent and choose Navigate To URL. Click Create a connection if this is your first module of the app.

  3. 03

    Map the address

    Fill the module fields. Map the web address from the first module into the matching field, so each new bundle (one item flowing from module to module, here one link) opens its own page.

  4. 04

    Add Get Webpage Content

    Click the next + and add Get Webpage Content. Fill the fields Make shows, with the same address or a value that Navigate To URL returned; Run once tells you which. The content then flows to whatever you add after, such as a sheet or a message.

  5. 05

    Test with Run once

    Click Run once to execute the scenario one time. Open the bubble above each module to read the bundles it received, and fix any field that came back empty before going further.

  6. 06

    Schedule and switch on

    Set the schedule on the first module with the clock icon. A new scenario checks every 15 minutes by default, and the Free plan cannot go below that. Switch the scenario on to let it run.

Modules

What each Anchor Browser Agent module does

Anchor Browser Agent gives you 15 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Anchor Browser Agent1

Create Session

ActionIn the docs only

Create Session is the module whose name points to opening a browser session on Anchor Browser Agent, a starting point the browsing modules can then work in. Make's documentation does not describe what it returns, so read its output before relying on it.

When to use it
at the start of a chain that clicks, types and scrolls on the same site, before the first browsing step.
Watch out
run it once with Run once and note which value the next modules need from it.
Anchor Browser Agent2

Create Task

ActionIn the docs only

With Create Task you record a task in Anchor Browser Agent from your scenario, as its name says. Picture a form reply that should turn into a job for the agent later rather than right away.

When to use it
when you want to prepare the task in one place and launch it at another point, with Run Task.
Watch out
the documentation gives no field list, so open the module and let Make show what it accepts before you map anything.
Anchor Browser Agent3

Get Webpage Content

ActionIn the docs only

Get Webpage Content fetches what a page holds and hands it to the next module as data you can map. It is the bridge between a web page and your sheet, CRM or message.

When to use it
a price, an announcement or a listing sits on a page with no export, and you want it inside your tools.
Watch out
check the first run with Run once; the documentation does not say which format the content comes back in.
Anchor Browser Agent4

Keyboard Shortcut

ActionIn the docs only

Keyboard Shortcut sends a key combination to the browser, the way your hands would on the keyboard. It covers the moments where a page reacts to keys rather than to a click.

When to use it
after Type Text, to submit a search box that only listens to the Enter key, or to trigger a site shortcut.
Watch out
a shortcut only acts on the page currently open, so place it after the module that brings you there.
Anchor Browser Agent5

List Tasks

SearchIn the docs only

List Tasks is the only search module of the app: it returns the tasks already stored in Anchor Browser Agent, possibly none, one or many. Each task comes out as its own bundle.

When to use it
to review what exists before creating a duplicate, or to feed Run Task with a task chosen from the list.
Watch out
every returned task runs the following modules once, and each run costs operations, the unit Make counts on your plan.
Anchor Browser Agent6

Make an API Call

ActionIn the docs only

Make an API Call reaches any endpoint of the Anchor Browser Agent API from your scenario, using the same connection as the other modules. It is the door to everything the named modules leave out.

When to use it
when none of the other 14 modules matches your need and the Anchor Browser Agent API offers it.
Watch out
you write the request yourself here, so keep the app's API reference open beside the editor.
Anchor Browser Agent7

Mouse Click

ActionIn the docs only

Mouse Click presses once on a spot of the page, just like a single click from you. Buttons, tabs, links and checkboxes all answer to it.

When to use it
to accept a cookie banner, open a menu or press a Next button between two other steps of the chain.
Watch out
if the page moves between runs, the click can land elsewhere; test it with Run once and look at a Screenshot Webpage output to confirm.
Anchor Browser Agent8

Mouse Double Click

ActionIn the docs only

Mouse Double Click gives two quick presses on the same spot. Some interfaces only open an item, or select a whole word, when they receive exactly that gesture.

When to use it
a file in a web viewer or a cell in an online table stays shut after a plain Mouse Click.
Watch out
keep it for elements that ignore a single click, and confirm with Run once that the item really opened.
Anchor Browser Agent9

Mouse Move

ActionIn the docs only

Mouse Move slides the pointer to a place on the page without clicking. Hover menus and tooltips appear this way, and nothing else would reveal them.

When to use it
a navigation menu unfolds only on hover, and the link you need hides inside it; move first, then click.
Watch out
the pointer leaves no trace, so pair it with Screenshot Webpage during your tests to see what the hover revealed.
Anchor Browser Agent10

Navigate To URL

ActionIn the docs only

Navigate To URL loads a web address in the browser driven by Anchor Browser Agent. Most browsing chains begin here, because every click or read needs a page to act on.

When to use it
right after the module that brings the link, for instance a new row holding a product or competitor page.
Watch out
map the address from the previous module rather than typing it, or every run will open the same page.
Anchor Browser Agent11

Perform Web Task

ActionIn the docs only

Perform Web Task asks the agent to carry out a job on the web in one step, going by its name, instead of you chaining clicks and keystrokes. It suits errands easier to describe than to script.

When to use it
the path through the site changes often, or would take a long line of Mouse Click and Type Text modules.
Watch out
the documentation says nothing about its output, so read the returned bundle before mapping it.
Anchor Browser Agent12

Run Task

ActionIn the docs only

Run Task launches a task that already exists in Anchor Browser Agent, as its name suggests. It pairs with Create Task, which prepares the job, and List Tasks, which finds it.

When to use it
the same task should run again whenever an event happens in another app, like a new order or a new lead.
Watch out
make sure you pass the right task; a search upstream can return several, and each one would start.
Anchor Browser Agent13

Screenshot Webpage

ActionIn the docs only

Screenshot Webpage captures an image of the page so your scenario can file it, share it or attach it. It gives you visual proof where text alone would not convince anyone.

When to use it
to keep a record of a page after a change, or to check what the browser saw while you build the scenario.
Watch out
if the image comes back as a file, remember the Free plan caps files at 5 MB.
Anchor Browser Agent14

Scroll Page

ActionIn the docs only

Scroll Page moves the view down or up the page. Content that loads only when you reach it, and buttons placed at the bottom, become reachable after it.

When to use it
before Get Webpage Content on a long listing that shows more results as you go down.
Watch out
each scroll is one more module run, and so one more operation; add only the ones the page truly needs.
Anchor Browser Agent15

Type Text

ActionIn the docs only

Type Text enters characters in the browser, as if you typed them. Search boxes, form fields and login inputs are where it earns its place.

When to use it
a lead name coming from your CRM must be typed into a site's search bar before reading the result.
Watch out
click the field first with Mouse Click, then finish with Keyboard Shortcut if the page waits for Enter.
Need help

Need help automating Anchor Browser Agent with Make?

A person reads every message.

FAQ

Questions about Anchor Browser Agent and Make

01Is the Anchor Browser Agent Make integration free?
Yes, on Make's side. Anchor Browser Agent 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 (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution, with usage counted in operations per month. Your Anchor Browser Agent account is separate, and this page says nothing about its price.
02What do you need to connect Anchor Browser Agent to Make?
An Anchor Browser Agent account and a Make account. Make's documentation lists no specific prerequisite and no official steps for this app, so the generic flow applies: add a module, click Create a connection, name it if you wish, authorize Make on the app's page or paste the key the app provides, then click Save. The connection is then reused by every Anchor Browser Agent module you add, in any scenario, so you only set it up once.
03Does Anchor Browser Agent trigger a Make scenario in real time?
No, because the app has no trigger module at all. The scenario has to start elsewhere. You can open it with the trigger of another app, for example a new row or a new form entry that carries the link to visit. Or you can start it on Make's own schedule, set with the clock on the first module: every 15 minutes by default, never below that on the Free plan and down to 1 minute on paid plans. Either way, Anchor Browser Agent modules come after the starting point.
04What if a module is missing in the Anchor Browser Agent Make integration?
Use Make an API Call. It calls any endpoint of the Anchor Browser Agent API from your scenario, with the same connection as the other modules, so you are not limited to the 14 named ones. Keep in mind that Make states its documentation for this app is incomplete, since little public information exists about it. Test each module with Run once and read the bundles it returns before building on it. If the API does not offer what you need either, another app will have to cover that step.
05Should you use Make or n8n with Anchor Browser Agent?
It depends on the tool your team already knows. On Make, you get 15 ready modules for this app, a visual editor with Run once for testing, and Make an API Call for anything else. Make's documentation does not say whether an n8n node exists for Anchor Browser Agent, so check the n8n side before comparing. Base the choice on the modules you actually need and on which editor you are more comfortable in, rather than on general claims about either tool.
Same platform

Other docs you might need on this stack.

Browse all integrations