Figma
Read Figma designs, comments and design systems so agents build what was designed.
Connect it with: Sign in (OAuth), API key. Figma's own documentation: https://developers.figma.com/docs/rest-api/oauth-apps/.
What agents can do
Connect Figma so the agents working your tasks can reach it. With it connected, they can:
- Read the frames, layers, text and styles of a design a task links to, and build the UI to match.
- Export images of frames to compare a build with the design.
- Read comments on a design for decisions and open questions.
- Use your published components and styles so code follows the design system.
Before you start
- A Figma account with at least view access to the files agents should read.
- A Jaah account. Anyone can add a personal secret; an organization secret needs an Org Owner or Admin.
Connect with Figma
This is the quickest way in: you sign in to Figma and approve what Jaah asks for. You never copy a key.
- In Jaah, open Secrets and select New.
- Search for Figma and select its card.
- Give the secret a name you will recognize, such as the account or workspace it reaches, and choose who can use it (see Who can use it).
- Select Connect Figma. Figma's sign-in window opens.
- Sign in to Figma if asked, check the access listed, and approve it.
- You land back in Jaah on the new secret, which reads Connected once its test passes.
If the button reads Jaah app not configured, this Jaah has no app registered at Figma yet. Use an API key, or your own OAuth app, until it does.
Scopes Jaah requests
Jaah asks Figma for these scopes, and no others. A scope marked optional is a checkbox on the Connect screen: untick it and agents simply cannot do that part.
| Scope | Why Jaah asks for it | Required |
|---|---|---|
current_user:read | Read your name, email and avatar, so the connection shows whose it is | Yes |
folders:read | List a team's folders and their files, so agents can find a design | Yes |
file_content:read | Read a design file's frames, layers and styles | Yes |
file_comments:read | Read the comments on a design for context | Yes |
library_content:read | Read published components and styles of your design system | Yes |
file_comments:write | Reply on a design with questions or results | No — you may untick it |
Connect with an API key
Prefer this when you cannot sign in with Figma — for example a service account, or a token your admin issued. On the Connect screen select Use an API key instead.
Find each value first:
- Personal access token (optional): Figma > your avatar > Settings > Security > Personal access tokens > Generate new token: name it Jaah, set an expiry, choose read scopes for File content, Comments and Library content, then copy it - Figma shows it once.
Then add it to Jaah:
- In Jaah, open Secrets, select New, and pick the Figma card.
- Name the secret and choose who can use it.
- Select Use an API key instead.
- Fill in Personal access token.
- Select Save. Jaah tests the secret straight away (see Test the connection).
Jaah encrypts what you type and never shows it again — not to you, and not to an admin.
Use your own OAuth app
Register your own OAuth app at Figma when your company requires apps it controls, or before this Jaah has an app registered there.
- Create an OAuth app in Figma's developer settings (Figma's documentation).
- Set its redirect URI to
https://app.jaah.ai/api/credentials/connect/callback(on your own Jaah, its console address followed by/api/credentials/connect/callback). - Give it the scopes in Scopes Jaah requests.
- Copy its client ID and client secret.
- In Jaah, start a new Figma secret, select Use your own OAuth app, paste both values and select Connect Figma.
The client secret is stored with the connection, encrypted, like any other secret value.
Test the connection
Select Test on the secret. Jaah makes one read-only call to Figma with the stored values and shows the result on the secret's page. Jaah also tests automatically when you save or reconnect.
Who can use it
Every secret has an owner, and the owner decides who can use it:
- Personal — only your own tasks can use it. This is the default.
- Organization — every task in the organization can use it. Only Org Owners and Admins can choose this.
- Attached to a project — every task on that project can use it, whoever started the task. See Attach a secret to a project.
More on owners and access: How secrets work.
Use it in an agent session
An agent asks for the secret with its credential_get tool, by the secret's path, when it needs it, and gets the values for that one call. The path is the owner's prefix and the secret's name:
org/<name>for an organization secret,projects/<project>/<name>for one attached to a project,me/<name>for your personal one.
A signed-in connection hands the agent a live access_token, with access_token_expires_at. Jaah refreshes it before it expires, so an agent never handles a refresh token.
A key connection hands the agent its fields: api_token.
Tell the agent in your task description which secret to use, for example “use the Figma secret org/figma”.
Manage, rotate or disconnect
Everything is on the secret's page under Secrets:
- Rotate a key: create a new key at the vendor first, then select Replace on the secret and paste it. Revoke the old key at Figma once the test passes. Steps: Replace or delete a secret.
- Reconnect: when Figma ends the grant (a password change, a revoked app, an expired refresh), the secret shows Needs reconnect. Select Reconnect and sign in again; agents get the new token on their next call.
- Disconnect: select Delete. The stored values are destroyed and agents lose access on their next call. To end access at Figma's side too, revoke Jaah in Figma's settings, or revoke or delete the key at Figma.
Limitations
- Agents see only the files the connected account can open.
- Figma's REST API reads designs; it cannot edit them. Changes go through comments.
- Personal access tokens expire after at most 90 days; a sign-in renews itself.
- Figma rate-limits REST API calls per user and plan, and very large files are slow to read.
- Agents can do only what the connected Figma account and its granted scopes allow.
Troubleshooting
Test says Figma rejected the personal access token
The token expired or was revoked. Generate a new one in Settings > Security and select Replace, or select Connect Figma instead.
The Connect button reads Jaah app not configured
This Jaah has no Figma app set up yet. Use a personal access token until your operator sets it up.
Agents get 403 or 404 for a file
The connected account cannot open that file. Share the file or its project with that account in Figma.
Still stuck? Select Test and read the result: it names the value Figma refused and the status it answered.
FAQ
Sign-in or personal access token?
Sign in for a connection that renews itself. A personal access token suits a quick start, but expires within 90 days.
Can agents change my designs?
No. Figma's API only reads design files; agents can reply in comments if you allow it.
Can Jaah or an admin see the key or token?
No. Jaah stores it encrypted and never shows it again. Only the tasks allowed to use the secret receive it, at the moment they ask for it.
Can I connect more than one Figma account?
Yes. Add one secret per account, each with its own name, and tell the agent which one to use.