Select Actions to adjust the guide

Some actions may require additional configuration in the provider to be accessible. Choose the actions you need and the guide will be updated.

Action

Scope(s)

Loading actions...

Dynamic Guide URL

Scopes Selected


          
            Separator

Generate a personal access token

Create a new personal access token for API authentication.

Click your profile avatar in the top-left corner and select Settings.
Navigate to the Security tab.
Scroll to Personal access tokens.

Click Generate new token.

Enter a descriptive Token name (e.g., "StackOne Integration")
Select an expiration period (max 90 days)

Enables actions: Auth Test, Bulk Create Dev Resources, Bulk Update Dev Resources, Create Comment, Create Comment Reaction, Create Webhook, Delete Comment, Delete Comment Reaction, Delete Dev Resource, Delete Webhook, Get Comment Reactions, Get Comments, Get Component, Get Component Set, Get Current User, Get File, Get File Component Sets, Get File Components, Get File Metadata, Get File Nodes, Get File Styles, Get File Versions, Get Image Fills, Get Project Files, Get Style, Get Team Component Sets, Get Team Components, Get Team Projects, Get Team Styles, Get Unified Credentials, Get Unified Organization, Get Webhook, Get Webhook Requests, Get Webhooks, List Dev Resources, List Unified Organizations, Render Images, Update Webhook

Under Scopes, enable the permissions for your use case.

Enterprise-only scopes (file\_variables:read, file\_variables:write, library\_analytics:read) are only visible on the Enterprise plan

Click Generate token. Copy the token immediately and store securely — it is only shown once.

A plan access token is created by an organization admin and is not tied to one user. Paste it in the same Personal Access Token field.

Go to figma.com/developers/tokens and click Generate REST API token. Multi-factor authentication is required.
Choose scopes, then choose All resources or an allowlist of teams, folders, and files.
Expiry can be up to one year.
Plan access tokens cannot call Figma's current-user endpoint, so `auth_test`, `get_current_user`, `unified_get_me`, `unified_list_organizations`, and `unified_get_organization` return an error with this token type. They also cannot use scopes excluded from plan tokens, such as `file_comments:write` (`create_comment`, `delete_comment`, `create_comment_reaction`, `delete_comment_reaction`) and `file_variables:write` (`bulk_create_update_delete_variables`). Other actions work.

Find your Team IDs (optional)

Figma's API has no endpoint that lists teams, so team-level actions (projects, components, component sets, styles) need a Team ID. Enter one or more Team IDs here, separated by commas, and agents can discover them with `list_configured_teams`. The first one is the default when an action is called without a team. Leave blank if you only use file-level or IAM actions, or if you will pass a Team ID on every call.

Click on your team name in the left sidebar.

Look at your browser address bar.

Format: `https://www.figma.com/files/team/TEAM_ID/team-name`
Example: if your URL is `https://www.figma.com/files/team/1234567890/My-Team`, your Team ID is `1234567890`

Linking the Account from the Hub

Use one of the three Linking Account Methods to access the Hub. Fill out the following fields using details from your provider:

Personal Access Token
Team IDs (Optional)
SCIM Tenant ID (Optional)
SCIM Bearer Token (Optional)

Click Connect
If applicable, the provider will redirect you to a sign-in or authorization page. Complete the provider's authorization flow.
Once authorization is successful, you will see a confirmation popup

If the account linking is successful, you will see the newly linked account in your Accounts page.

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.