Resources · n8n integration

Airtop n8n integrationAutomate Airtop with n8n.

What if a workflow could open a browser, read a page and click a button on its own? That is the whole point of the Airtop n8n integration. The node exposes 24 operations across 6 resources, Agent, Session, Window, Extraction, Interaction and File, for anyone who needs data from sites no API covers.

Verified Trustpilot reviews · AI, automation & growth agency

Why automate

Why set up the Airtop n8n integration?

Airtop runs a cloud browser that n8n can steer step by step. You open a session, open a window in it, point that window at a URL, then ask questions about what is on screen or act on the page the way a person would. Everything happens inside the workflow, so the page content becomes regular n8n data that the next node can use.

The first scenario is research at volume. A list of company URLs sits in Google Sheets, the workflow loops over it, and extraction.query asks each page a plain-language question: who runs the company, which plan is listed first, is there a careers link. The answer comes back as workflow data, and the loop writes it to the next column.

The second one is catalog collection. Product listings that split across pages, or load more rows as you scroll, are what extraction.getPaginated is built for. You describe what to pull, pick a Pagination Mode, and let the operation walk the pages. Feed the result into Microsoft Excel 365 or push a daily digest to Slack.

The third one is the logged-in chore nobody wants to do by hand. A session created with Save Profile keeps cookies and local storage under a profile name, so the next run starts already signed in. From there interaction.fill, interaction.click and session.waitForDownload handle the weekly report that a supplier portal only offers as a download button.

Anything the Airtop API does that falls outside these 24 operations goes through the HTTP Request node, which calls any endpoint of the API while reusing the same credential through predefined authentication. That is the standard escape hatch in n8n, and it means the node covers the common path while HTTP Request covers the rest.

Worth knowing before you build: this tool has no trigger node in n8n, so a workflow starts with something else, usually a Schedule Trigger at a fixed interval or an n8n Webhook, meaning a URL a third party calls. Sessions also cost resources while they stay open, and an idle session times out after 10 minutes by default, so plan where you terminate them. If you want the broader picture of the platform first, read the n8n review, and the n8n training covers expressions and loops, which you will use a lot here.

Connect

How do you connect Airtop to n8n?

  1. 01

    Create your Airtop account

    The credential is built on an API key, so you need an account on the Airtop Portal before touching n8n. Sign up, then keep the portal open in a second tab. The n8n node has no authentication selector of its own: one credential type covers all 24 operations, and once it is saved every Airtop node in every workflow can pick it from a dropdown.

  2. 02

    Generate an API key

    In the Airtop Portal, go to the API Keys page and select the + Create new key button. Enter a name for the key, something that tells you later which workflow uses it. Select the generated key to copy it. This is the one value n8n needs, so copy it carefully rather than retyping it from a screenshot.

  3. 03

    Save the credential in n8n

    In n8n, open the Credentials menu, create an Airtop credential and paste the value into the API Key field. A credential is created once and reused everywhere, on n8n Cloud and on a self-hosted instance alike. Save it, then drop an Airtop node into a workflow and pick the credential from its list.

Actions

What can the Airtop node do in n8n?

The Airtop node exposes 24 operations across 6 resources. For each one: the node as you configure it in n8n, the required fields, and our field notes.

Resources × operations matrix
ResourceCreate SessionGetClick an ElementClose WindowDeleteFill FormGet Live ViewGet ManyQuery Page with PaginationHover on an ElementList WindowsLoadQuery PageRunSave Profile on TerminationSmart ScrapeScrollTake ScreenshotTerminate SessionTypeUploadWait for Download
Agent✓
Extraction✓✓✓
File✓✓✓✓✓
Interaction✓✓✓✓✓
Session✓✓✓✓
Window✓✓✓✓✓✓

Agent

1 operation
01

Run an agent

agent.run

What you see in n8n

Notes & use cases

Calls a published Airtop agent from the workflow instead of assembling the browser steps yourself. The agent does its own navigating, and the node returns what it produced.

Key parameters

  • Agent: a resource locator that lists the agents published on your Airtop account, so you pick one rather than typing an identifier.
  • Agent Parameters: a resource mapper for the agent's own inputs, where each value can come from the incoming item, for example {{ $json.url }}.
  • Await Agent: enabled, the workflow waits for the run to finish; Timeout sets how many seconds it waits.
Use cases
a nightly run that hands an agent a list of prospect pages and collects one structured record per page.

Extraction

3 operations
02

Query page

extraction.query

What you see in n8n

Notes & use cases

Asks a question about what is loaded in a window and answers from the page content, without you writing a single selector.

Key parameters

  • URL: the page to load in the window before the question is asked.
  • Prompt: the question itself, in plain language, such as whether the page contains a login form.
  • Session Mode: Automatically Create Session builds a session and window for this one operation; Use Existing Session reuses the Session ID and Window ID you already have.
  • JSON Output Schema with Parse JSON Output: force the answer into a shape the next node can read field by field.
Use cases
reading a pricing page and returning the plan names and their prices as clean fields.
03

Query page with pagination

extraction.getPaginated

What you see in n8n

Notes & use cases

Collects the same kind of data across a listing that continues beyond the first screen, whether it uses page links or loads more rows as it scrolls.

Key parameters

  • Prompt: what to pull from every page, for instance all product names and prices.
  • Pagination Mode: Auto looks for pagination links first then tries infinite scrolling, Paginated sticks to the links, Infinite Scroll only scrolls.
  • Interaction Mode: Accurate prioritizes accuracy, Cost Efficient minimizes cost, Auto picks between them.
  • URL plus Session ID and Window ID: the listing to open and where to open it.
Use cases
a competitor catalog pulled in one run, then diffed against yesterday's export.
04

Smart scrape page

extraction.scrape

What you see in n8n

Notes & use cases

Returns the window content as markdown. No question, no schema, just the page in a text format that a language model or a document node can read directly.

Key parameters

  • URL: the page to scrape, loaded in the window before the content is captured.
  • Session Mode: create a session on the fly for a one-off page, or reuse an existing Session ID and Window ID when you are already mid-browse.
  • Auto-Terminate Session: disabled, the session stays alive and you terminate it yourself later.
Use cases
turning a documentation site into markdown files stored in Notion for a retrieval index.

File

5 operations
05

Delete a file

file.deleteFile

What you see in n8n

Notes & use cases

Removes an uploaded file from Airtop once the workflow is done with it, which keeps the file list short and predictable for later runs.

Key parameters

  • File ID: the identifier of the file to delete, typically carried over from the upload step as {{ $json.fileId }} rather than typed by hand.
Use cases
a cleanup branch at the end of a workflow that uploads a signed PDF, submits it on a portal, then deletes the copy it no longer needs.
06

Get a file

file.get

What you see in n8n

Notes & use cases

Fetches the details of one uploaded file, and optionally the file itself so the next node receives real bytes instead of metadata.

Key parameters

  • File ID: which file to retrieve, the same identifier the upload or the download wait returned.
  • Output Binary File: enabled, the node outputs the file in binary format when it is ready for download, which is what you want before sending it as an email attachment.
Use cases
picking up an invoice that a supplier portal produced, then attaching it to a message sent through Gmail.
07

Get many files

file.getMany

What you see in n8n

Notes & use cases

Lists the details of several uploaded files at once, which is how you audit what a series of browser runs left behind.

Key parameters

  • Return All: checked, n8n keeps requesting pages until every file is listed; unchecked, Limit caps how many come back.
  • Session IDs: a comma-separated list to filter on; leave it empty and files from all sessions are returned.
  • Output Files in Single Item: one item holding every file, or one item per file for looping.
Use cases
a weekly report counting the documents each scraping session downloaded.
08

Load a file

file.load

What you see in n8n

Notes & use cases

Pushes a file that already exists in Airtop into a live window, so the page's own file input receives it as if someone had picked it from a folder.

Key parameters

  • File ID: the file to load, plus the Session ID to load it into and the Window ID where the file input sits.
  • Element Description: an optional description of the input to interact with, such as the file upload selection box.
  • Include Hidden Elements: useful when the real input is hidden behind a styled button.
Use cases
attaching the same certificate to a form on several supplier portals in one pass.
09

Upload a file

file.upload

What you see in n8n

Notes & use cases

Brings a file into a session, either fetched from a URL or taken from the binary data of a previous node, and optionally opens the file dialog straight away.

Key parameters

  • File Name: the name the file gets in the session; all files loaded into one session should have unique names.
  • Source: URL fetches from the address in URL, Binary reads the Binary Property holding the file data.
  • File Type: Customer Upload is the default, alongside Browser Download, Screenshot and Video.
  • Trigger File Input: disabled, the file only lands in the session without opening any dialog.
Use cases
sending a generated contract straight into an e-signature page.

Interaction

5 operations
10

Click an element

interaction.click

What you see in n8n

Notes & use cases

Describe a button and the operation finds it and clicks it. No CSS selector, no XPath, which matters on sites that rewrite their class names every deploy.

Key parameters

  • Element Description: be specific, the placeholder shows the idea with the green save button at the top of the page.
  • Click Type: Left Click by default, with Double Click and Right Click available.
  • Visual Scope: Viewport analyzes the current view, Page the whole document, Scan handles sites where Page mode struggles.
  • Wait Until Event After Navigation: Fully Loaded is the default, DOM Only Loaded returns faster.
Use cases
accepting a cookie banner before any extraction runs.
11

Fill form

interaction.fill

What you see in n8n

Notes & use cases

Fills several fields in one shot. You describe the values in plain language and the operation maps them onto the form it sees in the window.

Key parameters

  • Form Data: the information to fill in, written as a sentence, for example a name and an email address listed one after the other.
  • Session ID and Window ID: the browser window holding the form, usually the one a previous node opened.
Use cases
a lead captured by a webhook is typed into a partner registration form, with the values built from the incoming item through an expression like {{ $json.email }}.
12

Hover on an element

interaction.hover

What you see in n8n

Notes & use cases

Moves the pointer onto an element you describe, which reveals the menus and tooltips that only exist while the mouse sits on them.

Key parameters

  • Element Description: what to hover on, the placeholder suggests the rounded user profile image at the top right of the page.
  • Visual Scope: Auto covers most pages, Viewport limits the analysis to what is currently displayed.
  • Wait Until Event After Navigation: pick a faster condition when the hover only opens a menu and loads nothing.
Use cases
opening a dropdown navigation menu to reach a sub-page that has no direct link.
13

Scroll on page

interaction.scroll

What you see in n8n

Notes & use cases

Brings content into view, either by describing where to go or by scrolling a set amount toward an edge of the page.

Key parameters

  • Scroll Mode: Automatic scrolls to an element you describe, Manual defines the direction and the amount.
  • Element Description: in Automatic mode, the target in plain language, such as the page section titled Contact Us.
  • Scroll To Edge and Scroll By: when both are set, the edge move runs first and the amount second; Vertically and Horizontally hold the directions.
  • Scrollable Area: scroll inside one element, a left sidebar for instance.
Use cases
reaching a lazy-loaded comment thread before a query.
14

Type text

interaction.type

What you see in n8n

Notes & use cases

Types a string into the window and can press Enter afterwards, which covers search bars and single-field logins in one node.

Key parameters

  • Text: what to type, often built from the incoming item with an expression such as {{ $json.query }}.
  • Element Description: optional here, and worth filling when several inputs share the screen, for example the search box at the top of the page.
  • Press Enter Key: enabled, the search submits without a separate click step.
Use cases
searching a directory for each company name stored in a spreadsheet, one row at a time.

Session

4 operations
15

Create a session

session.create

What you see in n8n

Notes & use cases

Opens the cloud browser and returns a Session ID, the value every other operation asks for. Nothing is required here, so the defaults already give a working session.

Key parameters

  • Profile Name: load or create a named profile so a signed-in state can come back on the next run.
  • Idle Timeout: minutes to wait before inactivity ends the session.
  • Proxy: None, Integrated for the Airtop-provided proxy, or Proxy URL with your own address in Proxy URL; Country picks where it exits.
  • Keep Same IP: holds one address, guaranteed up to 30 minutes.
  • Auto Solve Captchas and Extension IDs: captcha handling, and Chrome extensions in the session.
Use cases
one session per country to compare a landing page market by market.
16

Save a profile on session termination

session.save

What you see in n8n

Notes & use cases

Marks a running session so that when it ends, the browsing state it accumulated, cookies and local storage included, is written into a named profile.

Key parameters

  • Profile Name: the name to save under; it must contain only alphanumeric characters and hyphens, so a space or an underscore will be refused.
  • Session ID: which running session to capture, taken from the create step.
Use cases
logging into a portal once by hand through a live view, saving the profile, then having every scheduled run start already authenticated instead of replaying the login form.
17

Terminate a session

session.terminate

What you see in n8n

Notes & use cases

Ends a session on purpose rather than waiting for inactivity to do it. Sessions close on their own based on the Idle Timeout set at creation, or right here when the workflow decides.

Key parameters

  • Session ID: the session to end, usually the one the workflow opened at the start and carried through every node since.
Use cases
the last node of a branch, placed so it also runs when an earlier step errors, so a long scraping job never leaves a browser open behind it.
18

Wait for a download

session.waitForDownload

What you see in n8n

Notes & use cases

Pauses the workflow until a file triggered inside the session becomes available, then returns its file ID and download URL so the next node has something real to work with.

Key parameters

  • Session ID: the session where the download was started, usually right after a click on an export button.
  • Timeout: time in seconds to wait for the download to become available, worth raising when the site generates the file on demand.
Use cases
a monthly statement exported from a bank portal, collected without anyone watching the spinner.

Window

6 operations
19

Close a window

window.close

What you see in n8n

Notes & use cases

Shuts one browser window while the session keeps running, which is how a multi-tab job frees what it no longer needs without losing its logged-in state.

Key parameters

  • Window ID: the window to close, and Session ID to say which session it belongs to.
Use cases
a comparison workflow that opens one window per supplier page, extracts a price from each, then closes them one by one as the loop advances and keeps only the session for the final summary step.
20

Create a window

window.create

What you see in n8n

Notes & use cases

Adds a browser window inside an existing session and can land on a page straight away, which saves a separate navigation step.

Key parameters

  • URL: the initial page; left empty it defaults to the Google home page.
  • Get Live View: returns the URL of the window's Live View, with Include Navigation Bar to let a human move between pages.
  • Screen Resolution: forces the window size, written like 1280x720, and Disable Resize locks it.
  • Wait Until: Load, DOM Content Loaded, Complete for every iframe, or No Wait to return immediately.
Use cases
opening a mobile-sized window to check a responsive layout.
21

Get live view

window.getLiveView

What you see in n8n

Notes & use cases

Returns information about a window including its live view URL, the address where a person can watch and control the browser in real time.

Key parameters

  • Session ID and Window ID: which window to expose.
  • Include Navigation Bar: shows the bar so the viewer can navigate between pages themselves.
  • Screen Resolution and Disable Resize: fix the size of the view, handy when a screenshot has to match a known layout.
Use cases
posting the live view link to Slack when a run hits a step a human has to unblock.
22

List windows

window.list

What you see in n8n

Notes & use cases

Returns every browser window currently open in a session, which is the quickest way to know what a long run has accumulated.

Key parameters

  • Session ID: the session to inspect, and the only field the operation asks for.
Use cases
a maintenance branch that lists the windows of a session, loops over the result and closes each one before the workflow moves to its reporting step, so a job that opens a window per page does not drift.
23

Load a page

window.load

What you see in n8n

Notes & use cases

Navigates a window that already exists to another address, which keeps the session, the profile and the cookies intact while the page changes.

Key parameters

  • URL: the address to open in that window, often coming from the previous item as {{ $json.url }}.
  • Wait Until: Fully Loaded is the default, DOM Only Loaded returns as soon as the structure is there, Complete waits for every iframe, No Wait returns immediately.
Use cases
walking through a list of URLs in a single authenticated window instead of paying the login cost on each one.
24

Take screenshot

window.takeScreenshot

What you see in n8n

Notes & use cases

Captures what the window currently displays, which gives a workflow visual proof of a step that text alone cannot show.

Key parameters

  • Session ID and Window ID: the window to capture.
  • Output Binary Image: enabled, the image comes out as a binary file ready to be attached or uploaded; disabled, it comes out as a base64 encoded string.
Use cases
archiving the confirmation screen of an order placed by the workflow, alongside the reference stored in ClickUp.
Need help

Need help automating Airtop with n8n?

A person reads every message.

FAQ

Airtop and n8n: common questions

01Is the Airtop n8n integration free?
Yes on the n8n side. The Airtop node ships with n8n, so there is nothing to install and nothing extra to pay to n8n, whether you run n8n Cloud or a self-hosted instance under the Community Edition and its Sustainable Use license. A workflow behaves the same way in both. What an Airtop account itself costs is a separate question and this page does not cover it, so check that with Airtop before you plan a run that keeps sessions open all day. The 24 operations are available in full regardless of how you host n8n.
02What credentials do you need to connect Airtop to n8n?
An API key, and that is the only supported authentication method for this node. Create an Airtop account, log in to the Airtop Portal, open the API Keys page, select the plus Create new key button, name the key, then select the generated key to copy it. Paste that value into the API Key field of an Airtop credential in n8n. The node has no authentication selector, so one credential covers all 24 operations across the 6 resources. Credentials are created once in the Credentials menu and reused in every workflow, and each Airtop node picks one from a dropdown.
03What are the limits of the Airtop node in n8n?
Two things shape what you can build. First, the catalog: the node exposes 24 operations across 6 resources, and anything the Airtop API offers beyond them goes through the HTTP Request node, which calls any endpoint while reusing the same credential through predefined authentication. Second, sessions are stateful. Most operations need a Session ID and a Window ID from earlier nodes, a required field left empty stops the node, and an idle session times out after 10 minutes by default. On listings, Get many files returns everything only with Return All enabled, otherwise Limit caps the result.
04Does Airtop have a trigger node in n8n?
No. Airtop has no trigger node, so nothing in a workflow starts from an Airtop event. You start the workflow another way. A Schedule Trigger runs it at a fixed interval, which fits a nightly scrape or a weekly portal download. An n8n Webhook gives you a URL, meaning an address a third-party service calls, so another tool can kick off a browser run on demand. The trigger of another tool works too, for example a new row in a spreadsheet or a new message in a chat. Airtop nodes then run as actions inside that workflow.
05n8n or Make for Airtop?
It depends on three things. Hosting: n8n runs self-hosted with Docker or npm, or on n8n Cloud, while Make is hosted only. Data control follows from that, and browser automation touches page content and logged-in sessions, which is often the deciding factor here. Cost model: Make bills per operation, and a browser run chains many steps, one to create the session, one per window, one per interaction. Visual logic: both build workflows on a canvas, and the fit depends on how your team already works. No dig at either tool, they solve the same problem with different trade-offs.