> ## Documentation Index
> Fetch the complete documentation index at: https://docs.atako.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Figma

> Connect Figma to your Atako agents — 25 read and 10 write actions.

Let your agents work with your Figma files — read documents, export images, manage comments, dev resources and library assets.

## Connection

* **Authentication**: API key (Personal access token (figd\_...)).

<Note>
  Figma → click your avatar (top left) → Settings → Security tab → Personal access tokens → Generate new token. Name it, pick an expiration, and grant the scopes you need (at minimum "File content: Read-only"; add "Comments: Write", "Dev resources: Write" or "Webhooks: Write" for those actions), then copy the token (starts with figd\_).

  See [Figma's documentation](https://help.figma.com/hc/en-us/articles/8085703771159-Manage-personal-access-tokens).
</Note>

## Read actions (25)

| Action | Description |
| - | - |
| `get_component` | Fetch metadata of a published component by its key. |
| `get_component_set` | Fetch metadata of a published component set by its key. |
| `get_current_user` | Fetch the profile of the user who owns the access token. |
| `get_file` | Fetch a Figma file as a JSON document tree (optionally scoped to nodes or a version). |
| `get_file_component_sets` | List the component sets published from a file. |
| `get_file_components` | List the components published from a file. |
| `get_file_metadata` | Fetch lightweight metadata for a file (name, last modified, editor type) without the document tree. |
| `get_file_nodes` | Fetch specific nodes of a file by their node IDs. |
| `get_file_styles` | List the styles published from a file. |
| `get_image_fills` | Fetch download URLs for all user-uploaded images used as fills in a file. |
| `get_local_variables` | Fetch the local and remote design variables used in a file (Enterprise plan). |
| `get_published_variables` | Fetch the design variables published from a main file (Enterprise plan). |
| `get_style` | Fetch metadata of a published style by its key. |
| `get_webhook` | Fetch a webhook by its ID. |
| `list_comment_reactions` | List the emoji reactions on a comment. |
| `list_comments` | List all comments left on a file. |
| `list_dev_resources` | List the dev resources (linked URLs) attached to a file. |
| `list_file_versions` | List the version history of a file. |
| `list_project_files` | List the files inside a project. |
| `list_team_component_sets` | List the published component sets of a team library. |
| `list_team_components` | List the published components of a team library. |
| `list_team_projects` | List the projects of a team visible to the token owner. |
| `list_team_styles` | List the published styles of a team library. |
| `list_webhooks` | List webhooks for a team, project, file context or a whole plan. |
| `render_images` | Export rendered images (PNG/JPG/SVG/PDF) of file nodes and get temporary download URLs. |

## Write actions (10)

| Action | Description |
| - | - |
| `create_comment` | Post a comment on a file, optionally as a reply or pinned to a position/node. |
| `create_comment_reaction` | Add an emoji reaction to a comment. |
| `create_dev_resources` | Attach one or more dev resource links to nodes in files. |
| `create_webhook` | Create a webhook that calls an endpoint when a file/team/project event triggers. |
| `delete_comment` | Delete a comment you authored on a file. |
| `delete_comment_reaction` | Remove your emoji reaction from a comment. |
| `delete_dev_resource` | Delete a dev resource from a file. |
| `delete_webhook` | Delete a webhook. |
| `update_dev_resources` | Update the name or URL of existing dev resources. |
| `update_webhook` | Update the event type, endpoint, passcode, status or description of a webhook. |

## Permissions

Every action above must be explicitly granted to an agent before it can be used. See [Permissions](/integrations/permissions) for the grant model and [Security](/integrations/security) for how credentials are protected.

***

*Last reviewed against the provider API: July 2026.*


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.