> ## 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. # Affinity > Read Affinity organisations, people, opportunities, lists and relationship strength in Hebno, and add notes, list entries and field values after you confirm. The Affinity integration brings your firm's relationship data into client work. Ask who at the firm knows Contoso's CFO best, what was discussed at the last meeting, or which opportunities on a pursuit list have gone quiet, and Hebno answers from Affinity with each record cited. When a request implies a change, such as adding a note or putting an organisation on a list, Hebno shows a confirmation card and writes to Affinity only after you confirm. ## At a glance | | | | - | - | | **Connection** | Personal connection. Each member connects with their own Affinity API key. | | **Default access** | Read and write | | **Attach** | Organisations, people, opportunities, lists | | **Search** | Hebno searches Affinity when a request mentions a client, contact, introduction, relationship, list, opportunity or past meeting | | **Link** | A project links to an Affinity organisation and to one or more opportunities | | **Write** | Add a note, add to a list, update a field value. Every write needs a person to confirm. | ## Before you start You need: * An Affinity user in your firm's instance. * Permission to generate an API key. Affinity admins control this per role, so ask an admin if the option is missing. * An allowed integration. An owner or admin sets **Affinity** to **Allow** under **Admin → Connectors → Catalogue**. Affinity grants an API key the same access as the user who created it. There are no separate scopes, so Hebno sees exactly the lists, records and notes you can see in Affinity. Hebno uses the key for these requests: | Affinity API resource | Why Hebno needs it | | - | - | | Organisations, persons and opportunities | Read records, their global fields and enriched company data | | Lists, list entries and field values | Read lists and list fields, add entries and update values after you confirm | | Notes | Read notes on records and add them after you confirm | | Interactions and relationship strength | Read first and last email, last and next meeting, and the strength of each colleague's relationship with a person | | Whoami | Identify the connected user and instance | ## Connect Affinity **1. Create an API key in Affinity** In Affinity, open **Settings → Manage Apps** and select **Generate an API key**. Copy the key. Affinity shows it once. **2. Add the key in Hebno** Open **Settings → Connections**, find **Affinity** and select **Connect**. Paste the key and select **Connect**. You can also start from the prompt in a chat. **3. Check the connection** The card shows **Connected** with your Affinity instance and your name. Hebno reads and writes as you, so you see only the lists and records your Affinity sharing allows. The key is encrypted at rest. Select **Disconnect** at any time, or ask an admin to revoke the connection under **Admin → Connectors → Connections**. Revoking or regenerating the key in Affinity also ends the connection. ## What Hebno reads | Affinity object | Fields Hebno uses | Typical questions | | - | - | - | | **Organisation** | Name, domain, global fields, enriched data such as industry and headcount, lists it appears on | "What do we know about Contoso Retail?" | | **Person** | Name, emails, current organisation, job title, global fields | "Who do we know at Contoso?" | | **Opportunity** | Name, list, status, owners, associated organisations and people, list field values | "Which Contoso opportunities are open?" | | **List and list entry** | List name, type, entries, list fields such as status, owner and priority | "What is on the 2027 pursuits list, and what status is each entry?" | | **Note** | Content, creator, date, associated records | "What did Sarah note after the Contoso dinner?" | | **Interactions** | First and last email, last meeting, next meeting, with whom | "When did anyone last meet Contoso's CFO?" | | **Relationship strength** | Strength score between a colleague and an external person | "Who at the firm has the strongest relationship with Priya Nair?" | Reads are live. Hebno queries Affinity when a request needs it. Only what a reply used is stored with the conversation as its sources. Relationship strength appears as Affinity scores it, and Hebno names the colleague and the interactions behind it. > [!WARNING] > > Excerpts a reply uses become part of the conversation. Anyone you share the conversation with can read them, including notes, interaction history and contact details from Affinity. ## What Hebno writes Every write appears first as a confirmation card. You can change any field before you select **Confirm**. | Action | Affinity object | Fields on the card | | - | - | - | | **Add a note** | Note | Organisations, people or opportunities, note content | | **Add to a list** | List entry | List, organisation, person or opportunity | | **Update a field** | Field value | Record, list, field, new value | ![Confirmation card for Affinity with editable fields](https://mintcdn.com/hebno/JIjAXWoGoB3PLSSb/images/card-affinity.png?fit=max\&auto=format\&n=JIjAXWoGoB3PLSSb\&q=85\&s=7910a02d086b2ecb0c1fa520b18ec332) An Affinity change pending confirmation. Nothing is written until you confirm. Hebno never deletes records, notes or list entries, merges duplicates, changes list or field definitions, or changes sharing in Affinity. ```mermaid theme={"system"} sequenceDiagram participant You participant Hebno participant Affinity You->>Hebno: Note that Priya wants the pricing readout before Christmas Hebno->>Affinity: Find Priya Nair and Contoso Retail Affinity-->>Hebno: Person Priya Nair, organisation Contoso Retail Hebno-->>You: Confirmation card with records and note content You->>Hebno: Confirm Hebno->>Affinity: Create the note as you Affinity-->>Hebno: Note created Hebno-->>You: Done, with a link to the note ``` Notes are created with your API key, so Affinity shows you as the creator. ## Link a project to an organisation and an opportunity Linking marks which Affinity records belong to a project, so you can ask "who knows the client?" without naming the organisation. 1. Open the project and select **Brain**. 2. Under **Linked records**, select **Link record**, then **Affinity**. 3. Search for the organisation and select it. Repeat to add the opportunities that belong to the engagement. In chats tagged to the project, Hebno starts with the linked organisation and opportunities for any client or relationship question, and note cards default to them. See [Linked records](https://hebno.com/docs/projects/linked-records.md). ## Use Affinity in chat * **Attach**: open the **+** menu, choose **Sources → Affinity**, and pick an organisation, person, opportunity or list. Or type `/` and choose **Affinity**. * **Ask**: name the client, person or list in your request. For example: > Who at the firm has the strongest relationship with Contoso Retail's leadership, and when did each of them last meet? > List the entries on the 2027 pursuits list with no email or meeting since 1 October 2026. > Add Contoso Retail to the 2027 pursuits list, set the owner to Sarah Chen and add a note about the pricing review. * **Research runs** show a **Reviewing Affinity** step, with a chip for each record, list and note it read. * **Agents** can read Affinity on a schedule, for example a Friday list of key relationships with no contact in 60 days. Writes an agent proposes appear in [agent approvals](https://hebno.com/docs/automate/agent-approvals.md) for review. ## Troubleshooting | Symptom | Fix | | - | - | | **Connect** fails with **401 Unauthorized** | The key is wrong, was regenerated or was revoked. Generate a new key under **Settings → Manage Apps** and connect again. | | **Generate an API key** is missing in Affinity | Your role cannot create keys. Ask an Affinity admin to allow API key generation for your role. | | A list or note is missing from answers | The list or note is not shared with you in Affinity. Hebno reads only what you can read. | | A field update fails with **422** | The value does not match the field type, for example an unknown dropdown option. Pick a valid value on the card and select **Confirm** again. | | Relationship strength is missing for a person | Affinity has no email or calendar interactions between your colleagues and that person. | | Requests fail with **429 Too Many Requests** | Affinity limits requests per minute for each user and per month for each instance. Wait and retry, or ask an admin to check usage. | ## 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) * [Attio](https://hebno.com/docs/integrations/attio.md) * [HubSpot](https://hebno.com/docs/integrations/hubspot.md) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.