Airtop Zapier integrationAutomate Airtop with Zapier.
The Airtop Zapier integration gives you 1 action, 0 triggers and 0 searches: Zapier can launch one of your Airtop agents, but Airtop never starts a Zap by itself. Here is how to wire it, what it costs, and where it trips people up.
Verified Trustpilot reviews · AI, automation & growth agency
What the Airtop Zapier integration actually does
Airtop is a service where you describe a web automation in plain words and an agent carries it out. The Zapier side is narrow on purpose: one action, Run an Airtop Agent, which launches one of your agents with the input values your Zap passes along. Nothing else.
Three results people usually get out of it. First, a research run per new record: a new row lands somewhere, and an agent runs on the values of that row. Second, a filled-in result in the next step: with the agent awaited, whatever it returns can be mapped into a later step of the same Zap. Third, a fire-and-forget job: the Zap only kicks the agent off, gets back an invocation ID, and moves on while the agent works on its own.
What Zapier does not do here matters just as much. Airtop has no trigger on Zapier, so nothing that happens inside Airtop can start a Zap: the starting event always comes from another app. There is no search either, so a Zap cannot look up an earlier agent run. And no action creates or edits an agent: the Zap can only launch one.
If you would rather compare the same tool on other platforms, the Airtop n8n integration and the Airtop Make integration cover the same ground with their own logic.
Zapier vocabulary in one minute
Seven words you will meet on the next screens. Once explained here, they are used as is.
- Zap
- The automation you put together on Zapier: one trigger first, then one or more actions that run each time the trigger event happens.
- Trigger
- The event in an app that starts the Zap. With Airtop, it always belongs to another app, since Airtop offers none.
- Action
- What the Zap does once it has started. Here, the one action is launching an Airtop agent with the inputs you map.
- Task
- The unit Zapier bills: one action that your Zap completes successfully. Your plan is a monthly count of those.
- Polling or instant
- A polling trigger is checked on a timer set by your plan; an instant one is reported by the app as soon as the event happens.
- Filter
- A step that lets the Zap go on only when what arrived meets your condition. It turns the Zap into a multi-step one.
- Connection
- Your Airtop account linked to Zapier once, then reused by every step that talks to Airtop, in any Zap you build.
What an Airtop Zap really costs
The billing logic is short, and most people get one part of it wrong.
- Free plan100 tasks a month, unlimited Zaps
- Steps on freeTwo: one trigger, one action
- Premium appNo, Airtop works on the free plan
- Failed actionNot counted against your plan
The trigger never costs a task, and neither does Zapier checking for new data, however often it looks. Each run of Run an Airtop Agent that goes through counts as one task; a run that fails is not counted. Add a second action, a filter or a search and the Zap becomes multi-step, which the free plan does not allow: it stops at one trigger and one action. Airtop is not a premium app, so it works from the free plan.
Connect your Airtop account to Zapier
- 01
Open the Apps page
In your Zapier account, go to Apps and click + Add connection. A dialog opens. Type Airtop in the search box and pick it from the results. You need an Airtop account before this step.
- 02
Sign in to Airtop
Click Add connection. A new tab opens on the Airtop side: sign in with the Airtop account whose agents the Zap should run. If some of those agents are not yours, that account needs access to them.
- 03
Grant access and come back
Grant Zapier access to the account. That is the whole connection: your Airtop account linked once, then reused by every Zap step that uses Airtop instead of asking you again.
Your first Airtop Zap, step by step
GoalEach new row in a sheet launches an Airtop agent, and only rows marked as ready go through.
- 01
Create the Zap and pick the trigger
Start a new Zap. Since Airtop has no trigger, the first step comes from the app where your work starts, here a sheet where a new row means a new job for the agent.
- 02
Test the trigger on real data
Run the trigger test. Zapier brings back the three most recent rows of the connected account, so you pick a real one and map real values in the next steps instead of guessing.
- 03
Add a filter if you need one
A filter keeps half-filled rows from launching the agent. Keep in mind it makes the Zap multi-step, so it needs a paid plan. On free, skip it and go straight to the action.
- 04
Add Run an Airtop Agent
Add the action, choose Airtop, then Run an Airtop Agent. Pick your connection, map the row values into its inputs, and set Await Agent Result.
- 05
Test, then publish
Test the action once and read what came back: a result if you waited, an invocation ID if you did not. When it looks right, publish the Zap to switch it on.
The Airtop action on Zapier
Airtop gives you 1 action. For each one: what it does for you, when to reach for it, and what to watch out for.
Run an Airtop Agent
ActionIn Zapier“Runs a Airtop agent with the given input parameters. Can be used to run agents both asynchronously and synchronously.”
Launches one of your Airtop agents and feeds it the input values your Zap carries from the trigger. It can wait for the agent's result or hand back right away.
When an Airtop Zap breaks
Zapier attaches no help article to Airtop, so the traps below are the general ones of any Zap, seen from this action.
Most broken Airtop Zaps fail for reasons that have nothing to do with Airtop itself. They come from what the trigger app sends, or from what people expect a Zap to do with the past. Check these four before suspecting the agent. The Zapier troubleshooting page goes further on the generic cases.
Old records are never processed
A Zap only reacts to what happens after you switch it on. Rows that were already in the sheet will not launch the agent; moving that backlog is a separate job.The Zap keeps restarting itself
If the agent's result is written back into the very place your trigger watches, each write starts the Zap again, and the task count drains fast.A bulk import gets held back
When the trigger suddenly returns a huge batch, after an import or a migration, Zapier's flood protection can hold the runs back instead of launching every agent.The next step finds nothing to map
With Await Agent Result off, the action hands back an invocation ID only. Steps placed after it cannot use the agent's answer, because it does not exist yet.
Need help automating Airtop with Zapier?
A person reads every message.
