CRM Automation: HubSpot, Pipedrive and Zoho CRM in a Node Comparison

Many sales teams maintain leads, deals and contacts in parallel across multiple systems, and that is exactly where most everyday friction occurs. For the three most common CRM systems, HubSpot, Pipedrive and Zoho CRM, n8n provides its own app node for each, which creates, updates or retrieves the most important records directly from the workflow, without a single line of code being necessary.

However, the feature scope differs noticeably between the three nodes, and knowing in advance which resources and operations are available in each case helps plan more realistic workflows. This article compares the three native n8n nodes based on the official documentation and shows typical CRM automations that can be implemented directly with them. As of: July 2026.

What can the HubSpot node in n8n do?

The HubSpot node covers seven resources according to the n8n documentation and is therefore particularly suited to marketing and sales processes that are closely linked with forms and lists.

• Contact: create, update, delete, retrieve contacts individually or in bulk, and search them and read recently changed records.
• Contact List: add contacts to lists or remove them, for example for targeted campaigns.
• Company: create, delete, retrieve company records and search them by domain.
• Deal: full CRUD operations plus search for recently created or changed deals.
• Engagement: create, retrieve or delete activities such as notes or calls.
• Form: read form fields and submit form data.
• Ticket: create, update, retrieve and list support tickets.

For authentication, the HubSpot credentials documentation names three ways: a service key for the HubSpot node, a developer API key specifically for the HubSpot trigger node, and OAuth2. The classic API key method is considered deprecated by HubSpot itself, but still appears in n8n for compatibility reasons.

What does the Pipedrive node cover?

The Pipedrive node is structured more granularly and cleanly separates deal-related sub-resources from the main object.

• Activity: create, update, delete, retrieve and list activities.
• Deal: create, duplicate, update, delete, search, retrieve and list deals.
• Deal Activity: retrieve all activities for a specific deal.
• Deal Product: add, remove, update and retrieve products within a deal.
• File: create, delete, download and retrieve files.
• Lead: create, update, delete, retrieve and list leads.
• Note: create, update, delete, retrieve and list notes.
• Organization: create, update, delete, search, retrieve and list organizations.
• Person: create, update, delete, search, retrieve and list persons.
• Product: retrieve all products.

This division into Deal, Deal Activity and Deal Product pays off as soon as a workflow needs to maintain not only the deal itself but also the line items or activities linked to it, for example when automatically adding products to a quote.

What feature scope does the Zoho CRM node offer?

The Zoho CRM node supports ten resources according to the documentation: Account, Contact, Deal, Invoice, Lead, Product, Purchase Order, Quote, Sales Order and Vendor. For most of these resources, the same six operations are available: Create, Upsert, Delete, Get, Get Many and Update. For the Lead object, there is additionally an operation for retrieving the field definitions.

Particularly useful for automations is the Upsert operation, which is available for all ten resources: instead of having to check beforehand whether a record already exists, n8n either creates it new or updates the existing one, depending on whether a match is found. This significantly reduces the number of nodes needed in many sync workflows.

Node comparison at a glance

• Resource count: HubSpot offers seven, Pipedrive ten (including the deal sub-resources), Zoho CRM ten object types.
• Upsert: Zoho CRM offers Upsert natively for all ten resources; HubSpot and Pipedrive tend to work via separate create and update operations plus search.
• Trigger node: HubSpot and Pipedrive each come with their own trigger node that reacts to events such as new contacts or deal changes. For Zoho CRM there is no dedicated n8n trigger node; here the connection usually runs via polling or via Zoho's own webhooks combined with the generic webhook node.
• Sales vs. support focus: HubSpot additionally covers marketing and support processes with Form and Ticket, while Pipedrive and Zoho CRM focus more strongly on the classic sales process including lead, deal and linked documents such as quotes and invoices.
• Extensibility: If an operation is missing, the HTTP Request node can be chained with the same credential in all three systems to address the respective REST API directly.

Typical CRM automation workflows

Lead capture from forms and landing pages

A webhook or form trigger receives new prospects, a Function node cleans up the fields, and then the respective CRM node creates the lead or contact. In Zoho CRM, the Upsert operation directly handles duplicate checking; for HubSpot and Pipedrive, a search by email address beforehand is recommended.

Deal synchronization between two systems

If a company switches from Pipedrive to HubSpot or maintains both systems in parallel, a workflow periodically reconciles deal status, amount and close date. The Pipedrive trigger supplies the change, an IF node checks its relevance, and the HubSpot node updates the matching deal.

Automatic invoice and quote creation

As soon as a deal in Zoho CRM reaches the status "won", a workflow automatically creates a Quote or Sales Order via the corresponding Zoho CRM node and attaches the associated products from the deal, instead of transferring them manually.

Escalation for support tickets

The HubSpot node creates or updates tickets, while a parallel branch in the workflow automatically sends a message to the team in the case of high priority, for example via email or chat. This way, critical customer feedback does not remain unprocessed for days.

With n8n automation from NordFlux, such CRM workflows are set up self-hosted, so customer data does not run through third-party cloud instances and you retain full control over data flow and error handling.

Frequently asked questions

Which node is best suited for pure lead capture?

For simple lead capture without duplicate checking, the Zoho CRM node is the most straightforward thanks to its Upsert operation, because creating and updating happen in one step. HubSpot, on the other hand, scores as soon as the leads come directly from forms, since the Form resource type brings its own functions for this. Pipedrive is the right choice if the lead should be managed as a separate object from the contact from the outset.

Can I combine multiple CRM systems in a single workflow?

Yes, n8n allows multiple app nodes from different providers to be chained together within the same workflow. A typical example is a trigger from Pipedrive that, after a check, additionally creates a record in Zoho CRM or HubSpot, for instance during a migration phase between two systems.

What do I do if a required operation is missing from the node?

If none of the three nodes covers a desired operation, the HTTP Request node can be used with the same stored credential to address the respective REST API directly. This is possible with all three systems and is explicitly mentioned in the respective node documentation as a way to handle missing functions.

Do I necessarily need OAuth2 for HubSpot?

No, according to the documentation, a service key is also sufficient for the regular HubSpot node, with OAuth2 as the alternative to it. For the separate HubSpot trigger node, however, a developer API key is provided, and this cannot be replaced by the service key.

Is there also a dedicated trigger node for Zoho CRM in n8n?

No, unlike HubSpot and Pipedrive, n8n currently does not provide a dedicated trigger node for Zoho CRM. Incoming events can instead be mapped via a time-scheduled polling workflow with the Zoho CRM node, or via Zoho's own webhooks in combination with the generic webhook node.