Connect Parable to Figma using a Personal Access Token (PAT) sent as a Bearer credential. Parable ingests design assets, version history, team structure, and (Enterprise, opt-in) activity logs.
Design assets
Projects, files, components, variables, and version history
Activity & admin
File comments and org-level activity logs (Enterprise, opt-in)
Service account required. PATs are tied to the minting user — if that user is removed from the team the token is revoked immediately and ingestion stops. Always mint from a dedicated service-account user on a paid plan (Professional, Organization, or Enterprise).
activity_logs is disabled by default. Enable it only if your organization is on the Enterprise plan with the service-account user having org admin access. Non-Enterprise tenants will receive 402 payment_required on every sync.
Sign in to Figma as the dedicated service-account user.
Click your avatar in the top-right and open Settings.
Switch to the Security tab.
Scroll to Personal access tokens.
2
Generate the token
Click Generate new token.
Set:
Token name — something traceable, e.g. parable-platform-prod.
Expiration — choose the longest duration your security policy allows (30 days, 60 days, 90 days, 180 days, or No expiration). Rotate at least every 12 months even if using no expiration.
Scopes — add the following:
Scope
Purpose
file_metadata:read
Projects and files
file_variables:read
Design variables
file_dev_resources:read
Dev resources
file_comments:read
File comments and reactions
library_assets:read
Published library assets
library_content:read
Library content
team_library_content:read
Team-scoped library content
org:activity_log_read
Org activity logs (Enterprise only)
Copy the token.
Copy your now!This is the only time it will be displayed. Store it in a secure password manager before closing this page.
3
Enter values in the form
Personal Access Token: Paste the token from Figma.
Success! If you received a 200 OK response with valid data, your credentials are configured correctly. You can now proceed to configure this connector in Parable.
A successful response returns a JSON object with id, email, and handle for the minting user. If you receive 403 Invalid token, regenerate the token in Figma and retry.
Rate Limits: enforces rate limits of .Parable handles rate limiting automatically with exponential backoff, but initial syncs of large datasets may take longer due to these limits.
Token works in curl but the connector reports invalid
Confirm you copied the full token string — Figma PATs are 40+ characters and may contain hyphens. Trailing whitespace from a paste also fails; re-paste into the connector form.
