Skip to main content
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

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:

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

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.
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.
Confirmation card for Affinity with editable fields

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. Notes are created with your API key, so Affinity shows you as the creator. 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.

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 for review.

Troubleshooting