Integrations / Figma
Figma
Figma is a collaborative interface design tool
What Telara does
Capability matrix
Before you connect
Prerequisites
Vendor setup
Get the credential
Permissions Telara requests
- current_user:readOAuth 2.0
- file_comments:readOAuth 2.0
- file_comments:writeOAuth 2.0
- file_content:readOAuth 2.0
- file_metadata:readOAuth 2.0
- file_versions:readOAuth 2.0
- library_assets:readOAuth 2.0
- library_content:readOAuth 2.0
- projects:readOAuth 2.0
- team_library_content:readOAuth 2.0
- webhooks:readOAuth 2.0
- webhooks:writeOAuth 2.0
- file_dev_resources:readOAuth 2.0
- file_dev_resources:writeOAuth 2.0
In Telara
Connect in Telara
In Telara, open Settings → Integrations, choose this connector, and click Connect. Telara sends you to the vendor to approve access, then returns you here. You do not create an OAuth app or paste a client secret.
Personal Access Token. When access_token is present without refresh_token it is also treated as a PAT.
In Telara, open Settings → Integrations, choose this connector, and paste the key into the fields Telara shows.
- Token
Knowledge
What gets indexed
| Resource | Coverage |
|---|---|
| Design file | Partial — not every record the vendor holds is synced |
Sync
Freshness & sync
| Resource | Lag | Deletions |
|---|---|---|
| Design file | Up to 1 day | Removed records disappear on the next full sync |
Data handling
Permissions & data handling
The scopes above are the permissions this connector requests. They come from the catalog, not from a hand-written page.
Excluded from semantic search: Design file.
After connect
Verify it worked
After you save, Telara runs a read-only check against the account. The integration shows as connected when that check succeeds.
Honesty