# Airtop integrations: sessions, windows and files

> Create a session, create a window and create a file in Airtop. Connect Airtop to the rest of your AI stack with Tray.ai.

**Canonical page:** https://tray.ai/connectors/airtop-integrations/
**Categories:** AI
**Connects through:** HTTP Connector

## Overview

Airtop runs cloud web browsers that AI agents and scripts can control, so they can log in to sites, fill forms, scrape pages and monitor them for changes. Tray.ai connects to Airtop through the HTTP Connector, so your workflows can call the Airtop API alongside the rest of your stack.

## Use cases

### Sessions

Read, create, and manage sessions in Airtop from any Tray.ai workflow. The Airtop API covers calls such as list sessions and create a session.

- List sessions
- Create a session
- Get session info

### Windows

Read, create, update, and manage windows in Airtop from any Tray.ai workflow. The Airtop API covers calls such as create a window and load a URL.

- Create a window
- Load a URL
- Scrape a page

### Files

Read, create, delete, and manage files in Airtop from any Tray.ai workflow. The Airtop API covers calls such as list files and create a file.

- List files
- Create a file
- Get a file

### Automations

Read, update, and delete automations in Airtop from any Tray.ai workflow. The Airtop API covers calls such as list automations and get an automation.

- List automations
- Get an automation
- Update an automation

## Challenges Tray.ai solves

### Keeping Airtop credentials out of logs

A raw API call usually means pasting a key or token into the request, where it ends up in step inputs, logs, and screenshots.

**How Tray.ai helps:** Store Airtop credentials once as a Tray.ai authentication and reference them from the HTTP Connector. Tray.ai masks authentication values in logs, so the secret never shows up in a step's input or output.

### Going from the Airtop API docs to a working call

Translating an example request from API docs into a workflow step means copying the method, URL, headers, and body by hand.

**How Tray.ai helps:** Paste a cURL example from the Airtop API docs into the HTTP Connector and Tray.ai fills in the method, URL, headers, and body for you.

### Handling files and non-JSON responses

Not every API answers in JSON. Some return XML, files, or binary data, or expect a multipart upload.

**How Tray.ai helps:** The HTTP Connector parses JSON and XML responses, returns files you can pass to the next step, and sends multipart form data for uploads.

## Frequently asked questions

### Does Tray.ai connect to Airtop?

Yes. Tray.ai connects to Airtop through the HTTP Connector, which calls the Airtop API directly. Any call the Airtop API documents can run as a step in a Tray.ai workflow.

### How does Tray.ai authenticate with Airtop?

The Airtop API uses a bearer token. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated Airtop connector?

Airtop runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated Airtop connector from the Airtop API.

## Learn more

- Intelligent Integration: https://tray.ai/platform/intelligent-ipaas/
- Merlin Agent Builder: https://tray.ai/platform/merlin-agent-builder/
- Agent Gateway for MCP: https://tray.ai/platform/agent-gateway/
- Book a demo: https://tray.ai/contact/