Resources · Zapier integration

AirOps Zapier integrationAutomate AirOps with Zapier.

The AirOps Zapier integration gives you 0 triggers, 2 actions and 1 search. Another app has to start the Zap, then AirOps runs one of your AI workflows, with or without waiting for its output. Here is what each step does, what it costs and where it trips up.

See the 3 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the AirOps Zapier integration actually does

AirOps is where you build AI workflows and chat agents on top of large language models. Connecting it to Zapier means another app can hand it some input and ask it to run one of those workflows, with no copy-paste in between. Zapier calls each of these automations a Zap: one starting event, then one or more steps that run every time that event happens.

Three jobs come up again and again once AirOps sits inside a Zap.

A finished piece of AI output, ready for the next app. With Run AirOps Workflow (Wait for Result), the Zap holds on until the workflow is done and then passes the output to the following step. A brief written in a form can come back as a draft that lands in your docs or your CRM in the same run.

A background job you fire and forget. Run AirOps Workflow launches the workflow and lets the Zap move on. That suits a long enrichment or rewriting job whose result you will read inside AirOps anyway.

A status check on a past run. Get Execution fetches one execution from its UUID, so a later Zap can pick up what an earlier launch produced.

Now the part the app page does not spell out. AirOps exposes no trigger in the editor today. Nothing that happens inside AirOps can start a Zap on its own, so the first step always comes from another tool: a form, a sheet, a CRM, an inbox. There is no step to create, edit or delete a workflow either. You build and fix those in AirOps itself, and Zapier only runs them.

If you are still weighing the platform, start with our Zapier review, then the n8n vs Zapier comparison.

Vocabulary

Zapier vocabulary in one minute

Seven words show up on every screen of the editor. Here they are in plain English.

Trigger
The event in another app that wakes the Zap up. AirOps has none, so here it is a new row, record or form answer elsewhere.
Action
The step the Zap carries out once started. With AirOps, that means launching one of your workflows, waiting or not.
Task
What Zapier counts against your plan: one action that completes. Every AirOps workflow run that succeeds is one task.
Polling vs instant trigger
Polling: Zapier asks the starting app for news on a timer. Instant: that app warns Zapier itself as soon as it happens.
Filter
A gate between steps: the workflow only runs if the incoming item passes your rule, a filled column for example.
Search step
A step that reads something already there. For AirOps, it is the lookup of one past execution from its UUID.
Connection
The link between your AirOps login and Zapier, made once and then offered again in every Zap that runs a workflow.
Cost

What a Zap with AirOps really costs

Zapier bills tasks, not Zaps. AirOps is not a premium app, so it works on the free plan.

  • Free plan100 tasks a month, unlimited Zaps
  • Free plan Zap size2 steps: one trigger, one action
  • Premium appNo, AirOps works on Free
  • Trigger and checks0 tasks

The trigger never costs a task, and neither do the checks Zapier runs looking for new data. Each AirOps action that succeeds counts as one task; a failed run is not billed. The free plan gives you 100 tasks a month but only two-step Zaps: one trigger, one action. Add a filter, a second action or Get Execution and the Zap becomes multi-step, which needs a paid plan. On polling triggers from the other app, the check interval depends on the plan.

Connect

Connect your AirOps account to Zapier

  1. 01

    Open the Apps page

    In your Zapier account, go to Apps and click + Add connection. A dialog opens with a search box. You need an existing AirOps account before you start, since Zapier links to it rather than creating one.

  2. 02

    Pick AirOps and confirm

    Type AirOps in the dialog, select it, then click Add connection. A new tab opens on the AirOps side. That tab is where AirOps asks who you are, so keep it open until the next step is done.

  3. 03

    Sign in and grant access

    Sign in to AirOps in that tab and allow Zapier to reach the account. The connection then appears in your Apps list, and every Zap step that uses AirOps reuses it. Workflows owned by a teammate need access on your side too.

First Zap

Your first Zap: from a sheet row to an AI draft

GoalEach new sheet row with a filled brief column runs an AirOps workflow, and the Zap waits for its output.

  1. 01

    Create the Zap and pick the trigger

    Start a new Zap and choose the app that will feed AirOps. AirOps has no trigger, so the first step always belongs to another tool, here a spreadsheet that receives one row per request.

  2. 02

    Test the trigger on real data

    Run the test: Zapier brings back the three most recent rows of the connected sheet. Pick one with realistic content, since it is the sample you will map into AirOps.

  3. 03

    Skip empty rows

    From the plus icon, add Filter, then set the field (the brief column), the rule and the value. Empty rows stop here. A filter makes the Zap multi-step, so it needs a paid plan.

  4. 04

    Add the AirOps action

    Add a step, choose AirOps and the event Run AirOps Workflow (Wait for Result). Select your connection, fill in the step and map the sheet columns into its fields.

  5. 05

    Test the action

    Test the step once and read what came back. If the output looks right, the mapping holds. If it does not, adjust the mapping and run the test again.

  6. 06

    Publish

    Click Publish to switch the Zap on. From then on, each new row runs the workflow and costs one task. Rows already in the sheet are not processed.

Actions

AirOps actions on Zapier

AirOps gives you 2 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Run AirOps Workflow

Action

In Zapier“Executes an AirOps Workflow”

Starts a workflow in AirOps and hands control back to Zapier at once. The Zap does not wait for the run to end, so the workflow output is not there for the steps that follow.

When to use it
batch jobs whose result you review inside AirOps, such as enriching a list exported from a CRM.
Watch out
later steps cannot map the output; a separate Zap with Get Execution can read the run from its UUID.
2

Run AirOps Workflow (Wait for Result)

Action

In Zapier“Executes an AirOps Workflow and wait for result”

Launches one of your AirOps workflows and keeps the Zap waiting until it finishes, so its output is there for the next step to map into a doc, a message or a record.

When to use it
any Zap where the AI output has to go somewhere else right away, like a draft pushed into your CMS.
Watch out
each successful run is one task, and adding a step after it makes the Zap multi-step.
Searches

AirOps search on Zapier

1 search step looks for data that already exists in AirOps, so a later step can use it.

A search sits at the bottom of the event list, under the SEARCH heading. It reads something that already exists instead of creating it. Three settings decide what happens when the result is not what you expected.

1

Get Execution

Search

In Zapier“Gets an execution by UUID.”

Reads a single AirOps execution from its UUID and returns it to the following steps, which is how a later Zap gets hold of a run it did not launch itself.

When to use it
after a fire-and-forget launch, to read that run again from its UUID once it has had time to finish.
Watch out
the Execution UUID is required, and a search step makes the Zap multi-step, so a paid plan is needed.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on its default, an empty result stops the Zap and skips the steps that relied on it. Switched on, the Zap carries on without data.
  2. Create X if it doesn't exist yet?
    This box turns a search into find-or-create. AirOps offers no such variant for Get Execution, so you will not see it here.
  3. If multiple search results are found?
    Keep the first match (the default), stop the Zap, or pass every match on. With a UUID lookup, one match is the normal case.
When it breaks

When an AirOps Zap breaks

Zapier lists no help article and no rate limit specific to AirOps. What breaks is the general behaviour of Zaps.

Four situations account for most surprises. Each one is easy to avoid once you know it, and the Zapier troubleshooting page is the place to start when one shows up.

  • Past rows are never processed

    A Zap only reacts to what happens after you publish it. Requests already sitting in your sheet or form stay untouched, and moving that backlog is a separate job.

  • The Zap feeds itself in a loop

    If the AirOps output is written back into the same sheet the trigger watches, each write starts the Zap again and burns through your task count fast.

  • A bulk import gets held back

    After a mass import upstream, the trigger can return a huge batch at once. Zapier's flood protection may hold it back instead of running AirOps on every item.

  • Each item counts once

    On a polling trigger Zapier keeps track of what it has already seen, so one sheet row never launches the same AirOps workflow twice or bills a second task.
Need help

Need help automating AirOps with Zapier?

A person reads every message.

FAQ

AirOps Zapier integration: frequent questions

01Is the AirOps Zapier integration free?
Yes, as long as the Zap stays at two steps. AirOps is not a premium app, so it runs on the free plan, which gives 100 tasks a month and an unlimited number of Zaps. The catch is the size of each Zap: the free plan allows one trigger and one action, nothing more. A trigger from another app followed by one AirOps workflow fits. Adding Get Execution, a filter or a second action turns the Zap into a multi-step Zap, and that requires a paid plan. No price is quoted here because the plan grids change too often.
02How many tasks does an AirOps workflow consume?
One task per successful AirOps action. The trigger that starts the Zap costs nothing, and neither do the checks Zapier makes while looking for new data. If the workflow run fails, the action is not counted against your plan. In a Zap with several actions, each one that succeeds is billed on its own, so a Zap that runs AirOps and then writes the result to a doc uses two tasks per run. Keep that in mind when a busy sheet or form feeds the Zap, since every new item means another run.
03Can an AirOps Zap run in real time?
It depends entirely on the app that starts it, because AirOps has no trigger of its own in the editor. If that first app offers an instant trigger, it tells Zapier the moment the event happens and the Zap runs straight away on any plan. If it uses a polling trigger, Zapier checks on a timer: every 15 minutes on Free, every 2 minutes on Professional, every minute on Team and Enterprise. A Zap built on an instant trigger shows a lightning bolt in the editor, which is the quickest way to tell.
04What does it take to connect an AirOps account?
An existing AirOps account and a few clicks in Zapier. Open the Apps page, click + Add connection, search for AirOps, then confirm with Add connection. A new tab opens where you sign in to AirOps and allow Zapier to reach the account. The connection is saved once and reused by every step that touches AirOps. If the workflow you want to run belongs to someone else on your team, make sure your own account has access to it.
05Why does the Get Execution search find nothing?
Usually because the Execution UUID it receives is empty or wrong. That field is required, and the search reads one precise run, so it needs the exact identifier. Map it from the step that launched the workflow or from a record where you stored it. By default, a search that returns nothing stops the Zap and skips the steps after it. If you would rather let the Zap continue without data, switch on the setting Successful if no search results are found. Remember that this search also makes the Zap multi-step.
06What if the AirOps operation you need is not available?
Today the integration offers two ways to run a workflow and one way to read an execution, and nothing else. There is no trigger, so nothing happening in AirOps can start a Zap, and there is no step to create or edit a workflow. The practical route is to put the missing logic inside the AirOps workflow itself and let Zapier only launch it. Anything else, such as reacting to a finished run, stays outside what this integration covers.
07Zapier, Make or n8n for AirOps?
It comes down to criteria rather than a single winner. On Zapier, AirOps works on the free plan, but only two-step Zaps are free and each successful run is a task. Make and n8n bill and structure their automations differently, which matters once you run many workflows or chain several steps around each one. Look at how often your workflows run, how many steps surround them, and who on the team will maintain the automation before choosing.
Same platform

Other docs you might need on this stack.

Browse all integrations