How to Run AirOps Workflows from a Zapier Trigger

November 20, 2026

AirOps ships a Zapier integration that lets any Zap action start an AirOps workflow with JSON inputs, so a new lead row in your CRM can trigger an outline, a draft and a QA pass without anyone opening the AirOps dashboard. You wire it up in about 20 minutes on the Starter plan or above.

This second workflow angle is different from building the workflow itself. We assume you already have something running inside AirOps and now want an outside event to fire it.

What do you need before connecting AirOps to Zapier?

Four things: a paid AirOps plan (Starter or higher, since the Zapier app is not available on Free), a workflow that has been published at least once, an API token from Settings → API, and a Zapier account on a paid tier if you need multi-step Zaps.

One trap: AirOps only exposes published workflows in the Zapier picker. If your workflow is still in draft, it simply won’t appear in the dropdown and you will spend ten minutes wondering why.

Note the workflow ID too. It appears in the URL when you open the workflow editor (the path is /workflows/<id>) and you need it when you call the API directly instead of through Zapier.

Step 1: Publish the workflow with clean input variables

Before touching Zapier, open your workflow in AirOps and check the input variables. Zapier passes data as a JSON object, and every key you send must match a declared variable exactly — camelCase matters.

A good pattern for a content workflow triggered from a CRM:

  • company_name — text, required
  • target_keyword — text, required
  • tone — dropdown with 3 fixed options, default “professional”
  • word_count — number, default 900

Keep the variable count under eight. Every extra variable is another mapping step in Zapier and another place for a type mismatch. Numbers sent as strings are the most common failure: AirOps will accept "900" but downstream steps that do arithmetic on it break.

Publish the workflow, run it once manually with test values, and confirm the output lands where you expect (Google Sheet, Airtable, or a webhook).

Step 2: Build the Zap that fires the workflow

Create a Zap with your trigger app first — a new row in Google Sheets or HubSpot is the usual choice — then add AirOps as the action and pick Run Workflow.

Connect the AirOps account using the API token from Settings → API. Zapier stores it per connection, so rotating the token later means re-authorising every Zap that uses it.

Then map fields. Zapier shows the workflow’s declared variables as input boxes; pull values from the trigger step. For the example above:

Zapier field Maps from
company_name HubSpot Company Name
target_keyword Sheets column C
tone static “professional”
word_count static 900

Run a test. Zapier sends real data and AirOps starts a real run, which consumes credits. On the Starter plan that is fine — runs are cheap — but do not loop the test twenty times.

Step 3: Handle the async response

AirOps workflows on Zapier are asynchronous by default. The action returns a run ID immediately, not the finished article. Long workflows (research plus outline plus draft) can take two to five minutes.

Two ways to deal with that:

  1. Poll with a second Zap. Trigger on the AirOps “Workflow Completed” event if your plan exposes it, then push the output wherever it belongs.
  2. Push from inside the workflow. Add a final step in AirOps that writes to your sheet or POSTs to a webhook. This avoids Zapier entirely for the return leg and is what most teams end up doing.

Option 2 is more reliable. Zapier’s polling eats task quota and adds lag; a webhook at the end of the workflow fires the moment the last step finishes.

What does a Zapier-triggered AirOps run cost?

AirOps credits are consumed per run, not per Zapier task, and Zapier charges its own task on top. Starter pricing starts around $199/month with a credit allowance that covers a few hundred short runs; heavy workflows with web research burn through it faster.

So each triggered article costs you: one AirOps credit block plus one Zapier task. If you are pushing 200 pieces a month, budget for both line items, and check whether your Zapier plan’s task limit covers the volume before you build.

Who should wire AirOps to Zapier — and who should not

This setup fits teams that already live in Zapier and want content to appear as a side effect of normal CRM or form activity. Marketing ops people with a working Zap library will get it running in under half an hour.

The reverse applies if you need sub-minute turnaround or hundreds of runs per hour. Zapier’s polling interval and task limits get in the way, and the direct AirOps API with your own scheduler is the better path. It is also the wrong choice if your workflows change weekly — every variable rename breaks the Zap mapping silently, and AirOps does not warn you.

A quieter drawback: error handling in Zapier is coarse. If an AirOps run fails mid-workflow, Zapier reports a generic failure and you have to open AirOps to see which step broke.

Quick Summary

  • AirOps connects to Zapier on paid plans only; Free tier has no Zapier app.
  • Only published workflows appear in the Zapier action picker.
  • The Run Workflow action is async — it returns a run ID, not the output.
  • Best practice: end the AirOps workflow with a webhook or sheet write instead of polling.
  • Each run costs AirOps credits plus a Zapier task; 200 runs/month needs both quotas checked.
  • Keep input variables under eight and match key casing exactly.
Tags: