| name | figma-upgrade-migration |
| description | Handle Figma REST API scope changes, deprecations, and migration tasks.
Use when migrating from deprecated scopes, updating webhook versions,
or adapting to Figma API changelog changes.
Trigger with phrases like "upgrade figma", "figma deprecation",
"figma scope migration", "figma API changes", "figma v2 webhooks".
|
| allowed-tools | Read, Write, Edit, Bash(npm:*), Bash(git:*) |
| version | 1.6.0 |
| license | MIT |
| author | Jeremy Longshore <jeremy@intentsolutions.io> |
| tags | ["saas","figma"] |
| compatibility | Designed for Claude Code |
Figma Upgrade & Migration
Overview
Handle Figma REST API deprecations and breaking changes. The most significant recent change is the deprecation of the files:read scope in favor of granular scopes, and the move from Webhooks V1 to V2.
Prerequisites
- Current Figma integration working
- Git for version control
- Access to Figma developer settings
Instructions
Step 1: Scope Migration (files:read Deprecation)
The files:read scope is deprecated. Migrate to granular scopes:
| Deprecated Scope | Replacement Scopes | Endpoints Covered |
|---|
files:read | file_content:read | GET /v1/files/:key, GET /v1/images/:key |
files:read | file_comments:read | GET /v1/files/:key/comments |
files:read | file_dev_resources:read | GET /v1/files/:key/dev_resources |
files:read | file_versions:read | GET /v1/files/:key/versions |
Migration steps:
- Audit which endpoints your code calls
- Map each endpoint to its required scope
- Generate a new PAT with granular scopes
- Update OAuth apps with new scope list
- Test all endpoints with the new token
- Revoke old tokens
grep -rn "api.figma.com" --include="*.ts" --include="*.js" src/ \
| grep -oP '/v\d/[a-z_/]+' | sort -u
Step 2: Webhooks V1 to V2 Migration
