A collaborative interface design tool.
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.
Posts a specified emoji reaction to an existing comment in a Figma file or branch, requiring valid file_key and comment_id.
Creates a Figma webhook for team, project, or file events, sending POST notifications to the configured endpoint. Team webhooks require team admin permissions; project and file webhooks require edit access.
Creates and attaches multiple uniquely-URLed development resources to specified Figma nodes, up to 10 per node.
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 `resolvedType`.
Deletes a specific comment from a Figma file or branch, provided the authenticated user is the original author of the comment.
Deletes a specific emoji reaction from a comment in a Figma file; the user must have originally created the reaction.
Permanently deletes an existing webhook, identified by its unique `webhook_id`; this operation is irreversible.
Deletes a development resource (used to link Figma design elements to external developer information like code or tasks) from a specified Figma file.
Converts design tokens into Tailwind CSS configuration content with theme extensions, and optionally generates global CSS with font imports.
Detect background layers for selected nodes in a Figma file. This action analyzes the Figma document structure and identifies potential background elements for the given target nodes. It uses: - Geometric analysis (bounding box overlap/containment) - Z-index ordering (nodes earlier in the layer stack are behind later ones) - Visual properties (fills, node types) - Naming conventions (nodes named 'background', 'bg', etc.) Returns background candidates with confidence scores (0-1) and explanations.
Discovers Figma identifiers from supported file, design, board, prototype, slides, team and project URLs, and can list team projects, project files or file nodes. Project and file listing failures may appear as empty results.
Download images from Figma file nodes. Renders specified nodes as images and downloads them. Supports PNG, SVG, JPG, and PDF formats. REQUIRED PARAMETERS: - file_key (string): The Figma file key from the URL - images (array): List of objects, each containing: - node_id (string, required): The node ID to export (e.g., "1:2") - file_name (string, required): Output filename with extension (e.g., "logo.png") - format (string, optional): One of 'png', 'svg', 'jpg', 'pdf'. Defaults to 'png' Example usage: { "file_key": "abc123XYZ", "images": [ {"node_id": "1:2", "file_name": "logo.png", "format": "png"} ] } To find node IDs, use FIGMA_GET_FILE_JSON or look in Figma URLs after 'node-id='. NOTE: Returned image URLs expire shortly after generation — download them immediately.
Extracts design tokens from a Figma file using styles, optional variables and node properties. Results may be incomplete or use fallback style values; variables require appropriate access and a supported plan.
Extract prototype interactions and animations from Figma files. Required parameter: - file_key: The Figma file key extracted from a URL like 'https://www.figma.com/file/ABC123xyz/MyFile' (the 'ABC123xyz' part) Analyzes the prototype data to extract: - User interactions (clicks, hovers, etc.) - Transition animations - Component variant states - User flows and navigation
Retrieves detailed information about a specific webhook by its ID, provided the webhook exists and is accessible to the user.
Retrieves Figma organization activity log events with event-type and time-range filters, ordering, and a page-size limit. Access requires an OAuth app and an Enterprise organization admin with the activity log scope.
Retrieves all comments from an existing Figma file, identified by a valid `file_key`, returning details like content, author, position, and reactions, with an option for Markdown formatted content.
Fetches metadata for a specific component using its unique identifier. Use when you need to retrieve published component details from a team library.
DEPRECATED: Use FIGMA_GET_FILE_NODES instead. Get component data with automatic simplification. Returns clean, AI-friendly component structure.
Retrieves detailed metadata for a specific published Figma component set using its unique `key`.
Retrieves detailed information for the currently authenticated Figma user.
Retrieves development resources (e.g., Jira/GitHub links) for a Figma main file, optionally filtering by specific node IDs.
Retrieves all published component sets from the specified Figma main file (file_key must not be for a branch).
Retrieves published components from a Figma file, which must be a main file (not a branch) acting as a library.
Retrieves data for a Figma Design file or selected nodes, with options to specify a version and limit tree depth. By default it returns a simplified view that omits invisible nodes and empty values; choose full detail for the raw Figma response. Use node IDs and depth to reduce response size for large files.
Get Figma file metadata including name, creator, last modification details, thumbnail, and access information. Use when you need quick file overview without the full document tree.
Fetch JSON for specific node IDs from a Figma file to avoid full-file payload limits. Use when you already know target node IDs (from shallow file fetch or component listings) or when full-file JSON has hit payload limits. Prefer depth=1 for fast discovery.
Retrieves a list of published styles (like colors, text attributes, effects, and layout grids) from a specified main Figma file (not a branch).
Lists files in a Figma project, optionally including metadata for branches of main files. DEPRECATED: Figma recommends the folders endpoint GET /v2/folders/:folder_id/files instead; existing integrations are unaffected.
Retrieves temporary (14-day expiry) download URLs for all image fills in a Figma file; requires `imageRef` from `Paint` objects to map URLs.
Retrieves component insertion and detachment analytics for a specified Figma library, groupable by 'component' or 'team' and filterable by a date range (YYYY-MM-DD).
Retrieves component usage analytics for a specified Figma library file (identified by `file_key`), with data groupable by 'component' or 'file'.
Retrieves style usage analytics (insertions, detachments) for a Figma library, grouped by 'style' or 'team'; if providing a date range, ensure end_date is not before start_date.
Retrieves style usage analytics for a published Figma library. Returns data about how styles (colors, text styles, effects, grids) from the library are being used across your organization. Requires Enterprise plan and library_analytics:read scope. Group results by 'style' to see per-style metrics or by 'file' to see which files use the library's styles.
Retrieves weekly, paginated analytics data on variable insertions and detachments for a specified Figma library (identified by `file_key`), groupable by 'variable' or 'team', and filterable by an optional date range. Note: Requires Enterprise plan and library_analytics:read scope.
Retrieves paginated analytics data on variable usage from a specified Figma library, grouped by 'file' or 'variable', for libraries with enabled analytics.
Retrieves all local/remote variables for a Figma file/branch; crucial for obtaining mode-specific values which `/v1/files/{file_key}/variables/published` omits.
Retrieves a user's payment information for a Figma plugin, widget, or Community file; the authenticated identity must own the resource.
Retrieves projects (folders) visible to the authenticated user in a specified Figma team. On plans with nested folders enabled, results include only top-level folders.
Retrieves variables published from a specified Figma file; this API is available only to full members of Enterprise organizations.
Retrieves reactions for a specific comment in a Figma file.
Get Figma's SCIM service provider configuration. Returns configuration details including which SCIM operations are supported (patch, bulk, filter, etc.), authentication schemes, and service capabilities.
Retrieves detailed metadata for a specific style in Figma using its unique style key.
Retrieves a paginated list of published component sets (collections of reusable UI elements) from a specified Figma team's library.
Retrieves components published in a specific Figma team's library; the team must have published components, otherwise an empty list is returned.
Retrieves a paginated list of published styles (fill colors, text styles, effects, grids) from a specified Figma team's library. Note: The team must have published styles in its library for this endpoint to return data. Teams without published styles will return an empty list.
Retrieves the version history for a Figma file or branch, as specified by its `file_key`.
Retrieves a history of webhook requests for a specific Figma webhook subscription; data is available for requests sent within the last seven days.
Retrieves webhooks registered for a specified Figma team, project, or file context using the Webhooks V2 API.
Render Figma nodes as images (PNG, JPG, SVG, PDF). Returns a map of node IDs to temporary image URLs (valid for 30 days). Images are capped at 32 megapixels; larger requests are automatically scaled down. REQUIRED PARAMETERS: - file_key: Figma file key from URL (e.g., 'abc123XYZ' from figma.com/design/abc123XYZ/...) - ids: Comma-separated node IDs to render (e.g., '1:2' or '1:2,1:3,1:4') NODE IDs: Found in Figma URLs after 'node-id=' or from FIGMA_GET_FILE_JSON response. FORMATS: - png/jpg: Raster images with optional scale (0.01-4.0) - svg: Vector graphics with text outline options - pdf: Document format COMMON ISSUES: - null value in images map = node failed to render (invalid ID, invisible, 0% opacity) - 404 error = file_key not found or no access - 429 error = rate limit exceeded, wait and retry
Updates an existing Figma webhook, identified by `webhook_id`, allowing modification of its event type, endpoint, passcode, status, or description.
Updates the name and/or URL of one or more existing Figma Dev Resources, each identified by its unique `id`.
The Figma integration connects your Dench AI CRM directly to Figma, so agents can read and act on your Figma data as part of everyday work — answering questions in chat, keeping your CRM in sync, and running automations without anyone copying data between tools.
53 actions are available for agents to invoke on your behalf. Every call runs through Figma's own authorization, scoped to the account you connect.
Sign in to your Dench workspace and open Integrations.
Find Figma and click Connect — you'll authorize access through Figma's own sign-in flow. No API keys or code required.
Ask an agent to use Figma in chat, or call it from an automation.
Manage or disconnect the connection any time from workspace settings.
The Dench Figma integration connects your AI CRM to Figma, so AI agents can work with your Figma data as part of chats, automations, and CRM workflows. You connect your account once, and every agent in your workspace can use it — governed by your workspace permissions.
The Figma integration currently exposes 53 actions, including Add a comment to a file, Add a reaction to a comment, Create a webhook, Create dev resources, Create, modify, or delete variables, and Delete a comment. Agents invoke them on your behalf from chat or from automations.
No. You connect Figma from your Dench workspace using Figma's own sign-in and authorization flow — no API keys to copy, no glue code to maintain.
Connections are authorized through Figma's own authentication flow, and Dench stores only the authorization needed to act on your behalf. You can review and disconnect the Figma connection from your workspace settings at any time.