Resources · Make integration

Airtop Make integrationAutomate Airtop with Make.

What if a browser could open a website, read it and fill it in while you do something else? The Airtop Make integration gives you 26 action modules that drive an Airtop cloud browser. This guide is for ops and growth people who already know Airtop and want a first working scenario without code.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Airtop Make integration do for you?

The Airtop Make integration links Airtop to Make so a scenario (the automation you build in Make, a chain of bricks called modules) can open a cloud browser (a web browser that runs online, not on your computer), visit pages, act on them and bring the results back. Every Airtop module is an action: something else has to start the scenario, like a schedule or another app.

A page turned into clean text. Create Session opens the browser, Smart Scrape returns the page as markdown, and Terminate Session closes everything. Each item passed from one module to the next is a bundle; drop that bundle into a sheet or a database module from another app.

A form filled without anyone typing. A new row in your CRM can feed Load URL, then Fill Form with the data from that row. For fiddly pages, Click an Element, Type and Scroll let you act step by step, and Take Screenshot keeps proof of what the page showed.

A login a human handles. Some sites need a real person to sign in. Create Human Auth Request asks a user to log in, and Save Profile On Termination keeps the cookies and local storage for the next session. Paginated Extraction and Run Agent cover long result lists and your own Airtop agents.

What Make does not offer here: there is no trigger module, and no Make an API Call module to reach something the 26 modules skip. Make's own documentation for Airtop is also flagged as limited, so expect to test each module on a real page. If a run fails, the Make troubleshooting guide is a good first stop.

Airtop also has a node in n8n: the Airtop n8n integration page covers it, and n8n vs Make helps you pick a side.

Connect

How do you connect Airtop to Make?

  1. 01

    Add an Airtop module

    In your scenario, add any Airtop module, Create Session is a natural first pick, then click Create a connection. A connection is your Airtop account linked to Make once; every Airtop module in any scenario reuses it afterwards.

  2. 02

    Name it if you like

    Naming the connection is optional. It becomes useful as soon as you run more than one Airtop account, say one for a client project and one for internal tests, because the name is what you pick from the list later.

  3. 03

    Authorize and save

    Make either sends you to an Airtop authorization page or asks for a key that Airtop gives you, depending on how the app is set up. Approve access or paste the key, then click Save. The module now shows your account.

First scenario

Your first scenario with Airtop and Make

GoalWhen the schedule you set in Make comes around, Airtop opens a browser session, scrapes a page to markdown, then closes the session.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the big + to place the first module. Airtop has no trigger, so the first Airtop module simply runs whenever the scenario starts.

  2. 02

    Open a session

    Search for Airtop, pick Create Session and click Create a connection to link your account. This module starts the cloud browser that the next modules will use.

  3. 03

    Scrape the page

    Click the + on the right of Create Session and add Smart Scrape. Map what Create Session returned into it, then enter the address of the page you want as markdown.

  4. 04

    Close the browser

    Add Terminate Session after Smart Scrape and map the same session. Closing it at the end keeps sessions from piling up after each run of the scenario.

  5. 05

    Test with Run once

    Click Run once. Make runs the scenario one time and shows the bundles each module received, so you can read the markdown Smart Scrape produced before going further.

  6. 06

    Schedule and switch on

    Open the clock on the first module. A new scenario runs every 15 minutes by default; change it to suit your need, then switch the scenario on. Each module run counts as one operation on your Make plan.

Modules

The 26 Airtop modules, and when to reach for each

Airtop gives you 26 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Airtop1

Click an Element

Action

In MakeExecutes a click on an element given a description

This module clicks a button, a tab or a link that you describe in words, instead of pointing to it in code. It is the simplest way to move through a site the way a person would.

When to use it
a results page hides the data behind a "Show more" button that must be pressed first.
Watch out
a vague description can land on the wrong element, so name it the way it appears on screen.
Airtop2

Create Human Auth Request

Action

In MakeCreates a human authentication request to ask a user to log into a service

Some logins resist automation. Create Human Auth Request asks a real user to sign in to a service, so the browser can carry on once that person is done.

When to use it
a supplier portal needs a login step that your team prefers to handle by hand, with a Slack or email module from another app telling them.
Watch out
keep the request details from the output, since the Get, Update and Delete modules work on that same request.
Airtop3

Create New Browser Window

Action

In MakeCreates a new browser window inside a session. Can load a URL when created.

Opens an extra window inside a session that already exists, and can load an address straight away. You get a second tab for the same browser, with the same cookies.

When to use it
you need to compare two pages side by side, or keep a dashboard open while another window does the clicking.
Watch out
it needs a live session, so place it after Create Session in the scenario.
Airtop4

Create Session

Action

In MakeCreates an Airtop browser session.

Starts an Airtop cloud browser session, the base that almost every other module here builds on. Nothing loads, clicks or scrapes until a session exists.

When to use it
as the first Airtop step of nearly any scenario, right after whatever starts it, such as a schedule or a new row in a sheet.
Watch out
pair it with Terminate Session at the end, otherwise sessions stay open after the scenario has moved on.
Airtop5

Delete Human Auth Request

Action

In MakeDeletes a human authentication request once the user is done with it.

Removes a human authentication request once the person has finished logging in. It tidies up after the login step instead of leaving old requests lying around in your Airtop account.

When to use it
at the end of a branch where Create Human Auth Request was used and the browser has already gone past the login screen.
Watch out
map the ID from Create Human Auth Request, and delete only once the person has really finished.
Airtop6

Fill Form

Action

In MakeFill the form in the page with the provided data.

Fill Form writes the data you provide into the form shown on the page, in one module instead of a chain of clicks and typing. You map values from earlier bundles and Airtop places them.

When to use it
each new lead from your CRM has to be entered into a partner portal that has no integration of its own.
Watch out
run it with Take Screenshot afterwards during tests, so you can see what really landed in each box.
Airtop7

Get Browser Window Info

Action

In MakeGet browser window information including a Live View URL.

Returns information about a browser window, including a Live View URL. That link lets a person watch what the cloud browser is doing on that window.

When to use it
a colleague needs to follow a tricky run, or step in during a login, and you want to send them the live link by message.
Watch out
the link points to one window only, so fetch it for the window that actually does the work.
Airtop8

Get File

Action

In MakeDownloads a file once available

Downloads a file from Airtop once it is available, so the next module in Make can store or send it. Think of it as the exit door for what the browser fetched.

When to use it
a site exports a PDF or a CSV after a click, and you want that file in a drive or attached to an email.
Watch out
the file only comes back once ready; on the Free plan, Make handles files up to 5 MB.
Airtop9

Get Human Auth Request

Action

In MakeGet an authentication request payload by ID.

Reads back an authentication request by its ID and returns its payload. You find out where that request stands without creating a new one.

When to use it
after asking someone to log in, a later module checks the request before the browser goes on to the protected pages.
Watch out
it needs the ID returned by Create Human Auth Request, so map it from that module rather than typing it.
Airtop10

Hover on an Element

Action

In MakeExecutes a hover action on an element.

Moves the pointer over an element without clicking it. Plenty of menus and tooltips only show their content when the mouse sits on top of them.

When to use it
a navigation menu unfolds on hover and the link you need sits inside it, so Hover comes just before Click an Element.
Watch out
on its own it changes nothing visible in your results; it prepares the page for the next module.
Airtop11

List Files

Action

In MakeLists all files available for a given browser session

Lists every file available for a given browser session. Each file comes out as its own bundle, ready for the following modules.

When to use it
several downloads happened during the session and you want to collect them all before closing it, feeding each into Get File.
Watch out
each file listed then runs the next modules once, and every module run is an operation on your plan.
Airtop12

List Windows

Action

In MakeLists all browser windows in a session

Shows all the browser windows currently open in a session. Handy once a scenario has opened more than one and you lose track of which is which.

When to use it
a site opened a new window on its own after a click, and you need to find it before loading or scraping anything there.
Watch out
several windows mean several bundles, so later modules may run once per window.
Airtop13

Load a File into Session

Action

In MakeLoad a previously uploaded file into a session

Makes a file you uploaded earlier available inside a browser session. Airtop keeps the file at organization level; this module brings it into the session where the page can use it.

When to use it
a form asks for an attachment, such as a signed quote, and the file was sent to Airtop with Upload File.
Watch out
it only works on a file already uploaded, so Upload File must come first.
Airtop14

Load URL

Action

In MakeLoads a URL on an existing window.

Sends an existing window to a new address. The session, its cookies and its open windows stay the same, only the page changes.

When to use it
you walk through a list of product pages one after another in the same session, mapping each address from a sheet.
Watch out
it needs a window that already exists; to open a fresh one with a page, Create New Browser Window can load it directly.
Airtop15

Page Query

Action

In MakeQuery a page to extract data or ask a question given the data on the page.

Ask the page a question in plain words, or tell it what data to pull out, and get the answer back from what is on screen. It is the quickest route from a page to one precise piece of information.

When to use it
you want only the price and stock status of a product, not the whole page.
Watch out
phrase the question tightly; a loose question gets a loose answer.
Airtop16

Paginated Extraction

Action

In MakeExtract content from paginated or dynamically loaded pages.

Pulls content from pages split into several screens, or from lists that keep loading as you scroll. It handles the page-to-page walk that would otherwise take a loop of clicks.

When to use it
a directory or a search result spans many pages and you need every entry, not just the first screen.
Watch out
long lists mean long runs, and the Free plan caps a scenario run at 5 minutes.
Airtop17

Run Agent

Action

In MakeRun an airtop agent

Runs one of your Airtop agents from inside a Make scenario. The agent does its own browsing work, and Make handles what comes before and after.

When to use it
you already built an agent in Airtop and want a new form entry or a new row in a table to launch it.
Watch out
the agent is set up on the Airtop side; Make only starts it, so fix its behavior in Airtop.
Airtop18

Save Profile On Termination

Action

In MakeSave in a profile changes made in your browsing session such as cookies and local storage.

When the session ends, this saves what changed in the browser, such as cookies and local storage, into a profile. The next session can start already signed in.

When to use it
a person logged in once through a human auth request and you don't want to ask them again on the next run.
Watch out
set it before Terminate Session; once the session is gone, there is nothing left to save.
Airtop19

Scroll

Action

In MakeExecutes a scroll action in the page or within a scrollable element

Scrolls the whole page, or just one scrollable area inside it. Many sites only load their lower sections once a visitor gets there, so nothing below the fold exists until you scroll.

When to use it
reviews or comments appear only at the bottom of a product page, and you scroll before running Page Query or Smart Scrape.
Watch out
for lists split over many pages, Paginated Extraction does the walk for you.
Airtop20

Smart Scrape

Action

In MakeScrape a page and return the data as markdown.

Reads the whole page and returns it as markdown, a light text format that keeps headings and lists. That text drops easily into a document, a sheet cell or an AI module.

When to use it
you want the full content of an article or a help page, not one precise field.
Watch out
for a single value, Page Query gives a shorter and cleaner answer than a full markdown dump.
Airtop21

Take Screenshot

Action

In MakeTake a screenshot of the current page loaded in the browser

Captures an image of the page currently loaded in the browser. It is visual proof of what the page looked like at that moment.

When to use it
you archive a competitor's pricing page, or you check that Fill Form really put the right values in place.
Watch out
the capture shows the current state only, so place it after the clicks or scrolls that bring the page where you want it.
Airtop22

Terminate Session

Action

In MakeTerminate a session

Closes an Airtop session and every window in it. The browser stops, and nothing keeps running once the scenario is done with it.

When to use it
as the last Airtop step of every scenario that opened a session with Create Session.
Watch out
if a module before it fails, Make can stop the run before this step, so check for open sessions after errors during testing.
Airtop23

Trigger File Input

Action

In MakeExecutes a file input interaction in a specific browser window

Activates the file picker in a given browser window, the moment where a site asks you to choose a document. Combined with a file loaded into the session, it completes the upload on the page.

When to use it
a partner portal requires an attachment before the form can be sent.
Watch out
the file must already be in the session, via Upload File then Load a File into Session.
Airtop24

Type

Action

In MakeExecutes a type action on an element

Types text into a field on the page, character by character, as a person at a keyboard would. It suits single boxes where Fill Form would be overkill.

When to use it
a search bar on a site where you enter a company name from your CRM before reading the results.
Watch out
typing alone often doesn't submit anything; follow it with Click an Element on the search button.
Airtop25

Update Human Auth Request

Action

In MakeUpdates a human authentication request.

Changes an existing human authentication request instead of creating another one. You fix the request you already have rather than sending your teammate a second one.

When to use it
the login step changed, or you need to correct a request already sent to a teammate.
Watch out
map the ID of the original request; without it, there is nothing for this module to update.
Airtop26

Upload File

Action

In MakeUploads a file to your Airtop organization

Sends a file to your Airtop organization, where sessions can later pick it up. It is the entry point for any document the browser will need to attach.

When to use it
a contract from your drive must be submitted on a website, so you upload it here and load it into the session next.
Watch out
on the Free plan, Make moves files up to 5 MB, which matters for heavy PDFs.
Need help

Need help automating Airtop with Make?

A person reads every message.

FAQ

Airtop and Make: common questions

01Is the Airtop Make integration free?
Yes, on the Make side. Airtop is a standard app, so it works from the Free plan. That plan has limits worth knowing for browser work: 2 active scenarios, at least 15 minutes between scheduled runs, 5 minutes of execution per run at most, and files up to 5 MB. Paid Make plans lower the minimum interval to 1 minute and allow 40 minutes of execution. Your Airtop account itself is a separate matter, and this page says nothing about its pricing.
02What does it take to connect Airtop to Make?
An Airtop account and a Make account. Make's documentation lists no specific prerequisite for Airtop and is marked as limited, so there is no official checklist to follow. In practice you add an Airtop module, click Create a connection, optionally give it a name, then either approve access on an Airtop page or paste a key Airtop provides, and click Save. After that, every Airtop module in every scenario can reuse that same connection, so you only do this once per account.
03Can Airtop start a Make scenario on its own?
No. Airtop has no trigger module in Make, only 26 actions, so it never starts a scenario by itself. The scenario has to start some other way: with the schedule on the first module, which is every 15 minutes by default (15 minutes at the shortest on Free, 1 minute on paid plans), or with a trigger from another app, such as a new row in a sheet or a new deal in your CRM. Airtop then runs as the following steps.
04What if the Airtop module you need is missing?
It depends on the gap. The Airtop app in Make has no Make an API Call module, so you cannot call an unlisted Airtop endpoint from there. First check whether Run Agent covers the task, since an Airtop agent can do browsing work that no single module does. If not, another web data app in Make, such as Apify or AI Scraper by Parsera, may fit. For anything more specific, the Hack'celeration team can look at your case.
05Make or n8n: which one fits Airtop better?
It depends mostly on where the rest of your automations already live. Airtop exists on both platforms. On Make you get 26 action modules and no trigger, with scenarios started by a schedule or another app. If your team already builds in Make, staying there keeps every connection in one place. If your workflows are in n8n, use the Airtop node there instead. Neither choice changes what Airtop itself does in the browser.