Operator
← All integrations
Cloudinary logo+Figma logo

Connect Cloudinary to Figma

Automate Cloudinary and Figma with AI

Designs approved in Figma still need optimized assets in Cloudinary before they ship on the site. Your Operator agent on OpenClaw exports the frames you name, uploads them to the right Cloudinary folder with the transformations your stack expects, and returns delivery URLs you can paste into a handoff doc or ticket. Ask for every asset tied to a Figma page and it lists the Cloudinary public IDs and live links.

It reaches both apps directly or through connectors like Composio MCP and Pipedream MCP, which handle the sign in and token refresh, so there is no Zap to build and no API keys to paste.

What your agent can do with Cloudinary and Figma

What your agent does in Cloudinary

  • Activate Live Stream

    Tool to manually activate a Cloudinary live stream. Use when you need to start a live stream that is in an inactive state.

  • Create Asset Relations by Asset ID

    Tool to add related assets by asset ID. Use when you need to create relationships between assets in Cloudinary. Can relate up to 10 assets at once to a source asset.

  • Create Asset Relations by Public ID

    Tool to create relations between assets by public ID. Use when you need to link related assets together (e.g., linking subtitles to videos, or associating images with each other). Each request can relate up to 10 assets to the primary as...

  • Create Folder

    Tool to create a new asset folder. Use when you need to organize assets into nested directories. Use after confirming the folder path does not already exist.

  • Create Image from Text

    Tool to create an image from text using Cloudinary's text generation API. Use when you need to generate custom text images with specific styling options. The generated image can be customized with font, color, alignment, and other visual...

  • Create Live Stream

    Tool to create a new live stream in Cloudinary. Use when you need to set up a new live streaming session. The created stream will provide connection details (URI and stream key) for pushing live content.

All 108 Cloudinary actions →

What your agent does in Figma

  • Add a comment to a file

    Posts a new comment to a Figma file or branch, optionally replying to an existing root comment (replies cannot be nested); `region_height` and `region_width` in `client_meta` must be positive if defining a comment region.

  • Add a reaction to a comment

    Posts a specified emoji reaction to an existing comment in a Figma file or branch, requiring valid file_key and comment_id.

  • Create a webhook

    Creates a Figma webhook to receive POST notifications when specific events occur. Webhooks can monitor events at three scopes: - Team level: monitors all files in a team (requires team admin permissions) - Project level: monitors all fil...

  • Create dev resources

    Creates and attaches multiple uniquely-URLed development resources to specified Figma nodes, up to 10 per node.

  • Create, modify, or delete variables

    Manages variables, collections, modes, and their values in a Figma file via batch create/update/delete operations; use temporary IDs to link new related items in one request and ensure `variableModeValues` match the target variable's `re...

  • Delete a comment

    Deletes a specific comment from a Figma file or branch, provided the authenticated user is the original author of the comment.

All 52 Figma actions →

How it works

Tell the agent what you want to happen between Cloudinary and Figma, for example to watch one and act in the other, or to keep the two in step. It reads what it needs from Cloudinary, works out what to do, and runs the matching action in Figma without you mapping a single field.

You can have it run once, on a schedule, or whenever something changes. Ask it for a status any time and it reads the latest from both apps back to you in the same chat.

Common questions about Cloudinary and Figma

How do I connect Cloudinary and Figma to Operator?
You authorize Cloudinary and Figma once each from your Operator dashboard. Operator holds both connections and refreshes the access tokens for you, so your agent keeps working across them without you signing in again.
What can my agent do across Cloudinary and Figma?
You describe the outcome in plain language and your agent works between the two, reading from one and acting in the other. It picks the right Cloudinary and Figma actions on its own, so you do not map fields or pick triggers.
Can my agent keep Cloudinary and Figma in sync?
Yes. It can watch Cloudinary and act in Figma, or keep both in step, reading from one and running the matching update in the other. This runs on demand when you ask or on a schedule you set.
Do I need to build a workflow or write code?
No. There is no workflow to build, no fields to map, and no API keys to paste. Operator manages both connections, and you give the agent instructions in plain language.

Cloudinary and Figma integrations

Put your agent on Cloudinary and Figma

Sign in, connect both apps, and hand your agent the work. The same setup reaches every app in the catalog. Your first week is free.

Try for free