Integrations · MarketingConnect AirOps to Well
Attribute AirOps AI workflow run, input dataset, and owner to revenue in your CRM, with channel and cohort breakdown ready.
What Well pulls from AirOps
AirOps feeds AI workflow run, input dataset, owner into Well as a source. The connection is read-only; disconnect at any time from your workspace settings to revoke AirOps’s access.
| From AirOps | In Well | Relation | |
|---|---|---|---|
| AI workflow run | Execution log | Captures as | |
| Input dataset | Workspace context | Groups under | |
| Owner | Team member | Resolves to |
- Sync mode
- MCP hybrid
- Refresh
- live + reconciliation reads
- Direction
- AirOps → Well
What Well does with your AirOps connection
Connect
Connect AirOps over OAuth (MCP DCR): Well registers a client through AirOps's OAuth Dynamic Client Registration and you approve on AirOps's side, so the password never reaches Well; Well holds only a scoped token it can refresh.
Sync
Well brings AI workflow run, input dataset, and owner in from AirOps on live events backed by periodic reconciliation reads. The first sync backfills history in the background and the connection stays live after.
Enrich
Well resolves each AirOps entity into execution log, workspace context, and team member, assigns categories, and links every record to an audit trail across the rest of your connected tools.
Available
Your data from AirOps lands in the workspace as execution log, workspace context, and team member you can search, chart, and automate.
Questions AirOps unlocks
Ask in plain language. Well answers from your connected AirOps connection, resolved against the rest of your stack.
Ask anything about your AirOps connection
Ask about your AirOps connection…
Connect AirOps in three steps
- 01
Authorise AirOps via MCP
From Well's Connections panel, search for AirOps and click Connect. Well discovers AirOps's MCP OAuth metadata from its .well-known endpoint, registers a client via Dynamic Client Registration, and routes you through the authorize prompt on AirOps's side. No client credentials to paste.
- AuthOAuth (MCP DCR)
- DiscoveryMCP .well-known
- MCP serverapp.airops.com/mcp
- 02
Map your entities
Well's MCP client discovers AI workflow run, input dataset, and owner from AirOps that AirOps's MCP server exposes and brings them into your workspace using the canonical mappings defined in Well's data-views layer. You can inspect the workspace data model from Settings > Data Model.
- Mappingpreconfigured by Well
- 03
Use the data
Ask questions in conversation, build records tables, or let agents act on AirOps records. Because AirOps ships through MCP, Well treats every entity it exposes as queryable graph state alongside the rest of your connected tools.
- First syncstarts as soon as connect completes
MCP handshake typically completes under a minute on warm connections. Resource enumeration runs immediately after; full backfill of historical AirOps records happens in the background.
How AirOps stays secure with Well
Well connects to AirOps's MCP server (app.airops.com/mcp) via the Model Context Protocol. The MCP server itself handles credential issuance through OAuth Dynamic Client Registration; Well never sees a long-lived AirOps secret. Tokens are scoped to the AI workflow run, input dataset, and owner AirOps exposes and refreshed server-side. Reads only, Well cannot modify or delete AirOps records.
- granted
Read AirOps records
Resources the AirOps MCP server exposes, scoped by your OAuth approval.
- granted
Resolve AI workflow run, input dataset, and owner across your stack
Match identifiers in AirOps against the same entities your other connected tools expose, so each record carries cross-tool context.
- refused
Modify or delete AirOps records
Not granted; AirOps is read-only in Well. Write-back is opt-in per connector when a write surface exists.
- refused
Store AirOps passwords or session cookies
Authentication runs through OAuth (MCP DCR) tokens we never see.
Frequently asked questions about AirOps and Well
From Well, open Connections, find AirOps, and click Connect. Well discovers the OAuth metadata at app.airops.com/mcp/.well-known/oauth-authorization-server, registers a client on the fly via Dynamic Client Registration, and walks you through the authorize prompt on AirOps's side. No client_id or client_secret to paste; the handshake takes roughly a minute.
Well brings in AI workflow run, input dataset, and owner from AirOps and reshapes each entity into your workspace: AI workflow run becomes execution log; input dataset becomes workspace context. Every record arrives with the source identifier preserved, so AirOps stays the source of truth while Well lets you query the data alongside the rest of your stack.
Each AirOps campaign carries its spend, audience, and engagement records into Well. Joined to CRM deals and invoiced revenue, "blended CAC for the Q2 LinkedIn push" and "payback by channel" become queryable in conversation. The attribution stops being a separate worksheet.
Each AirOps AI workflow run is scored against the candidate execution logs in your workspace on identifier overlap, amount or quantity match, date proximity, and counterparty resolution. Matches above the auto-link confidence threshold flow through cleanly; below the threshold they queue for a one-click human review, with the most likely execution log prefilled and the AirOps source attached.
Well combines live AirOps events with periodic reconciliation reads of AI workflow run, input dataset, and owner. New rows appear within seconds when AirOps pushes them; periodic reads catch anything a push missed. The first connect backfills history from AirOps in the background.
Open Connections > AirOps in Well and click Disconnect. Well calls AirOps's token revocation endpoint and stops calling AirOps immediately on its side; provider-side propagation to AirOps's admin panel varies by provider. The AI workflow run, input dataset, and owner Well already synced stay in your workspace by default; ask Support to purge them if your compliance flow requires it.
AirOps records are stored in the region Well operates for your workspace. Specific region details and the steps to change region are available from Support. See /privacy for the current data-handling policy.
Pairs well with AirOps
More in Marketing
Bitly
Connect Bitly to Well to sync campaign data and marketing analytics.
Klaviyo
Connect Klaviyo to Well to sync campaign data and marketing analytics.
Supermetrics
Connect Supermetrics to Well to sync campaign data and marketing analytics.
Windsor.ai
Connect Windsor.ai to Well to sync campaign data and marketing analytics.
Popular cross-category
Ready to connect AirOps?
Connect once. Every AI workflow run, input dataset, owner from AirOps becomes searchable, queryable, and ready for your agents and tables. Disconnect any time.