> ## 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. # Miro > Read Miro boards, frames, sticky notes, cards and comments in Hebno, and add sticky notes or create boards after you confirm. The Miro integration brings workshop output into your client work. Ask what the Contoso pricing workshop concluded, group the sticky notes on a board into themes, or turn interview findings into notes for the next session, and Hebno answers from Miro with each board and frame cited. When a request implies a change, such as adding sticky notes or creating a board, Hebno shows a confirmation card and writes to Miro only after you confirm. ## At a glance | | | | - | - | | **Connection** | Personal connection. Each member connects their own Miro account and chooses a team. | | **Default access** | Read and write | | **Attach** | Boards, frames | | **Search** | Hebno searches Miro when a request mentions a board, workshop, frame, sticky note, card or comment | | **Link** | A project links to one or more Miro boards | | **Write** | Add sticky notes to a board, create a board. Every write needs a person to confirm. | ## Before you start You need: * A Miro account in the team that contains your client boards. You pick a team when you connect, and Hebno uses that team. * Edit access to a board before Hebno can add sticky notes to it. * An allowed integration. An owner or admin sets **Miro** to **Allow** under **Admin → Connectors → Catalogue**. * Approval from your Miro company admin if your company restricts which apps members can install. Hebno requests these OAuth scopes: | Scope | Why Hebno needs it | | - | - | | `identity:read` | Identify your Miro user by name and email | | `team:read` | Read the team you chose when you connected | | `boards:read` | Read boards, frames, sticky notes, cards, text, shapes, tags and comments | | `boards:write` | Add sticky notes and create boards after you confirm | ## Connect Miro **1. Start the connection** Open **Settings → Connections**, find **Miro** under **Design and whiteboards** and select **Connect**. You can also select **Connect** from the prompt in a chat. **2. Choose a team** Sign in to Miro, select the team that contains your client boards, and select **Add**. **3. Return to Hebno** The card shows **Connected** with your Miro team name. Hebno reads and writes with your own permissions, so you see only the boards you can open in that team. To use another team, select **Reconnect** and choose it. 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 | Miro object | Fields Hebno uses | Typical questions | | - | - | - | | **Board** | Name, description, owner, team, created and modified dates | "Which Contoso boards changed this week?" | | **Frame** | Title, items inside it | "What came out of the pricing tensions frame?" | | **Sticky note** | Text, colour, tags, frame, author, position | "Group the sticky notes from the workshop into themes." | | **Card** | Title, description, assignee, due date, tags | "Which actions from the workshop have an owner?" | | **Text and shape** | Text content, frame | "What headings did we use on the customer map?" | | **Comment** | Author, date, text, resolved flag | "What did Sarah Chen comment on the board?" | Reads are live. Hebno queries Miro when a request needs it. Only what a reply used is stored with the conversation as its sources. > [!WARNING] > > Excerpts a reply uses become part of the conversation. Anyone you share the conversation with can read them, including sticky notes and comments from Miro boards. ## What Hebno writes Every write appears first as a confirmation card. You can change any field before you select **Confirm**. | Action | Miro object | Fields on the card | | - | - | - | | **Add sticky notes** | Sticky notes on a board | Board, frame, text of each note, colour, tags | | **Create a board** | Board | Name, description, team | ![Confirmation card for Miro with editable fields](https://mintcdn.com/hebno/JIjAXWoGoB3PLSSb/images/card-miro.png?fit=max\&auto=format\&n=JIjAXWoGoB3PLSSb\&q=85\&s=1a2a279f78c8ccf6afc4bc56d564a741) A Miro change pending confirmation. Nothing is written until you confirm. New sticky notes are placed in a grid inside the frame you choose, or in an empty area of the board. Hebno never moves, edits or deletes existing items, changes board sharing, or deletes boards. ```mermaid theme={"system"} sequenceDiagram participant You participant Hebno participant Miro You->>Hebno: Add the interview themes to the Contoso workshop board Hebno->>Miro: Find the Contoso pricing workshop board and its frames Miro-->>Hebno: Board with frame Interview themes Hebno-->>You: Confirmation card with frame and six sticky notes You->>Hebno: Confirm Hebno->>Miro: Create the sticky notes as you Miro-->>Hebno: Six sticky notes created Hebno-->>You: Done, with a link to the frame ``` Items are created as your Miro user, so Miro shows you as the author. ## Link a project to a board Linking marks which Miro boards belong to an engagement, so you can ask "what did the workshop conclude?" without naming the board. 1. Open the project and select **Brain**. 2. Under **Linked records**, select **Link record**, then **Miro**. 3. Paste a Miro board link, or search by board name, and select it. Repeat for each board in the engagement. In chats tagged to the project, Hebno starts with the linked boards for any workshop question, and sticky note cards default to them. Boards created from the project are linked automatically. See [Linked records](https://hebno.com/docs/projects/linked-records.md). ## Use Miro in chat * **Attach**: open the **+** menu, choose **Sources → Miro**, and pick a board or a frame. Or type `/` and choose **Miro**. * **Ask**: name the board, frame or workshop in your request. For example: > Group the sticky notes in the pricing tensions frame into themes and count the notes in each. > Write up the Contoso workshop board as a one-page summary with decisions and open questions. > Create a board for the Contoso readout rehearsal and add one sticky note for each key finding. * **Research runs** show a **Checking Miro** step, with a chip for each board and frame it read. * **Agents** can read Miro on a schedule, for example a summary of new sticky notes after each workshop. Writes an agent proposes appear in [agent approvals](https://hebno.com/docs/automate/agent-approvals.md) for review. ## Troubleshooting | Symptom | Fix | | - | - | | A board you expect is missing | The board is in another team. Select **Reconnect** and choose that team. | | Adding sticky notes fails with `403 Forbidden` | You have view or comment access on the board. Ask the board owner for edit access. | | Miro says the app is not allowed for your company | A Miro company admin restricts apps. Ask them to approve Hebno, then connect again. | | Creating a board fails | Your team role cannot create boards, or the team has reached its board limit. Ask your Miro team admin. | | Sticky notes appear outside the frame | The frame is full. Resize the frame in Miro, or choose another frame on the card. | | Requests fail with `429 Too Many Requests` | Miro limits requests per minute for each user. Wait 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) * [Figma](https://hebno.com/docs/integrations/figma.md) * [Canva](https://hebno.com/docs/integrations/canva.md) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.