Start with an Affinity API key (from your Affinity admin/settings), then add the Affinity node in n8n and create new credentials using that key. Next, test a simple workflow: trigger from a webhook or schedule, then “Get Person” or “Create Person” in Affinity. If your workflow also touches Gmail or Google Calendar, connect those accounts too. Once the test run returns real data, you can map fields, add filters, and turn the workflow on.

A lot, and the best wins are the boring ones. You can auto-create people and companies from form fills, enrich records from spreadsheets, and keep lists updated based on tags or pipeline stage. Log meeting notes from Google Calendar events, post deal updates to Slack, or push daily pipeline snapshots to Notion. You can also route new introductions to the right owner so follow-ups happen the same day, not next week.

Yes. n8n needs access to your Affinity workspace via an API key to read and write data.

Common setups include syncing contacts from Google Sheets, logging inbound emails from Gmail, and creating tasks or notifications when a deal stage changes. A practical limitation is data quality: if your source tools have duplicate contacts or inconsistent domains, you’ll see messy merges in Affinity unless you add matching rules. API rate limits can also matter for big backfills, so batch updates and schedule runs help. Finally, be mindful of permissions: the API key’s user role controls what your workflow can edit.