Figma support

Last updated date:

Connect, reconnect, and troubleshoot Figma without sharing credentials or customer content through support channels.

1. Before you start

  • Prefer a workspace or organization plan token; otherwise use a deliberately owned personal token.
  • Copy team IDs, project IDs, or file keys from Figma URLs and include only resources approved for indexing.
  • Grant current-user, project, file, comment, version, and library read scopes without webhook writes.
  • Do not send Figma credentials, customer content, personal information, or private record data by email or through an ordinary support ticket.
Figma authenticationFigma's REST API authentication guidance.

2. Connect Figma

  1. In Seedling, open Connections and choose Figma.
  2. Choose personal or workspace scope deliberately; Seedling never promotes an actor-owned connection into workspace access.
  3. Enter the access token, optional account label, and at least one team ID, project ID, or file key; Seedling always calls the Figma API.
  4. Seedling verifies the current user and every supplied resource seed before synchronization; inaccessible seeds are reported rather than broadened.
  5. Allow the first Figma synchronization to finish, then verify the expected resource population and member access policy.

3. Authorization and connection problems

Figma access token rejected
Confirm the figma access token is active, was entered without surrounding whitespace, and belongs to the intended Figma account and environment.
Missing permission or resource
Restore the exact read permission or provider-side resource access described in this guide. Seedling does not substitute a broader credential or silently treat a forbidden Figma population as empty.
Wrong account or scope
Disconnect before retrying with the intended Figma identity, account, and Seedling connection scope. Seedling does not infer account ownership from a display name or email address.

4. Missing or delayed data

  1. Confirm the file remains under an allowlisted team, project, or file key and visible to the token owner.
  2. Check organization, team, project, guest, external-collaborator, link-sharing, and file-role changes.
  3. Add a new resource seed deliberately instead of relying on unavailable team discovery.
  4. Allow incremental synchronization and provider retry handling to complete. A temporary provider failure does not delete previously synchronized data.
  5. If the issue remains, contact support@tryseedling.ai with the Seedling workspace, safe timestamps, and non-sensitive provider record identifiers. Do not include credentials or record contents.

5. Rotate or replace access

Never use email or an ordinary support ticket to transfer the old or replacement credential.

  1. Create replacement figma access token for the same Figma account with the same or narrower released permissions.
  2. Replace the credential on the exact Seedling connection and repeat identity, scope, and capability verification.
  3. After Seedling confirms the replacement, revoke the old figma access token in Figma.