> ## 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. # How integrations work > Connect the systems your firm already runs on so Hebno can use client context and writes back only when you confirm. Integrations add the context outside your project files: the client's SharePoint site, last week's Zoom call, the open deal in your CRM, the job budget in your PSA, the receivables in your ledger, the survey results in Qualtrics. Hebno reads documents from an index and looks up records and personal data live, cites every record it used, and writes back to a system only after a person confirms the change on a card. ![Research run work trace with chips from SharePoint, Outlook, HubSpot and SAP S/4HANA](https://mintcdn.com/hebno/n4ZjS29g8cTdiNHz/images/research-trace.png?fit=max\&auto=format\&n=n4ZjS29g8cTdiNHz\&q=85\&s=b643aaf17089bc6eab6f8507cfd0e191) A research run reading from connected systems, with each record shown as a chip in the work trace. ## What an integration does Every integration does some or all of four things. ![Client map for Contoso Retail linking documents, CRM, ERP, finance, people and meetings](https://mintcdn.com/hebno/n4ZjS29g8cTdiNHz/images/hww-client-map.png?fit=max\&auto=format\&n=n4ZjS29g8cTdiNHz\&q=85\&s=7c62cd7a332da2e96e7ffc644a474dcb) Integrations connect each client's documents, deals, jobs, invoices, people and meetings. | Capability | What it means | Example | | - | - | - | | **Attach** | Pick an item from the system and add it to your message | Attach a Teams meeting transcript from the **+** menu | | **Search** | Hebno finds relevant records itself while it answers or runs research | "What did Contoso say about the renewal?" searches Outlook and Teams | | **Link** | Connect a project to its counterpart record so every chat in that project starts from it | Link the project to its HubSpot deal and its monday.com board | | **Write** | Hebno proposes a change on a confirmation card and writes it when you confirm | Create an Asana task, or a draft invoice in Xero | The [catalogue](https://hebno.com/docs/integrations/catalogue.md) lists which of these each integration supports, and exactly what it reads and writes. ## How a request is routed to a connected system ```mermaid theme={"system"} flowchart TD A[Your message] --> B{Does the request need connected data?} B -->|No| C[Answer from the chat and project] B -->|Yes| D[Search the relevant systems with your access] D --> E[Read the records that match] E --> F[Draft the answer or deliverable with citations] F --> G{Does it change a system?} G -->|No| H[Reply with sources] G -->|Yes| I[Confirmation card] I -->|You confirm| J[Write to the system and log it] I -->|You dismiss| H ``` The systems searched depend on your request. Naming the client, the system or the record ("in HubSpot", "the Asana project", "our last email with Priya") narrows the search. In a chat tagged to a project, the project's [linked records](https://hebno.com/docs/projects/linked-records.md) are searched first. ## How Hebno reads each system Documents in SharePoint, OneDrive, Google Drive, Dropbox, Box, Egnyte, iManage Work, NetDocuments, Confluence, Notion, Coda, Guru and Microsoft Loop that your admins select are stored in the knowledge index, searched by meaning and checked against source permissions. CRM, ERP, finance, PSA, HR, company data and analytics records and figures are looked up live and never copied. Email, calendar, meetings, call recordings and chat messages are searched live in the member's own account. Each live read runs at the moment of the request, so figures and statuses are current when the answer is drafted. The excerpts and records a reply actually uses are stored with the conversation, so the sources behind a deliverable remain available after the fact. See [How Hebno works](https://hebno.com/docs/get-started/how-hebno-works.md). ![Sources flowing through read, label, index and link steps, with business systems looked up live](https://mintcdn.com/hebno/n4ZjS29g8cTdiNHz/images/hww-pipeline.png?fit=max\&auto=format\&n=n4ZjS29g8cTdiNHz\&q=85\&s=d0e08b6826fd10f1af417a9d0a40e5f3) Documents are indexed by meaning. CRM, ERP and finance figures are looked up live. > [!WARNING] > > Excerpts a reply uses become part of the conversation. Anyone you share the conversation with can read them, including excerpts from email, meetings and finance systems. ## Writes always need a person Hebno never writes to a connected system on its own. When a request implies a change, the reply shows a confirmation card with the system, the action, the target record and every field it will set. Edit anything on the card, then select **Confirm**. For email and calendar invitations the button is **Send**. **Dismiss** discards the change. ![Confirmation card for a monday.com change with editable fields](https://mintcdn.com/hebno/A7yItabWdPf4lOIs/images/card-monday.png?fit=max\&auto=format\&n=A7yItabWdPf4lOIs\&q=85\&s=fe2c23161db57ce7408711d93b6000df) A confirmation card for monday.com. Nothing is written until you confirm. * A confirmed write uses your own account in the other system wherever you have a personal connection, so that system shows you as the author. * After a write, the card shows **Done** with a link to the record. * Every confirmed write is recorded in **Admin → Logs → Integrations**. * Agents never write unattended. A write an agent proposes appears in [agent approvals](https://hebno.com/docs/automate/agent-approvals.md) until someone confirms it. * In finance and ERP systems, Hebno creates drafts only. It never approves, posts, sends or pays. ## Two ways to connect | | Personal connection | Organisation connection | | - | - | - | | **Who connects** | Each member, for themselves | An owner or admin, once | | **Where** | **Settings → Connections**, or inline the first time you use it | **Admin → Connectors** | | **Whose access** | The member's own permissions in the other system | An integration user, scoped in Hebno by team and data area | | **Used for** | Microsoft 365, Google Workspace, files, knowledge, chat, meetings, CRM, project and time tools, design, engineering, support, surveys and marketing | ERP, finance, payments, PSA and resourcing, HR, company data and data warehouses | Some systems support both: the organisation connection provides access, and members can **Link your account** so writes appear under their own name. See [Permissions and access](https://hebno.com/docs/integrations/permissions-and-access.md) for how each model limits what a member can see. ## Where integrations appear * **Composer**: the **+** menu under **Sources**, or type `/` and the integration name. * **Work trace**: a research run shows a step per system, such as **Reviewing Outlook** or **Checking SAP S/4HANA**, with a chip for every item it found. * **Sources**: the button under each reply lists every file, email, meeting and record used, with the app logo and a link back to the original. * **Projects**: **Brain → Linked sources** and **Brain → Linked records**. * **Agents**: **Connected sources** and **Allowed actions** on the agent form. ## Get connected > [card] [Microsoft 365](https://hebno.com/docs/integrations/microsoft-365.md) > > OneDrive, SharePoint, Outlook, Teams, OneNote and Dynamics 365. > [card] [Google Workspace](https://hebno.com/docs/integrations/google-workspace.md) > > Drive, Docs, Sheets, Slides, Gmail, Calendar and Meet. > [card] [Meetings and calls](https://hebno.com/docs/integrations/zoom.md) > > Zoom, Webex, Gong, Fireflies.ai, Otter.ai, Fathom, Loom and Calendly. > [card] [PSA, time and resourcing](https://hebno.com/docs/integrations/kantata.md) > > Deltek WorkBook, Kantata, Productive, Harvest, Float and more. > [card] [Catalogue](https://hebno.com/docs/integrations/catalogue.md) > > All 111 integrations, what each one reads and what it writes. > [card] [Admin setup](https://hebno.com/docs/admin/connectors.md) > > Allow integrations, set access and connect organisation systems. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.