Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.

next
md 36 lines 2.09 KB
Rendered Raw
1 ---
2 type: "reference"
3 title: "Figma"
4 description: "Public support knowledge for Figma."
5 category: "auth-config"
6 visibility: "public"
7 timestamp: "2026-06-24T00:00:00Z"
8 tags:
9 - "figma"
10 ---
11 # Figma
12
13
14 ## Figma token auth is handled by Composio; customers do not need a separate Bearer-token auth scheme
15
16 For Figma, customers can provide the supported credentials/token through the toolkit's auth mode, and Composio handles the Bearer authorization header internally. They should not need to manually create a separate Bearer-token auth scheme for normal Figma tool use.
17
18 ## `FIGMA_EXTRACT_DESIGN_TOKENS` variables may be limited by the customer's Figma plan
19
20 Some Figma API features are plan-limited. If `FIGMA_EXTRACT_DESIGN_TOKENS` fails when `include_variables` is enabled, ask the customer to verify their Figma plan/API access. As a workaround, set `include_variables` to false.
21
22 ## Figma 429s can come from Figma/provider limits; use custom credentials for production
23
24 If Figma returns 429, verify the response is coming from Figma and review Figma's rate-limit docs. Composio's default Figma app is fine for testing, but production use should use the customer's own Figma credentials to avoid shared-app pressure and to control scopes/rate limits.
25
26 ## Remove deprecated `file_read` from Figma auth configs and reconnect
27
28 If a Figma auth config contains the deprecated `file_read` scope, remove it and initiate a new connection.
29
30 ## Figma tools are available across auth modes; fetch available tools dynamically
31
32 Figma tools should be usable regardless of whether the connection uses Composio-managed OAuth, a custom OAuth app, or token/API-key auth. If a customer cannot find a tool, fetch available tools dynamically and check the auth scopes required by that tool.
33
34 ## Common Figma design-token tools include extract, Tailwind conversion, and node fetch
35
36 For Figma design-token and component workflows, use `FIGMA_EXTRACT_DESIGN_TOKENS`, `FIGMA_DESIGN_TOKENS_TO_TAILWIND`, and `FIGMA_GET_FILE_NODES`. The older `FIGMA_GET_COMPONENT` action is deprecated. If a needed Figma tool is missing, ask the customer to file a tool request.