Figma
for LuumenAI
Sheets, files, and calendars in Figma pulled into the thread.
Pull the inventories, schedules, and checklists your team keeps in Figma into the thread, and write results back or book maintenance windows as reviewed actions.
The Figma toolbox
52 tools: 41 read, 11 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadDesign tokens to tailwindConvert design tokens to Tailwind CSS configuration.
- ReadDetect Background LayersDetect background layers for selected nodes in a Figma file.
- ReadDiscover Figma ResourcesSmart Figma resource discovery - extract IDs from any Figma URL.
- ReadDownload Figma ImagesDownload images from Figma file nodes.
- ReadExtract design tokensExtract design tokens from Figma files by combining styles, variables, and node-extracted values.
- ReadExtract Prototype InteractionsExtract prototype interactions and animations from Figma files.
- ReadGet activity logsRetrieves activity log events from Figma, allowing filtering by event types, time range, and pagination.
- ReadGet a webhookRetrieves detailed information about a specific webhook by its ID, provided the webhook exists and is accessible to the user.
- ReadGet 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.
- ReadGet componentFetches metadata for a specific component using its unique identifier.
- ReadGet component setRetrieves detailed metadata for a specific published Figma component set using its unique `key`.
- ReadGet current userRetrieves detailed information for the currently authenticated Figma user.
- ReadGet dev resourcesRetrieves development resources (e.g., Jira/GitHub links) for a Figma main file, optionally filtering by specific node IDs.
- ReadGet file componentsRetrieves published components from a Figma file, which must be a main file (not a branch) acting as a library.
- ReadGet file component setsRetrieves all published component sets from the specified Figma main file (file_key must not be for a branch).
- ReadGet file jsonGet Figma Design file data with automatic simplification.
- ReadGet file metadataGet Figma file metadata including name, creator, last modification details, thumbnail, and access information.
- ReadGet file nodesFetch JSON for specific node IDs from a Figma file to avoid full-file payload limits.
- ReadGet files in a projectFetches a list of files in a Figma project, optionally including branch metadata.
- ReadGet file stylesRetrieves a list of published styles (like colors, text attributes, effects, and layout grids) from a specified main Figma file (not a branch).
- ReadGet image fillsRetrieves temporary (14-day expiry) download URLs for all image fills in a Figma file; requires `imageRef` from `Paint` objects to map URLs.
- ReadGet 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).
- ReadGet 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'.
- ReadGet 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.
- ReadGet library analytics style usage dataRetrieves style usage analytics for a published Figma library.
- ReadGet 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…
- ReadGet 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.
- ReadGet 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.
- ReadGet paymentsRetrieves a user's payment information for a Figma plugin, widget, or Community file; the authenticated identity must own the resource.
- ReadGet projects in a teamRetrieves projects within a specified Figma team that are visible to the authenticated user.
- ReadGet published variablesRetrieves variables published from a specified Figma file; this API is available only to full members of Enterprise organizations.
- ReadGet reactions for a commentRetrieves reactions for a specific comment in a Figma file.
- ReadGet SCIM service provider configGet Figma's SCIM service provider configuration.
- ReadGet styleRetrieves detailed metadata for a specific style in Figma using its unique style key.
- ReadGet team componentsRetrieves components published in a specific Figma team's library; the team must have published components, otherwise an empty list is returned.
- ReadGet team component setsRetrieves a paginated list of published component sets (collections of reusable UI elements) from a specified Figma team's library.
- ReadGet team stylesRetrieves a paginated list of published styles (fill colors, text styles, effects, grids) from a specified Figma team's library.
- ReadGet webhooksRetrieves all webhooks registered for a specified Figma context (team, project, or file).
- ReadGet versions of a fileRetrieves the version history for a Figma file or branch, as specified by its `file_key`.
- ReadGet webhook requestsRetrieves a history of webhook requests for a specific Figma webhook subscription; data is available for requests sent within the last seven days.
- ReadRender images of file nodesRender Figma nodes as images (PNG, JPG, SVG, PDF).
- WriteAdd 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… Approval by default
- WriteAdd 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. Approval by default
- WriteCreate a webhookCreates a Figma webhook to receive POST notifications when specific events occur. Approval by default
- WriteCreate dev resourcesCreates and attaches multiple uniquely-URLed development resources to specified Figma nodes, up to 10 per node. Approval by default
- WriteCreate, 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… Approval by default
- WriteDelete a commentDeletes a specific comment from a Figma file or branch, provided the authenticated user is the original author of the comment. Approval by default
- WriteDelete a reactionDeletes a specific emoji reaction from a comment in a Figma file; the user must have originally created the reaction. Approval by default
- WriteDelete a webhookPermanently deletes an existing webhook, identified by its unique `webhook_id`; this operation is irreversible. Approval by default
- WriteDelete dev resourceDeletes a development resource (used to link Figma design elements to external developer information like code or tasks) from a specified Figma file. Approval by default
- WriteUpdate a webhookUpdates an existing Figma webhook, identified by `webhook_id`, allowing modification of its event type, endpoint, passcode, status, or description. Approval by default
- WriteUpdate dev resourcesUpdates the name and/or URL of one or more existing Figma Dev Resources, each identified by its unique `id`. Approval by default
One prompt, start to finish
What a governed Figma run looks like inside Luumen.
Questions
How does LuumenAI connect to Figma?
Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
Can LuumenAI change things in Figma on its own?
Read actions answer immediately. Anything that writes — add a comment to a file, add a reaction to a comment, create a webhook, create dev resources, and more — is shown as a plan and requires approval by default, including the 5 actions classified as destructive. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.
Who gets access to the integration?
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Is there an audit trail?
Every call to Figma — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Often connected alongside
All integrations
Put Figma to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.