16 min read

30 Best n8n Community Nodes (2025)

Hero image for 30 Best n8n Community Nodes (2025)
Table of Contents

Why community nodes

What you’ll learn:

  • How n8n community nodes expand integrations fast
  • How to choose safe, well maintained nodes
  • How to install, pin versions, and avoid risks

Callout: Community nodes turn n8n into a broad integration surface. In 2025 you can wire most APIs, ship faster, and avoid vendor lock‑in while keeping costs in check

A quick lens for busy builders:

  • Active maintenance with recent releases and resolved issues
  • Raw HTTP fallback so you are never blocked
  • Pin versions in prod and update on staging first

Built‑in vs community at a glance:

AspectBuilt‑inCommunity
UpdatesWith n8n releasesIndependent, faster cadence
CoveragePopular, generic APIsLong‑tail APIs, niche features, AI tools
RiskLower, vetted by coreVaries, check maintenance and code
Escape hatchMore opinionatedMany expose raw HTTP

Install in two minutes:

  1. Open n8n - Settings - Community Nodes - Install
  2. Search the service name (for example, “HubSpot”, “Zendesk”, “Ollama”)
  3. Grant permissions and pin the version for revenue or ops workflows

Global gotchas to avoid:

  • OAuth vs API keys: scopes define access. Create least‑privilege keys per environment
  • Webhooks: use the Production URL only after deploy. Protect with secrets
  • Rate limits: design backoff on day one. Test with 10Ă— sample data

Pro tip: When node names differ across packages, search in the Install dialog and read the node credentials page. Pin the one that matches your account type (EU vs US, sandbox vs prod)

Transition: With the basics covered, let’s map the top n8n community nodes for common teams and show reliable starter workflows

flowchart TD
    A[Need an integration] --> B{Built-in works}
    B -->|Yes| C[Use built-in]
    B -->|No| D[Find community]
    D --> E[Check maintenance]
    E --> F[Pin version]
    F --> G[Add HTTP fallback]

    classDef trigger fill:#e1f5fe,stroke:#01579b
    classDef process fill:#fff3e0,stroke:#ef6c00
    classDef action fill:#e8f5e8,stroke:#2e7d32
    class A,B trigger
    class C,D,E,F,G action

Sales workflows

What you’ll learn:

  • Which community nodes speed up RevOps
  • Safe auth scopes and rate limit settings
  • Paste‑in flows to deploy this week

Transition: Start with a small flow that updates contacts and lists, then expand to deals and routing

Node 1: HubSpot (Community)

What this node does best:

  • Bidirectional sync for contacts, companies, deals, engagements
  • Property mapping with custom objects for RevOps
  • Fast list updates without brittle CSVs

Setup and auth gotchas:

  • OAuth scopes must include crm.objects.read and crm.objects.write. Add crm.lists for list work
  • Custom object APIs differ by account. Verify object IDs with a test call
  • Date fields should be ISO strings. Avoid locale formats

Rate limits and throttling:

  • Batch writes of 50–100 with Wait between batches
  • 429 Retry‑After respected. Enable Retry On Fail with exponential backoff

Paste‑in workflow idea:

  • Trigger Webhook - Enrich via HTTP - HubSpot upsert contact - Add to list
{
  "nodes": [
    {"parameters": {"path": "lead"}, "name": "Webhook", "type": "n8n-nodes-base.webhook"},
    {"parameters": {"url": "https://api.clearbit.com/v2/people/find", "sendHeaders": true}, "name": "HTTP Enrich", "type": "n8n-nodes-base.httpRequest"},
    {"parameters": {"resource": "contact", "operation": "upsert"}, "name": "HubSpot Upsert", "type": "community.hubspot"}
  ]
}
erDiagram
    Contact ||--o{ Deal : has
    Company ||--o{ Deal : has

    Contact {
        int id
        string email
        string first_name
        string last_name
        datetime created_at
    }

    Company {
        int id
        string name
        string domain
        datetime created_at
    }

    Deal {
        int id
        string stage
        int amount
        datetime close_date
    }

Node 2: Salesforce (Community)

What this node does best:

  • SOQL queries for Leads, Contacts, Accounts, Opportunities
  • Bulk API for large imports without timeouts

Setup and auth gotchas:

  • Connected App with OAuth and refresh tokens. Sandbox and prod domains differ
  • Permission sets must allow API and object access

Rate limits and throttling:

  • Bulk API for more than 10k rows
  • REST concurrency capped to 2–3

Paste‑in workflow idea:

  1. Schedule daily
  2. Run SOQL for new leads in 24h
  3. Enrich and push to Slack
SELECT Id, Company, Email FROM Lead WHERE CreatedDate = LAST_N_DAYS:1
flowchart TD
    A[Daily schedule] --> B[Run SOQL]
    B --> C[HTTP enrich]
    C --> D[Post to Slack]

    classDef process fill:#fff3e0,stroke:#ef6c00
    classDef action fill:#e8f5e8,stroke:#2e7d32
    class A,B process
    class C,D action

Node 3: Pipedrive (Community)

What this node does best:

  • Simple updates for pipelines, activities, stage moves
  • Ideal for SMB sales ops and quick wins

Setup and auth gotchas:

  • API token auth. EU orgs must set the correct base URL
  • Custom fields have hash‑like keys. Fetch the field map first

Rate limits and throttling:

  • Paginate with start and limit
  • Wait 250–500 ms between loops

Paste‑in workflow idea:

  • Webhook from form - Create person - Create deal in stage “New” - Slack DM owner

Node 4: Close CRM (Community)

What this node does best:

  • Power dialer automation, sequences, lead and contact events
  • Event streams for near real‑time dashboards

Setup and auth gotchas:

  • API key with lead.read, lead.write, and activity scopes. Verify org ID in headers

Rate limits and throttling:

  • Respect X‑RateLimit‑Remaining. Slow when <10

Paste‑in workflow idea:

  • New lead - Auto create task and schedule first call - If no answer in 48h, re‑queue

Node 5: Apollo (Community)

What this node does best:

  • Prospecting and enrichment with sequencing hooks
  • Firmographic filters for ICP lists

Setup and auth gotchas:

  • API key tied to workspace. Check plan limits for enrichment

Rate limits and throttling:

  • Batch 25 prospects per call. Cache results to cut costs

Paste‑in workflow idea:

  • CSV upload - Apollo enrich - HubSpot upsert - Assign owner by territory map

Node 6: Lemlist (Community)

What this node does best:

  • Add to sequences, update statuses, pull replies

Setup and auth gotchas:

  • API key per account. Map sequence IDs explicitly

Rate limits and throttling:

  • Poll replies every 5–10 minutes. Use since parameter

Paste‑in workflow idea:

  • Form opt in - Lemlist add to Warm Inbound - Wait 3d - If no reply, handoff to SDR

Node 7: Clearbit (Community)

What this node does best:

  • Email and company enrichment for scoring and routing

Setup and auth gotchas:

  • Secret key required. Handle 404 when no person is found

Rate limits and throttling:

  • Cache by email domain for 24h with the Redis node

Paste‑in workflow idea:

  • Webhook - Clearbit enrich - If company_size > 200 - Route to Enterprise team

Node 8: Stripe (Community)

What this node does best:

  • Payments, subscriptions, invoices, events

Setup and auth gotchas:

  • Restricted keys for read only analytics vs write ops
  • Webhook signatures must be verified

Rate limits and throttling:

  • Replay using event IDs. Use idempotency keys for writes

Paste‑in workflow idea:

  • Stripe webhook invoice.payment_failed - Retry email - Create HubSpot task

Callout: For revenue flows, pin node versions and enable retries with exponential backoff before launch


Support workflows

What you’ll learn:

  • How to connect chat and ticket tools in n8n
  • Safe polling, pagination, and cursor handling
  • Ready flows for alerts and escalations

Transition: Start with a chatbot handoff to tickets, then layer alerts and product issue loops

Node 9: Zendesk (Community)

What this node does best:

  • Tickets, users, macros, SLAs, CSAT exports

Setup and auth gotchas:

  • OAuth with offline access. Subdomain matters. Roles must allow API

Rate limits and throttling:

  • Cursor pagination with 200–500 ms between pages

Paste‑in workflow idea:

  • Chatbot handoff - Create ticket with tags - Slack alert if VIP

Node 10: Intercom (Community)

What this node does best:

  • Conversations, users, companies, tags, notes

Setup and auth gotchas:

  • OAuth scopes per object. Legacy and workspace APIs differ

Rate limits and throttling:

  • Use cursors with since for conversation polling

Paste‑in workflow idea:

  • New conversation - Classify with LLM - If bug, create Jira issue and link back

Node 11: Freshdesk (Community)

What this node does best:

  • Lightweight ticketing with automations

Setup and auth gotchas:

  • API key and domain. Watch product editions for API parity

Rate limits and throttling:

  • Paginate tickets oldest to newest to avoid reprocessing

Paste‑in workflow idea:

  • Email - Freshdesk ticket - If refund, post to Finance Slack with details

Node 12: Linear (Community)

What this node does best:

  • Issues, projects, cycles for product and support engineering

Setup and auth gotchas:

  • Personal tokens or API tokens. Teams map to IDs, not names

Rate limits and throttling:

  • GraphQL: request only needed fields and batch queries

Paste‑in workflow idea:

  • Zendesk bug tag - Create Linear issue - Back sync status to ticket

Node 13: Slack Enhanced (Community)

What this node does best:

  • Rich blocks, threads, files, modals

Setup and auth gotchas:

  • Bot token with chat.write, files.write, channels.history. Install in each workspace

Rate limits and throttling:

  • 1 message per second per channel guideline. Queue bursts

Paste‑in workflow idea:

  • Pager alert - Post thread with action buttons - Slash command closes loop

Node 14: Microsoft Teams (Community)

What this node does best:

  • Channels, cards, mentions for enterprise rooms

Setup and auth gotchas:

  • Azure app registration. Admin consent may be required

Rate limits and throttling:

  • Throttling headers respected. Back off on 429

Paste‑in workflow idea:

  • High priority ticket - Adaptive Card to incidents - Button creates Zoom bridge

Node 15: Twilio (Community)

What this node does best:

  • SMS, WhatsApp replies, voice callbacks

Setup and auth gotchas:

  • Verify From numbers. WhatsApp templates must be pre approved

Rate limits and throttling:

  • Queue outbound SMS and cap to carrier guidelines

Paste‑in workflow idea:

  • CSAT < 3/5 - Send apology SMS with book a call link
flowchart TD
    A[New ticket] --> B{VIP}
    B -->|Yes| C[Alert channel]
    B -->|No| D[Create ticket]
    C --> E[Assign owner]
    D --> E

    classDef alert fill:#f3e5f5,stroke:#7b1fa2
    classDef action fill:#e8f5e8,stroke:#2e7d32
    class A,B alert
    class C,D,E action

Callout: Use cursor pagination and since parameters to avoid missing events during deploys


DevOps workflows

What you’ll learn:

  • How to wire CI and infra signals to actions
  • Safer auth for repos and clusters
  • Proven backoff patterns for reliability

Transition: Start with alerts to chat, then automate remediations you can safely roll back

Node 16: GitHub (Community)

What this node does best:

  • PR events, releases, issues for ChatOps

Setup and auth gotchas:

  • GitHub App vs PAT. For org wide use a GitHub App

Rate limits and throttling:

  • ETags to avoid wasted calls. Poll with If None Match

Paste‑in workflow idea:

  • New release - Build notes - Post to Slack and create status page update

Node 17: GitLab (Community)

What this node does best:

  • Pipelines, merge requests, artifacts

Setup and auth gotchas:

  • Project vs group tokens. Runners behind IP allowlists need outbound egress

Rate limits and throttling:

  • Pagination with X Next Page. Sleep 250 ms between pages

Paste‑in workflow idea:

  • Pipeline failed - Create Jira bug - Notify owner

Node 18: Jenkins (Community)

What this node does best:

  • Trigger jobs, read builds, fetch artifacts

Setup and auth gotchas:

  • Crumb issuer handled. Use token auth, not passwords

Rate limits and throttling:

  • Poll every 15–30 s for long builds, not every 2 s

Paste‑in workflow idea:

  • Git tag - Trigger Jenkins deploy - Post success with changelog to Teams

Node 19: Docker (Community)

What this node does best:

  • Inspect containers and restart unhealthy ones

Setup and auth gotchas:

  • Socket access on self hosted n8n. Restrict with read only when possible

Rate limits and throttling:

  • Backoff between restarts. Avoid loops with a max retries guard

Paste‑in workflow idea:

  • Healthcheck fail - Restart container - If still failing, page on call

Node 20: Kubernetes (Community)

What this node does best:

  • Get and patch deployments, scale replicas, watch events

Setup and auth gotchas:

  • ServiceAccount with RBAC. Scope cluster and namespace

Rate limits and throttling:

  • Server side selectors to reduce list calls

Paste‑in workflow idea:

  • CPU > 80% for 5m - Scale deployment and post Grafana link

Node 21: Cloudflare (Community)

What this node does best:

  • DNS changes, cache purge, firewall rules

Setup and auth gotchas:

  • API tokens scoped to zone.dns.edit. Never use global keys in prod

Rate limits and throttling:

  • Purge by tags. Avoid purging entire zones

Paste‑in workflow idea:

  • Deploy finished - Purge cache by URLs - Ping uptime check

Node 22: Datadog (Community)

What this node does best:

  • Events, metrics, monitors for central alert fan out

Setup and auth gotchas:

  • API and App keys. Site us3 or eu1 must match your tenant

Rate limits and throttling:

  • Aggregate metrics client side. Send one payload per minute

Paste‑in workflow idea:

  • Monitor alert - Create incident channel and pin runbook
flowchart TD
    A[Alert fired] --> B[Parse event]
    B --> C{Auto fix safe}
    C -->|Yes| D[Run fix]
    C -->|No| E[Notify team]
    D --> F[Post status]
    E --> F

    classDef trigger fill:#e1f5fe,stroke:#01579b
    classDef process fill:#fff3e0,stroke:#ef6c00
    classDef action fill:#e8f5e8,stroke:#2e7d32
    class A trigger
    class B,C process
    class D,E,F action

Callout: Guardrails matter. Add max retries, timeouts, and audit logs before enabling auto remediation


AI workflows

What you’ll learn:

  • When to use OpenAI, Anthropic, Gemini, or local LLMs
  • How to control cost with caching and batching
  • Starter flows for support, code review, and RAG

Transition: Begin with human in the loop approvals, then automate low risk responses

Node 23: OpenAI (Community)

What this node does best:

  • GPT for text, tools, structured output. Assistants for multi step tasks

Setup and auth gotchas:

  • Model names and regions change. Store in env vars

Rate limits and throttling:

  • Token budgets per run. Cache embeddings and responses

Paste‑in workflow idea:

  • New ticket - Summarize and propose response - Human approves - Send

Node 24: Anthropic (Community)

What this node does best:

  • Long context reasoning and safer drafting

Setup and auth gotchas:

  • System prompts used consistently. Set max_tokens to cap spend

Rate limits and throttling:

  • 429 backoff with exponential strategy. Reuse context chunks

Paste‑in workflow idea:

  • PR diff - Claude review - Post inline suggestions to GitHub

Node 25: Google Gemini (Community)

What this node does best:

  • Multimodal input for docs and support screenshots

Setup and auth gotchas:

  • API key vs OAuth differs by project. Set location for latency

Rate limits and throttling:

  • Batch images and downscale before upload

Paste‑in workflow idea:

  • Screenshot - OCR and classify - Create bug ticket with steps to repro

Node 26: Ollama (Community)

What this node does best:

  • Local LLMs for privacy sensitive data and low cost loops

Setup and auth gotchas:

  • Host and port exposed. Warm models at boot to avoid cold starts

Rate limits and throttling:

  • Queue heavy jobs. One worker per model on small boxes

Paste‑in workflow idea:

  • Docs folder change - Chunk and embed locally - RAG answers without cloud

Node 27: Pinecone (Community)

What this node does best:

  • Vector search for RAG, dedupe, semantic routing

Setup and auth gotchas:

  • Index name and dimension must match the embedding model

Rate limits and throttling:

  • Upsert in batches of 100–200 vectors

Paste‑in workflow idea:

  • New article - Embed - Upsert - Query for related content

Node 28: Weaviate (Community)

What this node does best:

  • Hybrid search with schema rich objects

Setup and auth gotchas:

  • Class names are case sensitive. Migrate schemas carefully

Rate limits and throttling:

  • Consistency ONE for speed when acceptable

Paste‑in workflow idea:

  • Support KB - Ingest - RAG answer first, escalate if confidence below threshold

Node 29: Qdrant (Community)

What this node does best:

  • Fast vector store with payload filters. Strong self hosted choice

Setup and auth gotchas:

  • Collections per tenant. Version pin server and client

Rate limits and throttling:

  • Batch writes and compress payloads

Paste‑in workflow idea:

  • Changelog - Embed - Similarity search to suggest release notes links

Node 30: Apify, Browserless, Playwright (Community)

What this node does best:

  • Headless browsing, scraping, structured extraction at scale

Setup and auth gotchas:

  • Provider tokens required. Respect robots and legal boundaries

Rate limits and throttling:

  • Concurrency caps with randomized delays and proxy rotation when allowed

Paste‑in workflow idea:

  • Competitor pricing check - Diff detector - Slack alert with evidence link

Rate limit patterns

What you’ll learn:

  • Four copy ready throttling patterns
  • Where to add Wait and batch nodes
  1. Loop and Wait: for 100 req per min, Wait 600 ms inside the loop
  2. Respect Retry After: read the header and sleep that many ms
  3. HTTP Batch: send 25 items per request with 2–5 s between batches
  4. Redis token bucket: decrement a key. If negative, Wait then retry
{
  "nodes": [
    {"name": "Split Items", "type": "n8n-nodes-base.itemLists"},
    {"name": "Wait 600ms", "type": "n8n-nodes-base.wait", "parameters": {"amount": 600, "unit": "milliseconds"}},
    {"name": "HTTP", "type": "n8n-nodes-base.httpRequest"}
  ]
}
flowchart TD
    A[Items in] --> B[Split items]
    B --> C[Wait 600 ms]
    C --> D[HTTP request]
    D --> E{More items}
    E -->|Yes| B
    E -->|No| F[Done]

Mini workflow library

What you’ll learn:

  • Four starter flows you can adapt today

  • Sales: Webhook - Enrich with Clearbit - HubSpot upsert - Owner routing - Slack DM

  • Support: Intercom new convo - Classify with LLM - Zendesk ticket - Linear bug if needed

  • DevOps: Datadog alert - Kubernetes scale - Cloudflare purge - Incident channel

  • AI: Notion doc change - Chunk and embed with Ollama and Qdrant - RAG answer - Audit log

Callout: Start with 3–5 nodes that move a KPI this week. Pin versions, add backoff, and ship. Then expand. Automation compounds

đź“§