Resources · Make integration

HARPA AI Web Browser Agent Make integrationAutomate HARPA AI Web Browser Agent with Make.

What if your browser could watch, read and search the web for your automations? The HARPA AI Web Browser Agent Make integration gives you 8 modules: 2 instant triggers and 6 actions. This guide shows how to link your key, then build a first scenario step by step.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the HARPA AI Web Browser Agent Make integration do?

The HARPA AI Web Browser Agent Make integration links the HARPA Chrome extension to Make, so the browser work HARPA does (reading pages, searching, running AI prompts, watching sites for changes) can feed a scenario, which is the automation you build in Make as a chain of modules. You connect once with the API key shown in the extension, and every module reuses it.

Price and content alerts that explain themselves. Watch Web Monitor starts a scenario the moment HARPA spots a change on a page you follow. Add Scrape a Web Page to grab the new text as markdown, then Run AI Prompt to turn it into a short note your team can read without opening the site.

Research on demand. Search the Web returns up to 8 results with links, titles and descriptions for any query. Pass each link to Scrape a Web Page and you have raw material for a brief, a lead list or a competitor sheet.

Browser automations triggered from anywhere. Run an AI Command launches one of your HARPA commands or workflows in the browser. When the extension answers a Run Action request, Watch Action Result hands the output back to Make, so another scenario can store or forward it.

What Make does not do here: it does not replace the extension. Several modules hand work to your HARPA browser node, and Ping a Browser Node exists to check that it is online and ready before you send anything. For endpoints the listed modules skip, Make an API Call reuses the same connection. If you also look at n8n, the n8n vs Make comparison sets the two side by side, and the Make training covers scenario design from the ground up. Stuck on an error? Read Make troubleshooting.

Connect

How do you connect HARPA AI Web Browser Agent to Make?

  1. 01

    Copy your API key from the extension

    You need an active HARPA account and the Chrome extension installed. Open the extension, click the AUTOMATE tab, and copy the API key displayed there. Keep it at hand, Make will ask for it in a moment.

  2. 02

    Add a module and create the connection

    In your Make scenario, add any HARPA AI Web Browser Agent module and click Create a connection. A connection is your HARPA account linked to Make once; every HARPA module in every scenario can reuse it afterward.

  3. 03

    Name it and paste the key

    The Connection name field is optional, but a clear label helps when you have several accounts. Paste the key you copied from the AUTOMATE tab, or follow the on-screen instructions, then save. The module is ready to fill.

First scenario

Your first scenario: summarize a page as soon as it changes

GoalWhen HARPA Web Monitor detects a change on a page you track, Make scrapes the page and has an AI prompt write a short summary of what moved.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the big +. Search for HARPA AI Web Browser Agent and pick Watch Web Monitor as the first module.

  2. 02

    Set up the webhook and connection

    Click Create a webhook, then Create a connection and paste the API key from the AUTOMATE tab. From now on, HARPA calls Make through that webhook whenever the monitor sees a change.

  3. 03

    Grab the updated page

    Click the + on the right of the trigger and add Scrape a Web Page. Enter the URL of the page you monitor so the module returns its fresh content as markdown text.

  4. 04

    Ask the AI for a summary

    Add Run AI Prompt after the scraper. Write a prompt such as "list what changed and why it matters" and map the markdown from the previous module into it. Each item passed along is a bundle.

  5. 05

    Test, then switch it on

    Click Run once, trigger a change on a monitored page, and read the bundles each module received. Once the summary looks right, switch the scenario on so it waits for the next change.

Triggers

What can start a HARPA scenario?

2 modules start a scenario when something happens in HARPA AI Web Browser Agent. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by HARPA AI Web Browser Agent as soon as it happens.

HARPA AI Web Browser Agent1Watch Action Result

Watch Action Result

Instant trigger

In Make“Triggers when the HARPA Chrome Extension Node has responded to a Run Action request.”

This trigger collects the answer your browser sends back after a Run Action request, so the result of a HARPA job lands in Make as a bundle you can store, forward or reuse in the next module.

How it fires
instant, the app calls Make through a webhook as soon as the extension node has responded.
When to use it
you launch browser jobs from one scenario and want a second, separate scenario to pick up each result and push it to a sheet, a CRM or a chat channel.
Watch out
nothing arrives until the extension node has answered, so if the browser is not ready, the result never shows up; Ping a Browser Node lets you check it first.
HARPA AI Web Browser Agent2Watch Web Monitor

Watch Web Monitor

Instant trigger

In Make“Triggers when the HARPA Web Monitor detects a change in a web page content, price, text etc.”

Watch Web Monitor turns HARPA's page watching into a starting point: whenever the monitor notices that a page's content, price or text has moved, Make receives the change and your scenario runs.

How it fires
instant, the app calls Make through a webhook as soon as it happens.
When to use it
you follow a competitor's pricing page, a supplier catalog or a job board and want an alert, a log line or an AI summary whenever something on it shifts.
Watch out
the trigger only receives what the HARPA Web Monitor reports, so a page that HARPA is not watching will never start the scenario.
Modules

What can HARPA AI Web Browser Agent do in Make?

HARPA AI Web Browser Agent gives you 6 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

HARPA AI Web Browser Agent1

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Make an API Call sends any authorized request to the HARPA API with the connection you already set up, which covers whatever the ready-made modules leave out.

When to use it
the endpoint you need has no dedicated module in the list, and you know from HARPA's documentation which path and parameters to send.
Watch out
you build the request yourself, so read the vendor documentation before you trust the output in production.
HARPA AI Web Browser Agent2

Ping a Browser Node

Action

In Make“Sends ping message to your HARPA Browser Extension to check if it is online and ready to run actions.”

Ping a Browser Node tells you whether your HARPA extension is online and ready, before any real work gets sent to it, so you know the browser is there before the scenario leans on it.

When to use it
place it at the start of a scenario that scrapes, searches or runs commands, and read its answer during Run once before the heavier modules fire.
Watch out
a ping only tells you the node is ready at that moment, so keep it right before the module that needs the browser.
HARPA AI Web Browser Agent3

Run AI Prompt

Action

In Make“Runs your AI prompt using any AI connection on any webpage without the need to build a custom command in HARPA.”

Run AI Prompt gives you an AI answer on any webpage using one of your AI connections in HARPA, without first building a custom command inside the extension.

When to use it
you want a quick summary, a classification or a rewrite of page content that arrives from an earlier module, such as the markdown from Scrape a Web Page.
Watch out
the answer depends on the AI connection you pick in HARPA, so test with Run once on a few pages before sending the answers anywhere important.
HARPA AI Web Browser Agent4

Run an AI Command

Action

In Make“Runs AI powered web automation, workflow or command in your browser.”

Run an AI Command starts an AI powered automation, workflow or command inside your browser, so the multi-step jobs you already use in HARPA can be launched from a scenario.

When to use it
a command you built in HARPA already does the job by hand, and you want an event in another app to set it off instead of a click.
Watch out
when one prompt is enough, Run AI Prompt does the job without building a custom command in HARPA first.
HARPA AI Web Browser Agent5

Scrape a Web Page

Action

In Make“Turns a specified URL into a markdown text. Extracts elements content by CSS / XPath / Text selectors.”

Scrape a Web Page turns a URL into clean markdown text and can pull out specific elements with CSS, XPath or text selectors, which gives the next module readable content instead of raw HTML.

When to use it
you need a product price, a headline or a whole article body from a page, for example right after Search the Web or Watch Web Monitor.
Watch out
selectors break when a site changes its layout, so check the bundle after any redesign.
HARPA AI Web Browser Agent6

Search the Web

Action

In Make“Searches the web for the given query. Returns up to 8 search results: links, titles, descriptions.”

Search the Web runs a query and hands back up to 8 results, each with its link, title and description, ready to map into the following modules.

When to use it
you want fresh sources on a topic, a company or a product before scraping them or asking an AI prompt to compare them.
Watch out
the list stops at 8 results, so for wider coverage split the topic into several narrower queries.
Need help

Need help automating HARPA AI Web Browser Agent with Make?

A person reads every message.

FAQ

Questions about the HARPA AI Web Browser Agent Make integration

01Is the HARPA AI Web Browser Agent Make integration free?
Yes, on the Make side. HARPA AI Web Browser Agent is a standard app, so it works from the Free plan. That plan allows 2 active scenarios, a scheduled run every 15 minutes at the shortest, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) drop the interval to 1 minute and remove the cap on active scenarios. You still need an active HARPA account with an API key, and HARPA's own subscription is described on its pricing page.
02What do you need to connect HARPA AI Web Browser Agent to Make?
You need an active HARPA account, the HARPA Chrome extension, and the API key that the extension shows under its AUTOMATE tab. In Make, add a HARPA module, click Create a connection, optionally give it a name, then paste the key. For the two instant triggers, Make asks you to click Create a webhook first and create the connection from there. One connection serves every HARPA module afterward, in any scenario you build.
03Does the HARPA AI Web Browser Agent Make integration react in real time?
Yes. Both triggers are instant: HARPA calls Make through a webhook as soon as the event happens, so there is no polling interval to wait for. Watch Web Monitor fires when the monitor detects a change in a page's content, price or text. Watch Action Result fires when the extension node has answered a Run Action request. The only condition is that your browser extension is online, which Ping a Browser Node lets you check from a scenario.
04What if a HARPA module is missing from the Make integration?
It depends on what is missing. The integration includes Make an API Call, which sends any authorized request to the HARPA API using your existing connection, so endpoints without a dedicated module stay reachable. You will need HARPA's documentation to know which path and parameters to use. Keep in mind that Make's own documentation for this app is AI-generated from the vendor docs and may contain mistakes, so contact HARPA directly when an important detail is unclear.
05Should you use Make or n8n for HARPA AI Web Browser Agent?
It depends on the tool you already run. The same app often has an n8n node too, so the choice rarely comes down to HARPA itself. In Make, you get 8 ready-made modules, including 2 instant triggers and Make an API Call for anything else, plus a visual editor where you test with Run once before switching a scenario on. If your automations already live in n8n, check for the HARPA node there before rebuilding anything in Make.