CRM n8n nodes

CRM nodes connect n8n workflows to customer relationship management systems, so information from other parts of your business can become a contact, company, deal, activity, or follow-up task. Use this category to find n8n CRM nodes for creating and updating CRM records, finding existing ones, and keeping sales information in sync with the events that matter.

Available CRM nodes

• Attio n8n node (@nativeship/n8n-nodes-attio): search, create, update, upsert, and merge Attio records, manage lists, and work with tasks, notes, meetings, and activities. Connects with an Attio OAuth2 credential.
• Close n8n node (@nativeship/n8n-nodes-close): manage Close leads, contacts, opportunities, tasks, sales activities, and reports, including merging two leads. Connects with a Close API key or OAuth2.

Looking for prospecting, enrichment, or outreach instead of CRM records? See Sales & Lead Generation nodes, or browse all n8n node categories.

The current CRM listings cover common record actions such as creating, finding, and updating people, organizations, and deal records. Depending on the integration, a CRM node may also support upserting or merging records, managing lists, adding notes and activities, or working with opportunities and pipeline reports. For example, the Attio node can upsert and merge records, and the Close node can merge leads and create or update opportunities. Each CRM has its own data model and operations, so check the individual listing before you decide how the workflow should map its data.

What CRM nodes can help you do in n8n

Create or update contacts and companies

When a workflow receives customer or prospect details, a CRM node can create a new contact or organization record, or update an existing one with the latest information. The source could be a signup, an approved lead, a service interaction, or another business event. n8n can normalize the incoming fields before passing them to the CRM.

Use a stable identifier, such as an existing record ID or a well-defined matching field, to avoid creating duplicate contacts. If a node offers an upsert action, check which fields it uses to decide whether to update a record or create a new one. A match based on the wrong field can join unrelated people or companies.

Keep people, companies, and deals connected

CRM records are useful when their relationships are preserved. A contact may belong to a company, while a deal or opportunity may be linked to both a company and one or more people. A workflow can create or find the related records first, then pass their IDs into the next CRM action.

CRM systems do not all use the same structure. One may represent a company as a lead or account with contacts nested under it; another may store people, companies, and deals as separate objects. A deal may also be called an opportunity. Close, for example, creates contacts and opportunities on a lead, while Attio works with records of different objects, such as companies and people. Check the node's resource names and required relationship fields before mapping data between systems.

Update pipeline stages and sales details

Once a deal exists, a workflow may update its stage, owner, value, close date, or custom fields when those actions are available. That can keep a pipeline current after a form submission, a handoff, or a change in another connected system.

Before updating a deal, look up the record and confirm that the incoming event refers to the correct one. Preserve the CRM's identifiers and use its available status values. A workflow should not guess a pipeline stage from incomplete data.

Add notes, activities, and follow-up tasks

CRM integrations may also expose related work such as tasks, notes, meetings, calls, emails, or custom activities. These records give a team context for why a contact or deal changed and what should happen next.

For example, after a qualified lead enters a pipeline, n8n can add a note with the source information and create a follow-up task for an assigned owner. The exact activity types and fields depend on the CRM and the node.

Examples of CRM workflows in n8n

In an n8n CRM integration, the CRM node usually handles the record action while other n8n steps supply the event, prepare the data, and decide what happens next. Common patterns include:

1. Create a contact from an approved signup: map the submitted fields, search for an existing contact, then create or update the CRM record and link it to the right company.
2. Keep company records current: use a source update to find a company by a stable ID or domain, update selected fields, and leave unrelated CRM fields untouched.
3. Open or update a deal: find the related company and contact, then create a deal or update its stage and value when the incoming data meets your rules.
4. Record a customer interaction: add an activity or note to the correct contact or company and create a follow-up task for the next owner.
5. Sync selected CRM changes elsewhere: find the matching record in another workflow destination, map the required fields, and preserve the CRM record ID for later updates.

Run the first workflow with a small set of records. Inspect how the node handles missing fields, duplicate matches, custom attributes, and linked records before allowing it to update a larger part of the CRM.

Choose a CRM node that fits your data model

Start with the record you need to create or update. Then confirm that a node supports the relevant object, its required fields, and the relationships your workflow needs to preserve.

Before installing, check:

• Supported objects: Can it work with contacts or people, companies or accounts, and deals or opportunities?
• Available actions: Does it create, find, update, upsert, merge, or delete the records you need?
• Matching behavior: Which fields identify an existing record, and can the workflow keep its CRM ID for later changes?
• Relationships: Can you associate contacts with companies and deals with the correct people or organization?
• Custom fields: Does the node expose the fields your workspace uses, and what format do those fields expect?
• Authentication and permissions: Does it use OAuth or an API key, and does the connected account have permission to read and write the required records?
• Installation requirements: Review the listing for current verification and n8n compatibility details.

The current CRM listings use OAuth or API-key credentials depending on the integration: the Attio node uses an Attio OAuth2 credential, and the Close node accepts a Close API key or OAuth2. Give each credential only the access needed for the workflow, and test a read or lookup action before enabling record changes.

Install a CRM node in n8n

Both current CRM listings install from npm on self-hosted n8n:

1. In n8n, open Settings → Community Nodes and select Install.
2. Paste the package name from the listing, such as @nativeship/n8n-nodes-attio or @nativeship/n8n-nodes-close.
3. Add the node's credential, then run a read or lookup action first.

Only Owner and Admin users can install community nodes from npm. See n8n's community node installation docs for the GUI, manual, and environment-variable methods. If a node disappears after a restart or upgrade, see n8n community node not showing.

Provenance and verification

The current CRM listings are published with npm provenance. Provenance links a package release to its source and build, helping you inspect how it was produced. Read more in how to publish an n8n node to npm with provenance. Provenance is separate from n8n verification; it does not mean n8n has verified a node. Both current listings are marked for self-hosted n8n, so check each listing for its current verification and installation status. To see what verification involves, read how to get your n8n community node verified.

Build an n8n node for your CRM

If you build a CRM or customer-data service, your customers will ask whether you have an n8n integration. NativeShip turns your OpenAPI spec into an official, branded n8n community node, published under your own GitHub and npm accounts, and the same project covers Make, Zapier, and Activepieces.

• Unsure whether it's worth it? Read should your SaaS build an n8n integration?
• Wondering what can be generated from your spec? See generate an n8n node from an OpenAPI spec.
• Ready to start? Plans begin at $149 one-time. See pricing or try NativeShip.