All connectors

Figma

52 tools Images & Design Team Collaboration

A collaborative interface design tool.

Open in SlashspaceDownload for Mac

Connect Figma

  1. Open Slashspace and go to Settings, then Connectors.
  2. On Discover, search for Figma and click Connect.
  3. Sign in to Figma in your browser. Slashspace updates when the account is connected.
  4. Then ask for what you need in any Agent mode chat. Figma is on in every chat unless you switch it off.

What your chats can do

52 tools from Figma.

  • Add a comment to a filePosts 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 commentPosts a specified emoji reaction to an existing comment in a Figma file or branch, requiring valid file_key and comment_id.
  • Create a webhookCreates 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.
  • Create dev resourcesCreates and attaches multiple uniquely-URLed development resources to specified Figma nodes, up to 10 per node.
  • Create, modify, or delete variablesManages 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`.
  • Delete a commentDeletes a specific comment from a Figma file or branch, provided the authenticated user is the original author of the comment.
  • Delete a reactionDeletes a specific emoji reaction from a comment in a Figma file; the user must have originally created the reaction.
  • Delete a webhookPermanently deletes an existing webhook, identified by its unique `webhook_id`; this operation is irreversible.
  • Delete dev resourceDeletes a development resource (used to link Figma design elements to external developer information like code or tasks) from a specified Figma file.
  • Design tokens to tailwindConverts design tokens into Tailwind CSS configuration content with theme extensions, and optionally generates global CSS with font imports.
  • Detect Background LayersDetect 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.
  • Discover Figma ResourcesDiscovers 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 Figma ImagesDownload 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.
  • Extract design tokensExtracts 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 InteractionsExtract 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
  • Get activity logsRetrieves 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.
  • Get a webhookRetrieves detailed information about a specific webhook by its ID, provided the webhook exists and is accessible to the user.
  • Get comments in a fileRetrieves 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.
  • Get componentFetches metadata for a specific component using its unique identifier. Use when you need to retrieve published component details from a team library.
  • Get component setRetrieves detailed metadata for a specific published Figma component set using its unique `key`.
  • Get current userRetrieves detailed information for the currently authenticated Figma user.
  • Get dev resourcesRetrieves development resources (e.g., Jira/GitHub links) for a Figma main file, optionally filtering by specific node IDs.
  • Get file componentsRetrieves published components from a Figma file, which must be a main file (not a branch) acting as a library.
  • Get file component setsRetrieves all published component sets from the specified Figma main file (file_key must not be for a branch).
  • Get file jsonRetrieves 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 file metadataGet 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.
  • Get file nodesFetch 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.
  • Get files in a projectLists 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.
  • Get file stylesRetrieves a list of published styles (like colors, text attributes, effects, and layout grids) from a specified main Figma file (not a branch).
  • Get image fillsRetrieves temporary (14-day expiry) download URLs for all image fills in a Figma file; requires `imageRef` from `Paint` objects to map URLs.
  • Get library analytics component action dataRetrieves component insertion and detachment analytics for a specified Figma library, groupable by 'component' or 'team' and filterable by a date range (YYYY-MM-DD).
  • Get library analytics component usage dataRetrieves component usage analytics for a specified Figma library file (identified by `file_key`), with data groupable by 'component' or 'file'.
  • Get library analytics style action dataRetrieves 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.
  • Get library analytics style usage dataRetrieves 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.
  • Get library analytics variable action dataRetrieves 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.
  • Get library analytics variable usage dataRetrieves paginated analytics data on variable usage from a specified Figma library, grouped by 'file' or 'variable', for libraries with enabled analytics.
  • Get local variablesRetrieves all local/remote variables for a Figma file/branch; crucial for obtaining mode-specific values which `/v1/files/{file_key}/variables/published` omits.
  • Get paymentsRetrieves a user's payment information for a Figma plugin, widget, or Community file; the authenticated identity must own the resource.
  • Get projects in a teamRetrieves projects (folders) visible to the authenticated user in a specified Figma team. On plans with nested folders enabled, results include only top-level folders.
  • Get published variablesRetrieves variables published from a specified Figma file; this API is available only to full members of Enterprise organizations.
  • Get reactions for a commentRetrieves reactions for a specific comment in a Figma file.
  • Get SCIM service provider configGet Figma's SCIM service provider configuration. Returns configuration details including which SCIM operations are supported (patch, bulk, filter, etc.), authentication schemes, and service capabilities.
  • Get styleRetrieves detailed metadata for a specific style in Figma using its unique style key.
  • Get team componentsRetrieves components published in a specific Figma team's library; the team must have published components, otherwise an empty list is returned.
  • Get team component setsRetrieves a paginated list of published component sets (collections of reusable UI elements) from a specified Figma team's library.
  • Get team stylesRetrieves 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.
  • Get webhooksRetrieves webhooks registered for a specified Figma team, project, or file context using the Webhooks V2 API.
  • Get versions of a fileRetrieves the version history for a Figma file or branch, as specified by its `file_key`.
  • Get webhook requestsRetrieves a history of webhook requests for a specific Figma webhook subscription; data is available for requests sent within the last seven days.
  • Render images of file nodesRender 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
  • Update a webhookUpdates an existing Figma webhook, identified by `webhook_id`, allowing modification of its event type, endpoint, passcode, status, or description.
  • Update dev resourcesUpdates the name and/or URL of one or more existing Figma Dev Resources, each identified by its unique `id`.