> ## Documentation Index > Fetch the complete documentation index at: https://hebno.com/docs/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > Hebno is an AI work platform for client research and delivery: chat, research runs with sources, deliverables (Word, PowerPoint, Excel, email), projects, a shared library, agents, Office add-ins, and integrations with Microsoft 365, Google Workspace, CRM, project delivery, ERP and finance systems. > Use British English (organisation, not organization). > Every feature and integration described in these docs is available. Describe it as documented. > Hebno never writes to a connected system without a member confirming a card. Finance and ERP writes are drafts only. > Do not discuss commercial terms. Direct commercial questions to support@hebno.com. > Start with /index and /get-started/quickstart. # Figma > Read Figma files, pages, frames, comments and versions in Hebno, attach frames as images, and post comments after you confirm. The Figma integration brings design work into your client conversations. Attach the checkout frame from the Contoso pricing prototype, ask what feedback is still open on a file, or compare this week's version with last week's, and Hebno answers from Figma with each file, frame and comment cited. When a request implies a change, such as replying to feedback, Hebno shows a confirmation card and posts the comment to Figma only after you confirm. ## At a glance | | | | - | - | | **Connection** | Personal connection. Each member connects their own Figma account. | | **Default access** | Read and write | | **Attach** | Files, pages, frames as PNG, SVG or PDF images | | **Search** | Hebno searches Figma when a request mentions a design, file, prototype, frame, page, comment or version | | **Link** | A project links to one or more Figma files or projects | | **Write** | Post a comment or a reply on a file or frame. Every write needs a person to confirm. | ## Before you start You need: * A Figma account that can open the files you want to use, as a member of the team or organisation or as a guest invited to the file. * An allowed integration. An owner or admin sets **Figma** to **Allow** under **Admin → Connectors → Catalogue**. * Approval from a Figma organisation admin if your organisation restricts which apps members can authorise. Hebno requests these OAuth scopes: | Scope | Why Hebno needs it | | - | - | | `current_user:read` | Identify your Figma account by name and email | | `file_metadata:read` | Read file names, owners, thumbnails and last modified dates | | `file_content:read` | Read pages, frames, layers and text, and export frames as images | | `file_versions:read` | Read a file's version history | | `file_comments:read` | Read comments, replies and reactions | | `file_comments:write` | Post comments and replies after you confirm | | `projects:read` | List the team projects and files you can open | Hebno does not request access to edit design content, variables, webhooks or library analytics. ## Connect Figma **1. Start the connection** Open **Settings → Connections**, find **Figma** under **Design and whiteboards** and select **Connect**. You can also select **Connect** from the prompt in a chat. **2. Sign in to Figma** Sign in, review the access request and select **Allow access**. **3. Return to Hebno** The card shows **Connected** with your Figma email. Hebno reads and writes with your own permissions, so you see only the files you can open in Figma. Tokens are encrypted at rest. Select **Disconnect** at any time, or ask an admin to revoke the connection under **Admin → Connectors → Connections**. ## What Hebno reads | Figma object | Fields Hebno uses | Typical questions | | - | - | - | | **File** | Name, team project, editor type (design, FigJam), last modified, thumbnail | "Which Contoso files changed this week?" | | **Page** | Name, frames on the page | "What pages are in the Contoso pricing prototype?" | | **Frame** | Name, size, text layers, component names, exported image | "Show me the new price tag frame." | | **Comment** | Author, date, text, replies, resolved flag, frame it is pinned to | "What feedback is still unresolved on the checkout flow?" | | **Version** | Label, description, author, date | "What changed between the 28 October and 2 November versions?" | | **Project** | Name, files | "Which files are in the Contoso Retail team project?" | Frames are exported through the Figma image endpoint as PNG at 1x or 2x, SVG or PDF. Exported frames are attached to the chat as images, so Hebno can describe a layout and quote its text. Reads are live. Hebno queries Figma when a request needs it. Only what a reply used is stored with the conversation as its sources. > [!WARNING] > > Excerpts and images a reply uses become part of the conversation. Anyone you share the conversation with can see them, even if they cannot open the file in Figma. ## What Hebno writes Every write appears first as a confirmation card. You can change any field before you select **Confirm**. | Action | Figma object | Fields on the card | | - | - | - | | **Post a comment** | Comment | File, frame to pin it to, comment text | | **Reply to a comment** | Comment reply | File, comment thread, reply text | ![Confirmation card for Figma with editable fields](https://mintcdn.com/hebno/JIjAXWoGoB3PLSSb/images/card-figma.png?fit=max\&auto=format\&n=JIjAXWoGoB3PLSSb\&q=85\&s=753f4fdec0760d673ace010e36d26f72) A Figma change pending confirmation. Nothing is written until you confirm. Hebno never edits layers, frames or components, resolves or deletes comments, changes sharing, or creates, moves or deletes files. ```mermaid theme={"system"} sequenceDiagram participant You participant Hebno participant Figma You->>Hebno: Comment on the price tag frame with the research finding Hebno->>Figma: Find the price tag frame in the Contoso prototype Figma-->>Hebno: Frame Price tag v3 on page Store Hebno-->>You: Confirmation card with file, frame and comment You->>Hebno: Confirm Hebno->>Figma: Post the comment pinned to the frame as you Figma-->>Hebno: Comment posted Hebno-->>You: Done, with a link to the comment ``` Comments are posted as your Figma account, so Figma shows you as the author. ## Link a project to a Figma file Linking marks which Figma files belong to an engagement, so you can ask "what feedback is open?" without naming the file. 1. Open the project and select **Brain**. 2. Under **Linked records**, select **Link record**, then **Figma**. 3. Paste a Figma file link, or search by file or project name, and select it. Repeat for each file or team project in the engagement. In chats tagged to the project, Hebno starts with the linked files for any design question, and comment cards default to them. See [Linked records](https://hebno.com/docs/projects/linked-records.md). ## Use Figma in chat * **Attach**: open the **+** menu, choose **Sources → Figma**, and pick a file, a page or a frame. Or type `/` and choose **Figma**. You can also paste a Figma link with a node ID to attach that frame. * **Ask**: name the file, frame or person in your request. For example: > List the unresolved comments on the Contoso pricing prototype, grouped by frame. > Put the price tag and shelf strip frames into a slide with a short caption for each. > Reply to Sarah Chen's comment on the checkout frame that the 12 interviews support the larger price font. * **Research runs** show a **Checking Figma** step, with a chip for each file and frame it read. * **Agents** can read Figma on a schedule, for example a Friday digest of new comments on linked files. Writes an agent proposes appear in [agent approvals](https://hebno.com/docs/automate/agent-approvals.md) for review. ## Troubleshooting | Symptom | Fix | | - | - | | Figma returns `403 Invalid token` | The authorisation was revoked or expired. Select **Connect** to authorise again. | | A file returns `404 Not found` | You cannot open the file in Figma. Ask the file owner to share it with you. | | A frame image is blank or fails to render | The frame is very large or contains many images. Pick a smaller frame, or attach at 1x instead of 2x. | | Figma says your organisation does not allow the app | A Figma organisation admin restricts apps. Ask them to approve Hebno, then connect again. | | A comment fails to post | You have view access without permission to comment, or the frame was deleted. Check your access in Figma. | | Requests fail with `429 Too Many Requests` | Figma limits requests per minute for each user. Wait for the time in the message and retry. | ## Related * [How integrations work](https://hebno.com/docs/integrations/index.md) * [Permissions and access](https://hebno.com/docs/integrations/permissions-and-access.md) * [Linked records](https://hebno.com/docs/projects/linked-records.md) * [Miro](https://hebno.com/docs/integrations/miro.md) * [Canva](https://hebno.com/docs/integrations/canva.md) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.