Affinity – Town Docs

Affinity

Connect Affinity and your assistant can keep your deal flow and relationships current — search companies, people, and opportunities, read lists, notes, and relationship strength, and log interactions or update records — so your CRM stays fed and its context shows up in your prep and follow-ups.

Everything runs as you: your assistant can only see or change what your Affinity account already allows. Updates and deletions to existing records are held for your approval by default; new notes, logged interactions, and newly created records write to Affinity without a prompt — switch the connection to approval-required if you want those reviewed too.

What’s included

With Affinity connected, your assistant can:

Connecting Affinity

  1. Go to Integrations
  2. Find Affinity and click Connect
  3. Create an Affinity API key (in Affinity: Settings → Manage apps → Create), then paste it into Town’s token field
  4. Return to Town

Affinity connects with an API key, not a one-click sign-in. Create the key in Affinity and paste it into Town — Town connects through Affinity’s official MCP server (mcp.affinity.co). API access requires an Affinity Scale, Advanced, or Enterprise plan. Your assistant is limited to what your Affinity permissions already allow, and you can revoke the key anytime from Affinity.

What your assistant can do

Capability What it does Makes changes?
Search companies Find companies matching a query No
Search people Find people matching a query No
Search opportunities Find deals in your pipeline No
Read lists & entries Read lists, saved views, and their entries No
Read fields & notes Read record fields, notes, and meetings No
Relationship strength Find the warmest path to a person or company No
Log an interaction Record a meeting or touchpoint on a record Yes
Create a note Add a note to a company, person, or opportunity Yes
Create records Add a company, person, or opportunity Yes
Update records Update list entries, fields, and opportunities Yes
Set reminders Create or update a follow-up reminder Yes

Use cases

Deal-flow prep

Walk into every meeting with the history:

Keep the CRM current

Turn what happened into logged activity:

Relationship recall

Answer questions across your network:

Follow-ups

Never leave a warm intro hanging:

Example routine

A routine that keeps Affinity current after every meeting, triggered when a founder or LP meeting ends:

When a founder or LP meeting ends:
1. Read the meeting notes
2. Find the matching company in Affinity
3. Log the interaction and update the list entry (stage, next step)
4. Hold the changes for my approval before they're written

Best practices

Turn on approval-required if you want every write reviewed. By default, only updates and deletions to existing records are held for approval — new notes, logged interactions, and newly created records go straight into Affinity. Since it all lands in the pipeline your partners rely on, switch the connection to approval-required if you want a look before anything is written.

Match your list and field names. When updating list entries, use the exact list and field names from Affinity so changes land in the right place.

Affinity stays your system of record. Town keeps it fed and puts it to work — it doesn’t replace working in Affinity.

Troubleshooting

Can’t connect

Can’t find records

Update fails