Claude Affinity connectorWhat Claude can do in your Affinity account.
The Claude Affinity connector exposes 31 tools. 19 read your relationship data, 5 write to it, and 7 are documented nowhere under their exact name. Below: what Claude reads, what it records, who can restrict it, and where sources differ.
Verified Trustpilot reviews · AI, automation & growth agency
What changes for a deal team
Before a partner meeting, you no longer rebuild the history by hand. Claude reads the people, companies and pipeline lists your firm keeps in Affinity, pulls past meetings and transcript excerpts, and answers in the chat. When the call is over, it can log the note, set the reminder and move a list entry forward.
Prep a meeting from your own history. get_meetings_for_entity lists every meeting with a founder or a company, get_notes_for_entity brings back what your team wrote, and get_transcript_fragments quotes what was actually said.
Read the pipeline without building a view. get_lists and get_single_list_entry show where a company sits in your deal lists, search_opportunities finds deals by keyword.
Log the outcome. create_note attaches your recap to the person or company, create_reminder schedules the follow-up and upsert_list_entry_field_values sets the stage and deal lead on the list entry.
What it will not do: the directory sheet carries no tool to delete a record or a reminder, and none to create a person, a company or an opportunity, although Affinity's documentation describes such tools elsewhere. Nothing runs on its own either: no tool fires when a relationship score moves. For event-driven syncs, the Affinity n8n integration covers another need, and the Integrations hub lists the rest.
The vocabulary in one minute
Five words you will meet while plugging Affinity into Claude.
- Connector
- The link you set up once between Claude and an account you already have, so Claude can work in it while it answers you.
- Tool
- One named thing a connector lets Claude do. Claude picks the ones it needs on its own, and the directory sheet lists them by name.
- Authorization
- Affinity's own sign-in and consent screen, where you hand Claude its access. Granted once per person, and you can take it back.
- Approval
- The confirmation Claude waits for before it goes ahead with a change to your account, shown in the conversation when it matters.
- MCP
- The shared standard connectors are built on: it is what lets an assistant like Claude talk to an outside service such as Affinity.
Connect Affinity to Claude in three steps
- 01
Find Affinity in Claude
Open Claude's settings, go to Customize then Connectors, and look for Affinity. On a Team or Enterprise workspace, an Owner or Primary Owner has to switch the connector on before members can sign in to it.
- 02
Start the connection
Click Connect on Affinity's row and sign in to Affinity in the window it opens itself. Every user does this individually. To re-authorize later, use Disconnect first, then connect again.
- 03
Read the consent screen
Go through Affinity's consent screen before you accept. It belongs to Affinity, not to Claude, and it sets what the access covers, including whether Claude may write at all. Affinity admins can revoke it later.
The 31 tools, sorted by what they do
Affinity gives Claude 31 tools: 19 that read your account, 5 that change something in it, and 7 no official source describes.
Three groups: what Claude reads, what it writes, and what no official source describes under its exact name. Tool names stay as Claude shows them.
- 19 read
- 5 write
- 7 not documented
What Claude reads (19)
19 toolsNineteen tools that look things up in Affinity without touching your data.
get_company_info
Opens the full profile of one company with its field data, such as description and location.
get_company_list_entries
Shows which of your lists a given company appears on, so Claude knows whether it is tracked as a deal, a portfolio company or a prospect.
get_current_user
Confirms which Affinity user Claude is authenticated as and that the connection works.
get_entities_attached_to_note
Finds which people, companies or opportunities are linked to a specific note, the context Claude needs to read it correctly.
get_entity_fields
Reveals which fields exist on people or companies, custom ones included. Claude learns your firm's vocabulary before filtering on it.
get_list_field_dropdown_options
Lists the options available on a dropdown field of a list, such as the values of a Status column.
get_list_fields
Shows which fields are tracked on a specific list, the columns your team fills for each entry.
get_list_info
Returns a list's metadata, with a direct link to open it in Affinity.
get_lists
Enumerates every list you have access to, optionally filtered by name.
get_meetings
Pulls past and upcoming meeting interactions with their attendees across your organisation.
get_meetings_for_entity
Brings back the meetings tied to one person, company or opportunity, so the history of a relationship fits in one answer instead of a scroll through the timeline.
get_notes_for_entity
Retrieves every note attached to a specific person, company or opportunity.
get_person_info
Opens the detailed profile of one person with their field data, such as current title and organisation.
get_person_list_entries
Reveals which lists a person appears on, telling Claude where that contact already sits in your pipelines.
get_reminders
Reads all of your team's reminders, gathered in one list rather than scattered across records.
get_single_list_entry
Fetches one specific entry on a list, for example a company's row on the Series A pipeline.
get_transcript_fragments
Retrieves dialogue fragments from your team's meeting transcripts, so Claude can quote the conversation instead of paraphrasing a note.
search_opportunities
Searches opportunities by keyword, or returns them all.
search_persons
Looks for people across your organisation with structured filters, sorting, a keyword, or a mix of the three.
What Claude writes (5)
5 toolsFive tools that add or change something. No source gives them their own confirmation rule: the general one below applies.
create_list_entry
Approval: see the rulePuts an existing person or company on a list as a new entry, for instance a startup onto your pipeline.
create_note
Approval: see the ruleCreates a note and attaches it to a person, a company, an opportunity or a meeting.
create_reminder
Approval: see the ruleSets up a reminder, one-time or recurring, and can assign it to you or a colleague.
send_feedback
Approval: see the ruleSubmits feedback to Affinity about a missing capability or a limitation you ran into. The message goes to the publisher, not into your CRM.
upsert_list_entry_field_values
Approval: see the ruleCreates or updates several field values at once on a specific list entry, such as stage and deal lead.
Not documented (7)
7 toolsThe directory lists these seven names, but Affinity's documentation describes no tool by these exact names. This page will not guess from a name.
get_entity_field_values
This name appears on the directory's tool list, and that is all anyone publishes about it. Affinity's tool reference uses other names, and no Claude page covers it, so this page goes no further.
get_list_entries
Listed by name on the directory sheet, with no description, and absent under that exact name from Affinity's reference and from Claude's documentation. Reading a role into the name would be inventing it.
get_notes
No official text describes a tool by this exact name: Affinity's page documents neighbouring note tools, not this one, and Anthropic has no Affinity page. Only the name is public.
get_relationship_strengths
Affinity's reference talks about relationship tools under different names; nothing official is written about this exact one. The directory shows the name and stops there, with no source describing its output.
search_companies
Only its name is published, on the directory sheet. Affinity documents company searches under other names, so nothing official says what this one returns, how it filters or whether it only reads.
semantic_search
Here too, the directory gives a name and no description, and neither Affinity's tool pages nor Anthropic's help centre mention it. This page will not describe what no source describes, however tempting the name.
upsert_entity_field_value
Nearly identical to a tool Affinity documents, yet the exact name on the directory sheet appears in no official source. A one-letter difference is not proof, so this page states nothing about it.
What Claude asks before it acts
By default, Claude stops and asks for your go-ahead before any action it takes on an account for you. No source gives an Affinity tool its own rule, so that default covers the five writes.
On a Team or Enterprise workspace, owners can cap the connector for everyone: in its Configuration tab, Tool permission restrictions set each tool to Always allow, Ask or Block, grouped into read-only and write or delete tools. Affinity notes these restrictions do not reach Claude Code CLI, desktop extensions or the API. Claude works with your Affinity permissions, list access and field visibility included, and nothing more.
Which plans this works on
None of the 819 sheets in the official directory shows plan availability. The per-connector answer is published nowhere, and that is a real gap in the catalogue.
The general rule is published: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner switches the connector on for the organisation before members sign in. The publisher says something about Claude plans too, set against this rule in the limits section. For the current state, check the connector's sheet in the official directory.
Where this connector stops
A connector is not an automation. Claude calls these tools while it answers you: nothing starts when a meeting is logged, a relationship cools or a reminder falls due.
Only Affinity documents this connector; neither Claude's help centre nor Anthropic's developer docs have a page on it. Affinity's tool reference and the directory sheet do not list the same tools, which is why seven stay undocumented here. The list is an observed floor, not a promise. The partner badge is not a security audit, and Anthropic says on every sheet that it does not guarantee how a publisher's tools behave. Affinity adds that its server stores no CRM data and never sees your prompts, only the tool calls.
Which Claude plans can use the Affinity connector?
- Claude help centre, general connector rule ↗September 2026Remote connectors are open to all users; on Team and Enterprise, an Owner must switch each one on first.
- Affinity developer documentation, Claude page ↗September 2026The publisher states the Affinity connector is available on Free, Pro, Max, Team and Enterprise.
What this page followsNeither is outdated, and they agree. Anthropic's rule covers every connector; Affinity's line targets this one but comes from the publisher, not from Anthropic. Check the directory sheet from your own account before relying on either.
Need help connecting Affinity to Claude?
A person reads every message.
