Figma is connected once at the org level by an admin. The credential is shared across all groups that have been granted access — individual team members don't need to connect their own accounts.
Generate a Personal Access Token in Figma: go to your Figma account Settings → Security → Personal access tokens → Create new token. Give it a name, set expiration, and paste the token below.
Ready to connect?
Go directly to the integrations page in your dashboard.
These are the data scopes On Belay can be granted for Figma. Your org admin controls which scopes are enabled per group.
| Scope | Description | Access |
|---|---|---|
current_user:read | Read current user profile | Read only |
file_content:read | Read file content | Read only |
file_metadata:read | Read file metadata | Read only |
file_versions:read | Read file versions | Read only |
file_comments:read | Read comments | Read only |
file_comments:write | Write comments | Read / Write |
library_assets:read | Read library assets | Read only |
library_content:read | Read library content | Read only |
team_library_content:read | Read team library content | Read only |
file_dev_resources:read | Read dev resources | Read only |
file_dev_resources:write | Write dev resources | Read / Write |
Double-check that you copied the full key without any leading/trailing spaces. Some platforms show a truncated preview — make sure to copy the full token. If the key was generated with restricted scopes, verify it includes the permissions listed above.
Check that your group has been granted access to this integration in On Belay → Groups → [your group] → Integrations. Also verify the specific scopes your group is permitted to use match what your query requires.
Some API keys have expiration policies. Generate a new key in Figma and update it in On Belay → Integrations → Figma → Update key. Consider creating a dedicated service account or machine user for On Belay so the key isn't tied to a personal account.
Still stuck? We're happy to help.
Contact support →