Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
| 1 | ## Why can `FIGMA_EXTRACT_DESIGN_TOKENS` fail when `include_variables` is enabled? |
| 2 | |
| 3 | When `include_variables` is enabled, the tool calls Figma's local variables endpoint and the connected account must have the `file_variables:read` scope. If Figma returns a 403 saying the endpoint requires `file_variables:read`, reconnect with Figma credentials that can grant that scope. Figma exposes this scope only for Enterprise organization members. |
| 4 | |
| 5 | If you do not need Figma variables, set `include_variables` to `false`. The tool can still extract tokens from local styles and nodes without calling the variables endpoint. |
| 6 | |
| 7 | ## What can cause Figma 429s? |
| 8 | |
| 9 | A 429 means Figma rate limited the request. Confirm the response is coming from Figma, reduce request volume, add backoff, and retry after the provider limit resets. |
| 10 | |
| 11 | Default Figma auth is useful for quick testing. For production traffic, use your own Figma credentials so your app controls its scopes, traffic pattern, and rate-limit exposure. |