Content & Documents · Integration
Cloudinary
Add Cloudinary to your product for your customers, and give your AI agents governed access to it.
Embed a Cloudinary integration so your customers can upload and manage media in their own account from inside your product, with usage attributed per tenant. Access runs through each customer's own credentials, so their existing folder structure and transformations apply rather than yours.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers upload images and video from your product into their own account.
Read asset metadata and derived versions so your product can reuse approved media.
Apply named transformations so output matches each customer's conventions.
Trigger your product when an asset is uploaded or replaced.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent finds the right existing asset before assembling content.
An agent uploads a generated asset within governed permissions.
An agent reacts to a new upload and files it against the right record.
Example prompt
List assets uploaded this week over 5 MB and whether a web-optimised version exists.
Set up Cloudinary in 4 steps
- 01Open the Cloudinary connector from your fastn dashboard.
- 02Have each customer supply their Cloudinary credentials.
- 03Map the folders and named transformations your product uses, then enable actions and triggers.
- 04Call them from your product, or expose them to an agent through the MCP server.
Why teams use the Cloudinary integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Cloudinary integration without building it. Your customers connect their own Cloudinary account inside your product and work their files, documents and versions there, with no per-customer code on your side.
- Handle the part that actually costs time: permissions and versioning are easy to get subtly wrong, and mistakes expose content. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Cloudinary update is not your on-call problem.
- One integration serves your product and your agents. The same governed Cloudinary connection powers in-product features and gives AI agents scoped, audited access, so you let your product work with your customers' documents in place without wiring it twice.
Used by these teams
Compare with
Bynder
AWS Simple Storage ServiceWorks well with
CloudConvertOften used alongside
Tools the same teams tend to run next to Cloudinary, across other categories.
Shopify
Stripe
Jira
AsanaCloudinary integration FAQ
How do I add a Cloudinary integration to my product?
Enable the Cloudinary connector in your fastn dashboard, then let each customer authenticate their own Cloudinary account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Cloudinary client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Cloudinary account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Cloudinary account and only ever sees their own files, documents and versions. 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 Cloudinary integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent finds the right existing asset before assembling content.
Who maintains the Cloudinary integration?
fastn does. When Cloudinary 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.
Whose permissions does the Cloudinary integration run under?
Each customer's own Cloudinary grant. Where Cloudinary holds a library, their existing folder and item permissions apply and your product cannot reach content the connected account could not reach itself. Where it processes content you supply rather than storing it, the call runs under that customer's own credentials and is logged per tenant.
Can my product create or update content in Cloudinary automatically?
Where Cloudinary supports writes, documents, entries and assets can be created, updated and filed from your product or by an agent within scoped permissions, with each action logged. Where it is a read surface, the same connection serves reads only.
What can I build with the Cloudinary integration?
A common starting point: upload images and video from your product into their own account. 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 Cloudinary integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Cloudinary does not change your per-connector cost. You can start free with 3 connected accounts.
Add Cloudinary to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.