AFFINITY n8n INTEGRATION: AUTOMATE AFFINITY WITH N8N
AFFINITY N8N INTEGRATION: AUTOMATE AFFINITY WITH N8N
Need help automating Affinity with n8n?
Our team will get back to you in minutes.
Why automate Affinity with n8n?
The Affinity n8n integration gives you access to 1 trigger monitoring over 20 different events and 16 actions covering people, organizations, lists, and list entries. This means you can build sophisticated automations that react to virtually any change in your Affinity workspace and take action across hundreds of other applications.
Significant time savings is the most immediate benefit. Instead of manually updating spreadsheets when deals move through your pipeline, or copying contact information between tools, n8n handles these repetitive tasks automatically. Your team can focus on building relationships rather than managing data. Improved responsiveness comes naturally when your workflows trigger instantly—the moment a new organization is created in Affinity, your sales team can receive a Slack notification, a task can be created in your project management tool, and an enrichment workflow can pull additional company data. Zero oversight means every single event is captured: every new person, every field update, every list entry deletion triggers your automation 24/7, ensuring nothing falls through the cracks.
Here's what teams are building with the Affinity n8n integration: automatically creating Affinity organizations when companies sign up through your website, syncing deal stages with your finance tools, enriching new contacts with data from Clearbit or LinkedIn, sending personalized follow-up sequences when opportunities reach specific stages, and maintaining a single source of truth across Affinity, your CRM, and your communication tools.
How to connect Affinity to n8n?
! 1 stepHow to connect Affinity to n8n?
- 01
Add the node
Search and add the node in your workflow.
TIP💡 TIP: Create a dedicated API key for n8n rather than reusing existing keys. This way, if you ever need to revoke access or troubleshoot, you can do so without affecting other integrations. Label your keys clearly in Affinity's settings so you remember which key connects to which service.- 01
Need help automating Affinity with n8n?
Our team will get back to you in minutes.
Affinity triggers available in n8n
01 Trigger 01Affinity Trigger
The Affinity Trigger is your gateway to event-driven automation. This powerful webhook-based trigger monitors your Affinity workspace and fires your workflow the instant specific events occur—whether that's a new person being created, a field value being updated, or an opportunity being deleted.
What makes this trigger particularly versatile is its comprehensive event coverage. You can listen for changes across seven different resource types: field values, fields, files, list entries, lists, notes, opportunities, organizations, and people. Each resource type supports relevant lifecycle events (created, updated, deleted), giving you granular control over exactly when your automations should run.
Configuration parameters:
- Credential to connect with: Select your stored Affinity credentials from the dropdown. This parameter is required and establishes the authenticated connection between n8n and your Affinity workspace.
- Events: Choose which specific events should trigger your workflow. Available events include field_value.created, field_value.updated, field_value.deleted, field.created, field.updated, field.deleted, file.created, file.deleted, list_entry.created, list_entry.deleted, list.created, list.updated, list.deleted, note.created, note.updated, note.deleted, opportunity.created, opportunity.deleted, organization.created, organization.updated, organization.deleted, person.created, person.updated, and person.deleted. This checkbox list is required, and you can select multiple events to monitor simultaneously.
Typical use cases: Trigger a Slack notification whenever a new organization is created in Affinity, start an email enrichment workflow when a new person is added, update your data warehouse when list entries change, log all note additions to a central documentation system.
When to use it: Deploy this trigger whenever you need real-time reactions to changes in your Affinity data. It's particularly valuable for maintaining data synchronization across tools, alerting team members to important updates, and initiating multi-step workflows based on CRM activities.
Affinity actions available in n8n
01 Action 01Get a list
This action retrieves detailed information about a specific list from your Affinity account. Use it when you need to fetch list metadata, verify a list exists, or gather list properties before performing other operations.
Key parameters: Credential to connect with (dropdown to select your Affinity authentication credentials, required), Resource (automatically set to 'List'), Operation (automatically set to 'Get'), and List ID (text field where you enter the unique identifier of the list you want to retrieve, required).
Use cases: Verify list existence before adding entries, retrieve list configuration for conditional logic, pull list details for reporting dashboards.
02 Action 02Get many lists
This action fetches multiple lists from your Affinity workspace at once, perfect for building dashboards, generating reports, or when you need to iterate through all your lists programmatically.
Key parameters: Credential to connect with (select your Affinity account credentials, required), Resource (preset to 'List'), Operation (preset to 'Get Many'), Return All (toggle switch to fetch all available lists regardless of limits, optional, defaults to off), and Limit (numeric input specifying the maximum number of lists to return, optional).
Use cases: Generate a master index of all lists for documentation, build a list selector in a custom interface, audit your Affinity workspace structure.
03 Action 03Get many list entries
Retrieve multiple entries from a specific list in bulk. This action is essential for data exports, synchronization tasks, and when you need to process list data in batches.
Key parameters: Credential to connect with (your Affinity credentials, required), Resource (set to 'List Entry'), Operation (set to 'Get Many'), List Name or ID (specify which list to pull entries from, accepts expressions for dynamic values, required), Return All (toggle to retrieve every entry in the list, optional), and Limit (set the maximum number of entries to fetch with default shown as 5, optional).
Use cases: Export deal pipeline data to a spreadsheet, sync list entries with an external database like Airtable, batch process entries for data enrichment.
04 Action 04Get a list entry
Fetch a single, specific entry from a list when you need detailed information about one particular record. Ideal for lookup operations and when processing data item by item.
Key parameters: Credential to connect with (Affinity authentication selection, required), List Name or ID (the list containing the entry you want, required), and List Entry ID (the unique identifier of the specific entry to retrieve, required).
Use cases: Look up deal details when processing a webhook, verify entry data before updates, retrieve full entry information for detailed notifications.
05 Action 05Create an organization
Add a new organization record to your Affinity workspace. This action is perfect for automatically populating your CRM when new companies are identified through forms, website signups, or external data sources.
Key parameters: Credential to connect with (your Affinity account, required), Name (the organization name to create, text input supporting expressions for dynamic values, required), Domain (the organization's website domain, optional but recommended for enrichment features), and Additional Fields (expandable section for any extra properties, optional).
Use cases: Create organizations from website form submissions, add companies discovered through lead generation tools, sync organization data from other CRMs like HubSpot.
06 Action 06Delete a list entry
Remove a specific entry from a list. Use this action for cleanup operations, archiving workflows, or when entries need to be removed based on certain conditions.
Key parameters: Credential to connect with (Affinity credentials, required), List Name or ID (identifies which list contains the entry, required), and List Entry ID (the unique identifier of the entry to delete, required).
Use cases: Remove closed deals from active pipelines, clean up duplicate entries automatically, archive entries based on date conditions.
07 Action 07Create a list entry
Add a new entry to a specified list, linking an entity (person or organization) to that list. This is fundamental for pipeline management and tracking relationships through stages.
Key parameters: Credential to connect with (your Affinity account, required), List Name or ID (the target list for the new entry, required), Entity ID (the ID of the person or organization to add to the list, required), and Additional Fields (extra properties for the entry, optional).
Use cases: Add qualified leads to your sales pipeline, move organizations through workflow stages, track new contacts in specific campaigns.
08 Action 08Delete an organization
Permanently remove an organization from your Affinity database. Exercise caution—this action is irreversible and will remove associated data.
Key parameters: Credential to connect with (Affinity authentication, required) and Organization ID (the unique identifier of the organization to delete, required).
Use cases: Remove test data during development, clean up organizations marked for deletion in another system, automate data hygiene processes.
09 Action 09Get many organizations
Retrieve multiple organization records in a single operation. Essential for bulk data operations, reporting, and cross-system synchronization.
Key parameters: Credential to connect with (your credentials, required), Return All (toggle to fetch all organizations, optional), Limit (maximum number to retrieve with default 5, optional), and Options (additional filtering parameters, optional).
Use cases: Export organization data for analysis, synchronize with external databases, build organization directories.
10 Action 10Get an organization
Retrieve detailed information about a single organization by its ID. Perfect for lookup operations and when you need complete organization data.
Key parameters: Credential to connect with (Affinity credentials, required), Organization ID (the specific organization's unique identifier, required), and Options (additional properties, currently limited, optional).
Use cases: Look up organization details for notifications, verify organization data before updates, enrich outbound communications with company info.
11 Action 11Create a person
Add a new person record to your Affinity workspace. This action is essential for automatically capturing contacts from various sources.
Key parameters: Credential to connect with (your Affinity account, required), First Name (the person's first name, required), Last Name (the person's last name, required), Additional Fields (extra properties like phone numbers and titles, optional), and Emails (add one or more email addresses, optional but recommended).
Use cases: Create contacts from webinar registrations, add people from business card scanning apps, sync contacts from email tools.
12 Action 12Update an organization
Modify existing organization data in Affinity. Use this to keep organization records current as information changes or when enriching data from external sources.
Key parameters: Credential to connect with (Affinity credentials, required), Organization ID (which organization to update, required), and Update Fields (click 'Add Field' to specify which properties to change, optional but necessary for actual updates).
Use cases: Update company information from enrichment services, sync changes from other CRM systems, batch update organization statuses.
13 Action 13Update a person
Modify existing person records with new or corrected information. Crucial for maintaining accurate contact data across your systems.
Key parameters: Credential to connect with (your credentials, required), Person ID (the unique identifier of the person to update, required), Result (define output format, required), and Emails (update or add email addresses, optional).
Use cases: Correct contact information from form updates, sync person data from HR systems, update contact details after data enrichment.
14 Action 14Get Many
A flexible action for retrieving multiple records of a specified resource type. Particularly useful for person records with additional filtering options.
Key parameters: Credential to connect with (Affinity authentication, required), Resource (select the resource type such as 'Person', required), Operation (set to 'Get Many', required), Return All (toggle for complete data retrieval, optional), Limit (maximum records to return with default 5, optional), and Options (additional configuration parameters, optional).
Use cases: Batch retrieve person records, export data for reporting, build contact lists for outreach.
15 Action 15Get a person
Retrieve complete details about a specific person using their unique identifier. Essential for lookup operations and detailed contact information needs.
Key parameters: Credential to connect with (your Affinity credentials, required), Person ID (the unique identifier of the person, required), and Options (additional properties, currently limited, optional).
Use cases: Look up contact details for personalized communications, verify person data before automated outreach, retrieve full profiles for detailed reports.
16 Action 16Delete a person
Permanently remove a person record from your Affinity database. Use carefully—this action cannot be undone.
Key parameters: Credential to connect with (Affinity account credentials, required) and Person ID (the identifier of the person to remove, can be a fixed value or dynamic expression, required).
Use cases: Remove contacts who've requested data deletion, clean up test records, automate compliance-related data removal.
Build your first workflow with our team
Drop your email and we'll send you the catalog of automations you can ship today.
- Free n8n & Make scenarios to import
- Step-by-step setup docs
- Live cohort + community support
Frequently asked questions
Is the Affinity n8n integration free?
The Affinity n8n integration itself is completely free to use—there are no additional costs for the connector. However, you'll need active subscriptions to both platforms: an Affinity account (which includes API access on their paid plans) and either a self-hosted n8n instance or an n8n Cloud subscription. Self-hosting n8n is free and open-source, while n8n Cloud offers managed hosting with various pricing tiers. Your Affinity plan must include API access, which is typically available on Professional and Enterprise tiers. Check both platforms' current pricing pages for the most accurate information.What data can I sync between Affinity and n8n?
The Affinity n8n integration gives you access to four primary resource types: People (create, read, update, delete contact records), Organizations (manage company records with names and domains), Lists (retrieve list metadata and configurations), and List Entries (add, retrieve, and delete entries that connect people or organizations to lists). The trigger additionally monitors field values, fields, files, notes, and opportunities. This means you can build comprehensive automation workflows that keep your relationship data synchronized with virtually any other application in your tech stack, from CRMs and email platforms to spreadsheets and data warehouses.How long does it take to set up the Affinity n8n integration?
Most users can complete the initial setup in under 5 minutes. Generating your API key in Affinity takes about 30 seconds, and configuring the credentials in n8n is equally quick. Building your first working workflow typically takes an additional 10-15 minutes, depending on complexity. The trigger-based webhooks are automatically configured by n8n, so you don't need to manually set up webhook endpoints in Affinity. For teams already familiar with n8n, expect even faster setup times. The most time-consuming part is usually planning your automation logic rather than the technical configuration itself.
