Workflow & Automation · Integration
AirOps
Add AirOps to your product for your customers, and give your AI agents governed access to it.
AirOps runs are triggered against a published app, and the publish step is a hard requirement: an unpublished app cannot be executed at all, which is the usual reason a working draft returns nothing through the API. The base is https://api.airops.com/public_api with a bearer token, and you choose between POST /airops_apps/{uuid}/execute, which runs inline but is capped at ten minutes, and /async_execute, which returns an execution uuid you then poll at /airops_apps/executions/{uuid}. The execution object is richer than a simple status flag, carrying inputs, outputs, runtime in seconds, credits_used and a status that includes review_needed as well as pending, running, success, error and cancelled, so a run can finish without being done. Cancel and retry are separate calls on the execution rather than parameters on the run, and there is a feedback call for rating a successful execution. fastn holds each customer's AirOps key, manages the polling, and keeps the connection working as keys are rotated.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own AirOps workspace so workflow runs draw on their credits and their published apps
Kick off an async workflow when a record changes in your product and store the returned execution uuid against it
Show run history for an app with runtime and credits used so customers can see what a workflow costs them
Expose cancel and retry in your UI for long running executions instead of sending customers back to AirOps
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Let an agent execute a named published app with supplied inputs and return the outputs once the execution succeeds
Have an agent check an execution that came back as review_needed and explain what is waiting on a human
Audit per tenant which apps an agent executed and the credits each run consumed, since spend lands on the customer's workspace
Example prompt
Run the content brief workflow for this keyword and tell me how many credits it used.
Set up AirOps in 4 steps
- 01Enable the AirOps connector from your fastn dashboard.
- 02Have each customer authorise their own AirOps account, so calls run under their credentials rather than a shared key.
- 03Decide which processes, runs and queues your product needs, map those fields, then enable the actions and triggers you want.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the AirOps integration
What you get by embedding it with fastn instead of building it yourself.
- Ship an AirOps integration without building it. Your customers connect their own AirOps account inside your product and work their processes, runs and queues there, with no per-customer code on your side.
- Handle the part that actually costs time: runs are asynchronous and can fail long after they are accepted, so an outcome that never arrives must look different from one that succeeded. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so an AirOps update is not your on-call problem.
- One integration serves your product and your agents. The same governed AirOps connection powers in-product features and gives AI agents scoped, audited access, so you start work in the automation platform your customers already run, and get the outcome back without wiring it twice.
Used by these teams
Compare with
Ansible
Automation Anywhere
Microsoft Power AutomateOften used alongside
Tools the same teams tend to run next to AirOps, across other categories.
Amazon SES
Resend
Mailgun
PostmarkAirOps integration FAQ
How do I add an AirOps integration to my product?
Enable the AirOps connector in your fastn dashboard, then let each customer authenticate their own AirOps account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no AirOps client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own AirOps account?
Yes. Every connection is scoped to the individual customer, so each authorises their own AirOps account and only ever sees their own processes, runs and queues. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this AirOps integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. Let an agent execute a named published app with supplied inputs and return the outputs once the execution succeeds
Who maintains the AirOps integration?
fastn does. When AirOps changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Can my product start an AirOps run and read its outcome?
Yes. Your product can trigger a process in the customer's own AirOps account, pass it input, and take the result back as an event rather than polling for it.
What happens when an AirOps run is slow or fails?
The failure surfaces with its error rather than as a silent timeout, and the run keeps its own identifier so a retry can be matched to the original. That matters more here than in most integrations, because a run that half-completed is not the same as one that never started.
What can I build with the AirOps integration?
A common starting point: let a customer connect their own AirOps workspace so workflow runs draw on their credits and their published apps. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the AirOps integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding AirOps does not change your per-connector cost. You can start free with 3 connected accounts.
Add AirOps to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.