Figma

{/* Generated by scripts/generate-integration-catalog.mjs. Do not edit by hand. */}

At a glance

  • Availability: Enabled by default.
  • Authentication: OAuth 2.0.
  • Connection: A user authorizes the connection in the provider's consent screen.
  • Scopes: current_user:read, file_content:read, file_comments:read, file_comments:write.

Credentials

Set these per environment. See Connect an integration.

These variables are required only when you supply your own OAuth app. If a managed app is available, you can connect without setting them. Provider permissions and consent still apply.

VariableRequiredDescription
FIGMA_CLIENT_IDYesFigma OAuth Client ID (from your app settings) Docs.
FIGMA_CLIENT_SECRETYesFigma OAuth Client Secret Docs.

Setup

  1. Choose who owns the Figma OAuth app: On hosted Veryfront, Figma uses the Veryfront-managed Figma OAuth app: connect Figma from the project's integrations and approve the Figma consent screen, no environment variables needed. Set FIGMA_CLIENT_ID and FIGMA_CLIENT_SECRET only to use your own Figma OAuth app, which is required for local and self-hosted runs.
  2. Create an OAuth app: In Figma, open My Apps and create a new app for your team or organization.
  3. Set the redirect URLs and scopes: Select the scopes current_user:read, file_content:read, file_comments:read and file_comments:write. Add the redirect URI of the environment that completes the flow: https://api.veryfront.com/oauth/callback/figma for hosted Veryfront, or your app origin followed by /api/auth/figma/callback for a local or self-hosted app. Set FIGMA_CLIENT_ID and FIGMA_CLIENT_SECRET from the app's credentials.
  4. Publish the app: While the app is a draft, only you and your plan admins can authorize it. Publish it privately for your team or organization, or publicly after Figma's review, so other users can connect.
  5. Verify access: Run Get Me (read-only). It returns the connected Figma user without changing anything.

Provider notes

  • The connection requests current_user:read, file_content:read, file_comments:read and file_comments:write. file_comments:write is only needed by the tool that posts comments.
  • Tools that create, update, send or delete data are marked as writes and need write authority; the other tools are read-only.

Provider API reference.

Tools

ToolAccessDescription
Get Me<br /><code className="reference-identifier">figma__get_me</code>ReadGet Figma user profile
Get File<br /><code className="reference-identifier">figma__get_file</code>ReadGet file
Get Comments<br /><code className="reference-identifier">figma__get_comments</code>ReadGet comments
Post Comment<br /><code className="reference-identifier">figma__post_comment</code>WritePost comment

Verify the connection

Call a read tool such as figma__get_me with arguments for your account. Confirm that the result comes from the intended account or workspace before enabling write tools.