Unlocking Automation with n8n: A Complete Guide for CRM and Revenue Teams
n8n lets you build workflows visually, drop into code when you need to, and run them in n8n's cloud or on your own servers. This guide explains how n8n workflow automation works in 2026: the licence, cloud versus self-hosted, how executions are priced, how to connect Salesforce and HubSpot safely, and what a production-ready setup needs.
Key Takeaways
- n8n is a workflow automation platform: you connect trigger, app, logic and code nodes on a canvas, and each run of a workflow is an execution.
- It is fair-code, not open source. The self-hosted Community edition is free for internal business use under the Sustainable Use License; n8n Cloud and the Business and Enterprise plans are paid.
- Paid plans are priced by production executions, not by steps or users, so one long workflow costs the same as a short one.
- Salesforce and HubSpot both have built-in n8n nodes and triggers. Connect Salesforce through an External Client App and a dedicated integration user, and budget its daily API allocation.
- Production use needs an error workflow, retries, a fixed encryption key, sandbox testing and, as volume grows, queue mode.
What is n8n workflow automation? n8n is a platform for building automated workflows between apps, databases and APIs. You place nodes on a canvas, such as a trigger, a CRM action, a condition or a block of JavaScript or Python, and connect them. When the trigger fires, n8n runs the nodes in order. It can be used as n8n's hosted cloud service or installed on your own infrastructure.
We first published this guide in 2025. This version is rebuilt from n8n's current documentation, licence and pricing pages and from Salesforce's own documentation, checked in October 2026. It corrects figures that were out of date, removes results we could not source, and adds what CRM teams ask before they commit: licensing, hosting, execution costs, Salesforce and HubSpot authentication, error handling and governance. It is written for RevOps, sales operations, CRM admins and IT leaders at growing and mid-market companies, and it applies equally to enterprise teams evaluating n8n.
What Is n8n, and What Is It Used For?
n8n is a workflow automation tool that combines a visual builder with real code. Teams use it to move data between systems, react to events such as a new lead or a closed deal, call any REST API, and add AI steps. It sits between simple point-and-click connectors and custom integration code, and it can run in n8n's cloud or on your own servers.

Six terms cover most of what you need to read n8n's documentation:
| Term | What it means in n8n |
|---|---|
| Workflow | A collection of connected nodes that automates a process. It can branch, merge and loop. |
| Node | One step: a trigger, an app action (Salesforce, HubSpot, Slack), a logic step (IF, Merge, Loop) or a code step. |
| Trigger node | The node that starts a workflow: a webhook, a schedule, an app event, or another workflow calling it. Every production workflow needs one. |
| Credential | Stored authentication for a service, encrypted in n8n's database and selected on each node that uses it. |
| Expression | A JavaScript snippet that fills a node parameter from earlier data, such as the email address of the record that triggered the run. |
| Execution | One run of a workflow. Manual runs happen while you build; production runs start when a published workflow's trigger fires. |
Definitions follow n8n's key concept glossary. On integrations, n8n's own pages give different numbers: the homepage says more than 500 native integrations, and the integrations directory lists 2,000+ entries including partner-built ones. For CRM work, the more useful fact is that anything with a REST API can be reached through the HTTP Request node.
How Does an n8n Workflow Run, Step by Step?
A trigger starts the run, each node receives a list of items from the node before it, and the workflow ends by writing to a system, responding to the caller or notifying someone. Because nodes process every item they receive, a workflow that reads 200 leads handles all 200 without an explicit loop. Errors go to a separate error workflow you define.
Large workflows can be split into sub-workflows called with the Execute Sub-workflow node. n8n describes this as building "modular, microservice-like workflows", and it also helps when one workflow grows large enough to hit memory issues (sub-workflows). A shared "find or create account" sub-workflow, for example, can serve every lead source.
Should You Use n8n Cloud or Self-Host n8n, and What Does the Licence Allow?
Choose n8n Cloud if you want to start quickly without running infrastructure; choose self-hosting if you need full control over where data and credentials live, custom modules, or the free Community edition. Both run the same product and both support production use. Self-hosting moves patching, backups, monitoring and scaling onto your team.
| n8n Cloud | Self-hosted | |
|---|---|---|
| Setup | No installation; a 14-day trial with Pro features | Docker Compose, a one-line installer, or AWS, Azure, Google Cloud and other providers |
| Who runs it | n8n handles hosting, updates and scaling | Your team owns servers, the database, upgrades and backups |
| Cost | Paid plans priced by executions | Community edition free; Business and Enterprise paid by licence key |
| Code node | No external npm or Python libraries (crypto and moment are available) | External npm modules and allowlisted Python packages can be enabled |
| Best for | Teams without DevOps capacity, fast pilots | Data residency, internal-network systems, high volume, custom nodes |
Sources: n8n's guide to choosing how to use n8n, hosting documentation and Code node documentation.
Self-hosted editions
The free Community edition has "almost the complete feature set". Registering it with an email unlocks folders, debug in editor and custom execution data at no cost. It does not include projects, sharing of workflows and credentials, SSO, environments, Git version control, external secrets, log streaming or custom variables. Those need a Business or Enterprise licence key (compare editions). For a CRM team, the missing sharing feature matters most: on Community, only the instance owner and the creator can open a workflow or credential.
The licence in plain terms
n8n calls itself fair-code, not open source. Its source code is public, but the Sustainable Use License limits how it may be used. Paid n8n Cloud has its own terms; the licence below applies to self-hosted n8n.
Allowed. Run your own business processes on it, including CRM and revenue workflows. Run several instances. Build automations for clients on your instance as long as they cannot create or edit them. Use n8n behind the scenes in your product. Pay a partner to build, maintain and support workflows.
Not allowed without a commercial agreement. Hosting n8n as a service where your customers build workflows, letting external users configure workflows through your product (by UI, API, MCP or an AI agent), forking n8n into your own automation product, white-labelling it, or using licence-key features without a licence.
Sources: n8n's fair-code licence page and licence FAQ. n8n moved from Apache 2.0 with Commons Clause to the Sustainable Use License on 17 March 2022, and in doing so removed the earlier restriction on charging for consulting and support. If your use case is borderline, n8n asks you to email its licensing team before you build.
How Does n8n Pricing Work, and What Counts as an Execution?
Paid n8n plans are priced by monthly production executions, and one execution is one complete run of a workflow, however many steps it has. All plans include unlimited users, unlimited workflows and every integration. Test runs, sub-workflow runs and error-workflow runs do not count, so modular designs cost nothing extra.
| Plan | Hosting | Executions per month | Notable inclusions |
|---|---|---|---|
| Community edition | Self-hosted | No n8n fee | Core features; you pay only for infrastructure |
| Starter · $20/mo | n8n Cloud | 2,500 | 1 shared project, 5 concurrent executions |
| Pro · $50/mo | n8n Cloud | 10,000 | 3 shared projects, admin roles, workflow history |
| Business · $800/mo | Self-hosted | 40,000 | SSO and LDAP, environments, Git version control, queue mode |
| Enterprise · custom | Cloud or self-hosted | Custom | External secrets, log streaming, audit logs, SLA support |
Prices are per month billed annually, as shown on n8n's pricing page on 28 October 2026; check it before you budget, because plans change. The page also offers a Start-up Plan with 50% off Business for companies under 20 employees.
How executions are counted
- Schedule Trigger: one execution every time it fires, whatever the outcome. A workflow every 5 minutes is about 8,640 executions in a 30-day month.
- Polling triggers: one execution only when new data is found. Empty polls are free.
- Webhooks: one execution per inbound request that starts the workflow, including empty ones. Malformed requests that fail before the workflow starts are not counted.
- Not counted: manual test runs, sub-workflow runs (only the parent counts) and error-workflow runs.
The rules come from n8n's documentation on executions. Two design habits keep costs predictable: process records in batches inside one run rather than one webhook per record where the source allows it, and avoid tight schedules for data that changes once a day.
How Do You Connect n8n to Salesforce Securely?
Create an External Client App in Salesforce, authenticate n8n with OAuth2 or the JWT bearer flow as a dedicated integration user, and give that user only the objects and fields the workflows need. Then use the Salesforce node for records and SOQL, the Salesforce Trigger for record events, and the HTTP Request node with the same credential for anything else.
What the Salesforce node can do
| Area | Operations |
|---|---|
| Records | Create, upsert, get, get all, update and delete accounts, contacts, leads, opportunities, cases, tasks, attachments and custom object records; add notes; add leads and contacts to campaigns |
| Query | Run a SOQL query and return all results in one response |
| Flow | List flows and invoke a flow, so n8n can hand work to automation that lives in Salesforce |
| Documents and users | Upload a document; get users |
| Trigger events | Created or updated accounts, contacts, leads, opportunities, cases, tasks, attachments, users and custom objects |
From n8n's Salesforce node and Salesforce Trigger documentation. Custom fields are added under Additional Fields › Custom Fields.
Authentication and the integration user
- Use an External Client App for new connections. n8n's Salesforce credential guide notes that Salesforce is deprecating Connected Apps in favour of External Client Apps. Existing Connected Apps keep working.
- Pick OAuth2 or JWT. JWT suits server-to-server workflows: you upload a certificate to the app, enable the JWT bearer flow, and store the private key in n8n. Set the credential's environment to Sandbox or Production.
- Connect as a dedicated user. Salesforce recommends one user per integration for least privilege and traceability, and its Integration User licence restricts that user to API access. Our guide to Salesforce integration user licences covers the setup.
- Narrow the scopes where you can. n8n's setup example requests full access plus refresh tokens. Treat that as the maximum, and relay Salesforce's own policy advice from the same guide: expire refresh tokens after 90 days and pre-authorise only admin-approved users.
Budget Salesforce API calls
Every Salesforce node call uses the org's daily API allocation, which is shared by all integrations. Enterprise Edition gets 100,000 requests per 24 hours plus an amount per user licence, so an org with 15 Salesforce licences has 115,000 (Salesforce API request limits). Prefer one SOQL query over many single-record gets, use upserts instead of a search followed by a create, and batch large updates with the Loop Over Items node.
n8n or Salesforce Flow?
Keep automation that only touches Salesforce data inside Salesforce, in Flow, where it runs with the record, respects sharing and needs no API calls. Use n8n when the process crosses systems: a form tool, a warehouse, Slack, an ERP, an AI model. If your org still runs Workflow Rules or Process Builder, note that Salesforce stopped supporting both on 31 December 2025; they still run, but get no fixes, and Salesforce recommends migrating them to Flow (end of support notice). Our Salesforce Flow guide covers that side.
How Does n8n Work with HubSpot?
n8n has a HubSpot node for contacts, companies, deals, tickets, engagements and forms, and a HubSpot Trigger that reacts to record events through HubSpot webhooks. Authenticate the node with a HubSpot service key or OAuth2, and the trigger with a developer app. Plan triggers carefully, because HubSpot allows only one webhook at a time.
- Events available: companies, contacts, deals and tickets created, deleted or with a property changed, plus conversation events such as new messages (HubSpot Trigger).
- One active trigger: n8n warns that activating a second HubSpot Trigger stops the first, since each registers a new webhook and HubSpot allows only one. Route all HubSpot events through one trigger workflow, then call sub-workflows by event type.
- Credentials: n8n recommends a HubSpot service key for the node (in public beta at HubSpot), a developer API key for the trigger, or OAuth2. HubSpot's old API keys are deprecated, and private apps created in the HubSpot UI are now legacy (HubSpot credentials).
n8n is not a replacement for HubSpot's native Salesforce connector when the goal is a standard two-way sync of contacts, companies and deals. It is useful around that sync: enriching records before they reach either CRM, handling objects the connector does not map, or pushing data to systems neither CRM connects to. Our Salesforce and HubSpot integration services cover the core sync design.
Which n8n Nodes Should CRM Teams Learn First?
Learn six: Webhook, Schedule Trigger, HTTP Request, Code, Loop Over Items and Execute Sub-workflow. Together with the Salesforce and HubSpot nodes, they cover almost every revenue-operations workflow: receiving events, running jobs on a timetable, calling any API, transforming data, staying inside rate limits and reusing logic.
Webhook
Receives data when an event happens elsewhere. Separate test and production URLs, Basic, Header or JWT authentication, a 16MB default payload limit, and the option to return a response like an API.
Schedule Trigger
Runs a workflow at fixed intervals or times, like cron. It follows the workflow's or instance's timezone, so set it explicitly for nightly jobs.
HTTP Request
Calls any REST API, can import a curl command, and can reuse a predefined credential such as Salesforce's for operations the app node lacks.
Code
JavaScript or Python, run once for all items or once per item. Native Python runs on task runners and is stable from n8n 2; the older Pyodide mode was removed in 2.0.
Loop Over Items
Processes items in batches of a size you set. Use it to stay within API rate limits or to page through results; most other nodes already handle lists without it.
Execute Sub-workflow
Calls another workflow with defined inputs. Sub-workflow runs do not count as executions, and you can restrict which workflows may call each one.
Details from n8n's documentation for the Webhook, Schedule Trigger, HTTP Request and Loop Over Items nodes. n8n also offers an AI Agent node that connects a chat model to tools, including the Salesforce node itself; our n8n AI agent guide covers that side.
Two security settings deserve attention. Credentials have an "Allowed HTTP Request Domains" option, so a Salesforce credential can be restricted to your Salesforce domain when used in an HTTP Request node. And a production webhook URL can be called by anyone who has it unless you add authentication: always set it on a production webhook and validate the payload before it touches the CRM.
How Do You Handle Errors in n8n Workflows?
Combine three layers: node settings that retry or route failures, an error workflow that alerts someone when a run fails, and execution history to inspect and re-run. Without them, a CRM workflow that fails at 02:00 fails silently, and the first sign is a missing lead or a wrong report days later.
| Tool | What it does | Use it for |
|---|---|---|
| Retry On Fail | Reruns a failed node until it succeeds | Timeouts and temporary API errors from Salesforce, HubSpot or enrichment APIs |
| On Error: Continue (using error output) | Passes the failed item down a separate error branch instead of stopping | Logging rejected records, such as validation-rule failures, while the rest of the batch continues |
| Error workflow | A workflow starting with the Error Trigger, set in each workflow's settings, that receives the workflow name, failing node, error message and execution link | One shared alert to Slack, email or a ticket for every production workflow |
| Stop And Error | Fails the run on purpose under a condition you define | Business rules, such as a webhook arriving without an email address |
| Executions list | History of runs with their data, which you can load back into the editor | Debugging and replaying a failed run after a fix |
From n8n's documentation on error handling, the Error Trigger and node settings. One caution from the same pages: the Error Trigger only fires for automatic runs, so test your error workflow with a scheduled or webhook run, not a manual one. Retention also matters: on n8n Cloud, execution logs are kept for 7 days on Starter and 30 days on Pro, so export what auditors need.
What Does a Secure, Scalable n8n Setup Need?
Protect the encryption key, keep secrets out of workflows, give people roles rather than shared logins, separate development from production, and scale with queue mode when one instance is not enough. Several of these controls require Business or Enterprise, so decide which you need before choosing a plan.
| Control | How it works | Availability |
|---|---|---|
| Credential encryption | n8n encrypts credentials with a key created on first launch. Set N8N_ENCRYPTION_KEY yourself and back it up, because every instance and worker needs it to read stored credentials | All editions |
| Roles (RBAC) | Instance roles (Owner, Admin, Member) plus per-project roles; custom roles on Enterprise | Project roles: all Cloud plans; self-hosted Registered Community and above |
| SSO | SAML or OIDC sign-in | Cloud Enterprise; self-hosted Business and Enterprise |
| Environments and Git | Instances linked to Git branches, so workflows move from development to production by push and pull | Business and Enterprise |
| External secrets | Credentials read from AWS Secrets Manager, Azure Key Vault, GCP Secrets Manager, HashiCorp Vault, 1Password or Infisical | Enterprise |
| Log streaming and audit logs | Events sent to your own logging and alerting tools | Enterprise |
| Queue mode | A main instance queues executions in Redis and worker instances run them; add workers to scale. Use PostgreSQL, not SQLite | Self-hosted (included in Community) |
Sources: n8n's documentation on the encryption key, RBAC, SSO, source control and environments, external secrets, log streaming and queue mode. In queue mode, every worker needs the same encryption key as the main instance, or it cannot read credentials.
What Can CRM and Revenue Teams Automate with n8n?
The best first workflows cross system boundaries, run often, and follow clear rules. Lead capture, enrichment, routing alerts, CRM-to-warehouse syncs and finance handoffs fit well. Each pattern below uses only documented nodes. Measure your own baseline first, such as minutes per record or errors per week, so you can show the result.
| Workflow | Trigger | Steps | Watch for |
|---|---|---|---|
| Web lead to Salesforce | Webhook from a form tool | Validate fields → SOQL search for the account → upsert the lead → Slack alert to the owner | Webhook authentication; upsert key to stop duplicates |
| Lead enrichment | Salesforce or HubSpot trigger on create | HTTP Request to an enrichment API → update company fields → flag low-fit leads | Enrichment vendor rate limits; which fields the CRM owns |
| Closed-won handoff | Opportunity updated to Closed Won | Create the customer in the finance or project tool → post a kickoff message → write the external ID back | Retries and an error branch, so no deal is lost |
| Nightly CRM export | Schedule Trigger at 02:00 | SOQL query of changed records → Loop Over Items → load to the warehouse → summary email | API allocation; timezone setting; execution duration limits on Cloud |
| Support email triage | Email trigger | AI Agent classifies the request → create a Salesforce case → route by category | Human review before replies go out; data sent to the model |
n8n's own customer stories show the scale one workflow can reach. In n8n's published Delivery Hero case study, an IT team replaced a manual account-recovery process, about 800 requests a month, with a single workflow: the employee's manager approves, and n8n calls Okta, Jira and Google to restore access. Average lockout time fell from 35 to 20 minutes, which n8n reports as 200 hours a month saved. The same pattern of approval followed by API calls applies to revenue processes such as discount approvals and account handoffs.
When Is n8n the Right Automation Tool, and When Is It Not?
n8n fits teams that want visual building with code when needed, predictable execution-based pricing, and the option to self-host. It fits less well when nobody will own the workflows, when the automation lives entirely inside one CRM, or when you need a fully managed enterprise integration platform with vendor-run connectors and support for every system.
Choose n8n when workflows span several systems; you have someone comfortable with APIs, JSON and a little JavaScript; data residency or internal-network access makes self-hosting attractive; long multi-step workflows would be expensive on per-step pricing; or you want AI steps inside the same tool.
Look elsewhere when the process stays inside Salesforce (use Flow) or HubSpot (use HubSpot workflows); business users must build without technical support; you plan to let your own customers build workflows (the licence needs a commercial agreement); or the integration needs an enterprise iPaaS with managed connectors and API management.
Twopir Consulting implements several integration platforms, including n8n, Zapier, Workato, Celigo and MuleSoft, so the choice comes from the process rather than a preferred tool. For comparisons, see our guides to Zapier and Make.com, and our Workato integration services.
How Should You Roll Out n8n for Your CRM?
Start with one workflow that matters, built against a Salesforce or HubSpot sandbox, with error handling and an owner from day one. Prove it in production, then standardise the pieces you will reuse: credentials, sub-workflows, naming and alerting. Scale the platform only once workflow volume or team size requires it.
| Phase | Decisions and work | Done when |
|---|---|---|
| 1. Choose | Cloud or self-hosted; edition or plan; licence check for your use case; who owns the platform | A written decision with expected monthly executions |
| 2. Prepare | Integration user and permission set in Salesforce; External Client App; HubSpot service key; encryption key stored safely; sandbox credentials | Credentials test successfully in n8n |
| 3. Build the first workflow | Trigger, validation, upsert, retries, error branch, shared error workflow | Test records flow correctly and a forced failure raises an alert |
| 4. Go live | Production credentials; authenticated webhook; publish; monitor executions and API usage | A full week without unhandled failures |
| 5. Standardise and scale | Naming conventions, shared sub-workflows, documentation, roles; environments and queue mode as volume grows | A second person can change a workflow safely |
Checklist for every production workflow
- A clear name, a description and a named owner.
- Credentials named by system, environment and purpose, restricted to the domains they need.
- Upserts or duplicate checks before any create in the CRM.
- Retry On Fail on API nodes, an error branch for rejected records, and the shared error workflow set.
- Batching for large volumes, and a check of the Salesforce API allocation.
- Tested in a sandbox with real-looking data, including empty and malformed inputs.
The Bottom Line
n8n gives CRM and revenue teams a flexible way to automate across systems, with costs tied to completed runs and the option to keep everything on their own infrastructure. The work that makes it dependable is the same as for any integration: a secure connection, clear data ownership, error handling and an owner. Twopir Consulting designs and builds CRM integrations on n8n and other platforms for Salesforce and HubSpot, from the integration user and data mapping to monitoring and support.
- 1
Check the licence and pick Cloud or self-hosted based on who will run the platform.
- 2
Estimate monthly executions from your triggers before choosing a plan.
- 3
Connect Salesforce through an External Client App and a dedicated integration user.
- 4
Give every production workflow retries, an error branch and a shared error workflow.
- 5
Back up the encryption key, and add roles, environments and queue mode as you grow.
Plan Your First n8n Workflows with Us
Tell us which processes cross your CRM today and where data gets re-keyed. We will recommend whether n8n fits, how to host it, and which workflows to build first.
Schedule a Discovery CallFrequently Asked Questions
Not in the OSI sense. n8n's source code is public, but it is released under the Sustainable Use License, which limits use to internal business, personal or non-commercial purposes. n8n calls this model fair-code. Enterprise features in files marked .ee. are under the separate n8n Enterprise License.
The self-hosted Community edition is free to use for your own internal business processes, and you pay only for the infrastructure that runs it. n8n Cloud and the self-hosted Business and Enterprise plans are paid. Offering n8n to your own customers so they can build workflows needs a commercial agreement with n8n.
One complete production run of a workflow, regardless of how many steps it has. A Schedule Trigger counts every time it fires, a webhook counts every request that starts the workflow, and a polling trigger counts only when it finds new data. Manual test runs, sub-workflow runs and error-workflow runs do not count.
Yes. n8n has a Salesforce node for creating, updating, upserting and deleting records, running SOQL queries and invoking flows, and a Salesforce Trigger for record events. It authenticates with OAuth2 or JWT. n8n recommends an External Client App for new connections, and Salesforce recommends a dedicated integration user.
Yes. The HubSpot node works with contacts, companies, deals, tickets, engagements and forms, and the HubSpot Trigger reacts to record events through HubSpot webhooks. Only one HubSpot Trigger can be active at a time, so route all HubSpot events through one trigger workflow and branch from there.
Use n8n Cloud if you want to start quickly and have no one to run servers. Self-host if you need control over data location, access to internal systems, external code libraries, or the free Community edition, and you have the skills to manage upgrades, backups, the database and the encryption key.
No. Keep automation that only touches Salesforce data in Flow, where it runs inside Salesforce and uses no API calls. Use n8n for processes that cross systems. Workflow Rules and Process Builder lost Salesforce support on 31 December 2025, and Salesforce recommends moving them to Flow, not to an external tool.
Each node can retry on failure, stop the workflow, continue, or send failed items down an error output. Each workflow can also name an error workflow that starts with the Error Trigger and receives the failing node and message, so one shared workflow can alert your team in Slack or by email.
Twopir Consulting
Twopir Consulting helps growing and mid-market companies solve complex CRM, integration, and business system challenges. We implement, rescue, optimize, and integrate complex CRM and revenue systems, including integrations built on n8n, Zapier, Workato, Celigo and MuleSoft, for 500+ clients over 12+ years.