Operator
← All integrations
Figma logo+Google Drive logo

Connect Figma to Google Drive

Automate Figma and Google Drive with AI

Exported assets pile up in Google Drive while the source of truth stays in Figma. Your Operator agent on OpenClaw watches a Figma file for version changes, writes new exports to the Drive folder your team uses, and renames paths when a frame moves to approved. Ask for the logo package on a launch and it finds the Drive folder tied to the Figma component set.

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 Figma and Google Drive

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 →

What your agent does in Google Drive

  • Insert File Parent (v2)

    Tool to add a parent folder for a file using Google Drive API v2. Use when you need to add a file to an additional folder.

  • Insert Property (v2 API)

    Tool to add a property to a file, or update it if it already exists (v2 API). Use when you need to attach custom key-value metadata to a Google Drive file.

  • Copy file with advanced options

    Creates a copy of a file and applies any requested updates with patch semantics. Use when you need to duplicate a file with advanced options like label inclusion, visibility settings, or custom metadata.

  • Create Comment

    Tool to create a comment on a file in Google Drive. Returns a nested `data` object; extract `data.id` for the resulting comment identifier. Omit `anchor` and `quoted_file_content_*` for general file-level comments.

  • Create Shared Drive

    Tool to create a new shared drive. Use when you need to programmatically create a new shared drive for collaboration or storage.

  • Create File or Folder

    Creates a new file or folder in Google Drive. Supports both metadata-only creation (for folders and empty documents) and file upload with content. When file_to_upload is provided, uploads the actual file bytes; otherwise creates an empty...

All 76 Google Drive actions →

How it works

Tell the agent what you want to happen between Figma and Google Drive, for example to watch one and act in the other, or to keep the two in step. It reads what it needs from Figma, works out what to do, and runs the matching action in Google Drive 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 Figma and Google Drive

How do I connect Figma and Google Drive to Operator?
You authorize Figma and Google Drive 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 Figma and Google Drive?
Tell it the job and it moves between Figma and Google Drive as one task, choosing which actions to run on each side. There is nothing to map and no trigger to configure; you give instructions the way you would to a person.
Can my agent keep Figma and Google Drive in sync?
Yes. It can watch Figma and act in Google Drive, 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.

Figma and Google Drive integrations

Put your agent on Figma and Google Drive

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