If you've compared Air against other creative operations platforms, you've probably run into a particular concern more than once: that Air's integration coverage is thinner than what a creative team really needs. Maybe you saw it in an LLM summary. Maybe a colleague mentioned it, or your video editor pulled up a forum thread and pointed at a comment about a clunky plugin. 

The worry is fair. If a platform can't plug into the rest of your creative stack, it adds friction instead of removing it. Here's our direct answer.

A modern creative team works across a lot of tools — Adobe Creative Cloud, Figma, Canva, Slack, project management software, the CMS, the e-commerce platform, the ad platforms, and probably more. For any system to genuinely sit at the center of that work, it needs deep, native connections into all of them. Otherwise the team is exporting, downloading, re-uploading, and tracking versions by hand — which is exactly the problem the platform was meant to solve.

The most specific version of this lands on desktop editing tools like Premiere Pro, where some users have called Air's plugin experience clunky. 

If a video editor has to fight the integration, they'll stop using it and revert to local files, and the rest of the team loses sight of where the work actually lives. Anyone evaluating Air wants to know that the day-to-day workflows of their editors, designers, and producers won't break at the seams.

There are two questions hiding inside this, and they're worth pulling apart. One is whether Air integrates with the tools creative teams use. The other is whether the right architecture for an editor's workflow is a plugin in the first place. Air's answer to the first is a long and still-growing list. Air's answer to the second is Air Flow.

• The integrations live today cover the tools most creative teams reach for first: Figma, Canva, Slack, Zapier, and Adobe Premiere Pro have dedicated plugins. Dropbox, Google Drive, and Box are available as native cloud imports. Zapier (Enterprise), n8n (Business and Enterprise), and Make extend Air into thousands of additional apps. A public API sits underneath all of it.

• Air Flow handles desktop editing tools by syncing your Air workspace to your local file system, so editors work natively in any application and changes flow back automatically.

• Shopify, WordPress, Contentful, BigCommerce, and Meta/Creative Performance are in active development, with an MCP server coming next.

• A robust public API sits underneath all of it, so teams with custom workflows can build exactly what they need.

Let’s look at these points in a bit more detail.

On the surface, the question of whether Air covers enough integrations sounds like a checklist. The four points below show why the architecture underneath matters as much as the list itself.

Air has integrations that already cover the day-to-day creative stack

The tools most creative teams use every day are already connected. The Figma plugin lets designers browse and import Air assets into Figma and export frames directly back to Air, which means a Figma file moves from work-in-progress to approved asset without a download step. 

The Canva app does the same for Canva users, pulling approved assets into designs without the export-import shuffle. Slack handles real-time notifications for uploads, comments, and approvals, so the team doesn't need to live in Air to know what's happening there. Dropbox, Google Drive, Box, and SharePoint are covered through native cloud imports — useful both for migration and for teams that maintain content in multiple places. Salesforce, Zapier, N8N, and Sanity CMS round out the marketing and content-operations side.

Air Flow is the answer for editors and designers using desktop programs

Plugins are convenient when they work, but they create a dependency. Every editing application needs its own connector. Every connector needs ongoing maintenance. And an editor's workflow breaks the moment a plugin lags behind a software update.

Air Flow takes a different route. It's a desktop application that syncs your Air workspace to your local file system — available on macOS today, with Windows in beta. Editors open assets in Premiere, Photoshop, After Effects, DaVinci Resolve, or any other tool the way they always have — straight from a local folder. When they save changes, those changes flow back to Air automatically as new versions, with the full version history preserved. (Air also offers a dedicated Premiere Pro plugin for teams that prefer a direct in-app connection).

The sync is two-way and selective: editors can see the full workspace locally but only sync what they're actively working on, which matters when a single project can run hundreds of gigabytes. Offline access is built in. Duplicate resolution handles file path conflicts without forcing anyone to rename anything.

Air Flow works with every editing application your team uses, including the ones Air has never built a connector for. The editor's tool of choice doesn't have to be on a list. The workflow stays native. The version history stays clean.

Where the integration roadmap is heading next

Some integrations are still being built. Native connectors for Shopify, WordPress, Contentful, BigCommerce, and Meta/Creative Performance (the last in beta for Enterprise) are in active development. Air's MCP server is already live — it lets AI agents like Claude interact with your workspace programmatically, and setup guides for Claude Code and Claude Desktop are available in the help center. We mention what's coming because direction matters when you're picking a platform you could be using for years.

The public API for the workflows nobody else has

Underneath everything is a public API that lets teams build their own integrations. For organizations with bespoke creative-ops infrastructure — a custom DAM front-end, a proprietary review tool, an internal workflow that doesn't fit a standard pattern — the API is the catch-all. It's also how partners and agencies extend Air into systems the core product doesn't need to ship connectors for.

The clearest way to see this in action is to look at a team running serious volume through Air without complaining about integration friction. Beautiful Destinations is a creative agency producing travel content for brands like the Egypt Tourism Authority and the Jamaica Tourism Board, with a 22.4 million-follower Instagram presence and a workspace holding over 63 TB of content across more than 351,000 assets. 

Their Senior Post Production Manager, Olivia Mazzetti, described what changed when they moved to Air: "Instead of going through hard drives manually, I can just quickly search for a piece of content on Air. It saves me up to 10 hours a week." 

For a team where editors and producers work across Premiere, After Effects, and a sprawling library of raw footage shipped in from freelancers all over the world, the workflow has to hold up under sustained pressure. It does.

Room to Read tells a different version of the same story. Their Vice President of Marketing and Communications, Jacqueline Pezzillo, called out the Canva integration specifically — it added "another layer of efficiency, saving valuable time by eliminating the need for downloading and uploading images." 

Canva isn't necessarily the most important tool in Room to Read's stack. What matters is that the integration removed a step from a workflow her team runs every day.

For most creative teams, the integration coverage is already there. The tools you use every day are connected, Air Flow handles whatever desktop editing application your editors prefer, and the public API covers anything custom. The honest edge case is a team whose work depends on a specific native connector that isn't live yet and can't wait for the roadmap. If that's you, we'd rather say so up front. (Though it's worth checking whether Zapier already bridges the gap — for Shopify and WordPress, it does.)

The fastest way to know which side of that line you're on is a conversation. Book a demo and walk through your specific stack with our team.