n8n and RD Station: Community Nodes for Marketing and CRM

n8n doesn’t have a built-in RD Station node: there is no RD Station page among the built-in integrations in n8n’s documentation. To connect n8n to RD Station you either install a community node or call the RD Station API yourself with n8n’s HTTP Request node. This guide compares the RD Station community nodes listed on our RD Station hub, using each package’s README and our own npm data, so you can pick the right one for RD Station Marketing or RD Station CRM.

First: Marketing or CRM?

RD Station Marketing and RD Station CRM are separate products with separate APIs, and every package below is built for one of them. Pick the product first, then the package.

RD Station community nodes at a glance

Weekly npm downloads as of 27 October 2026. The hub lists 8 packages with 265 downloads a week between them.

RD Station Marketing packages

n8n-nodes-rdsm

The widest Marketing coverage in the list. Its source is in the ResultadosDigitais organization on GitHub. According to its README it covers:

• Contact: Create, Get, Update, Delete, Add Tags, Get Events
• Conversion: Create Conversion Event
• Custom Field: Get Many, Create, Update, Delete
• E-Commerce Event: Checkout Started, Abandoned Cart, Order Paid, Order Canceled, Order Fulfilled, Shipment Delivered
• Qualification and Funnel: Get Contact Funnels, Mark Lead as Opportunity, Mark Opportunity as Won, Mark Opportunity as Lost, Update Contact Funnel
• RD Station Marketing Trigger: Converted, Marked Opportunity

Authentication is an RD Station Marketing OAuth2 credential. You create an app in the RD Station App Store, use its client_id and client_secret, and register n8n’s OAuth Redirect URL as the app’s callback URL. The README says it must match exactly.

n8n-nodes-rdstation-marketing

Contacts (create, update, get by email or UUID), standard conversion events, and segmentations with their contacts, with automatic pagination. OAuth2 with automatic token refresh.

@deviobr/n8n-nodes-rdstation and n8n-nodes-rd-station-marketing-conversion

Both do one thing: record a conversion event in RD Station Marketing (New Conversion). The difference is the credential. The first uses OAuth2 through an RD Station App Store app, the second an API key generated in RD Station Marketing. They are the simplest choice if all you need is to send leads from a form or another app into RD Station.

RD Station CRM packages

n8n-nodes-rd

Also in the ResultadosDigitais organization on GitHub. It adds two nodes, RD Station CRM and RD Station CRM Trigger. Resources: Deals (Create, Get Many, Update), Contacts, Companies, Tasks and Products (Get Many, Get, Create, Update), Webhooks, and Metadata (pipelines, custom fields, users, deal sources). The trigger fires on contact, deal and organization created or updated events. It uses an RD Station CRM OAuth2 credential and works with RD Station’s staging or production environment. Install it by its npm name, n8n-nodes-rd.

n8n-nodes-rd-station-crm-api-v2 and @matheusprm-nodes/n8n-nodes-rdstation-crm

Both cover the RD Station CRM API v2 with OAuth2. The first lists deals, contacts, organizations, tasks, products, pipelines and webhooks. The second lists 18 resources, including campaigns, notes, attachments, lost reasons, stages, teams and users, plus RDQL filtering and a raw request mode for custom API calls.

n8n-nodes-rdstation-crm-v1

The only package here that uses CRM API v1 with a plain API token (in RD Station CRM under Settings > Integrations > API Token). Its author says they chose v1 because API v2’s OAuth2 needs an RD Station Marketing plan, while v1 works with any RD Station CRM account. It covers deals, contacts and organizations (create, get, get many, update).

How to choose

• Only sending conversions or leads to Marketing: @deviobr/n8n-nodes-rdstation (OAuth2) or n8n-nodes-rd-station-marketing-conversion (API key).
• Full Marketing automation, including funnel stages, e-commerce events and a trigger: n8n-nodes-rdsm.
• CRM with a trigger for new or updated deals and contacts: n8n-nodes-rd.
• CRM with the widest API v2 coverage: @matheusprm-nodes/n8n-nodes-rdstation-crm.
• CRM without OAuth: n8n-nodes-rdstation-crm-v1.

Before you install, open the package’s page here to check its latest version and last release date, and, where it has one, its GitHub repository for open issues. Download counts on this hub are small, so a package’s maintenance history matters more than its rank.

Installing an RD Station community node

On a self-hosted n8n instance, an owner or admin goes to Settings > Community Nodes, selects Install, enters the npm package name and accepts the risk notice. Full steps, including npm and Docker, are in How to Install n8n Community Nodes. On n8n Cloud you can only install community nodes that n8n has verified, see Verified vs Unverified n8n Community Nodes.

For OAuth2 credentials, the callback URL to register in your RD Station app is the OAuth Redirect URL shown in the n8n credential screen.

FAQ

Does n8n have a built-in RD Station node?

No. n8n’s documentation lists no built-in RD Station node. Use a community node, or the HTTP Request node with the RD Station API.

Which RD Station community node is the most used?

@deviobr/n8n-nodes-rdstation, with 81 weekly npm downloads on 27 October 2026, followed by n8n-nodes-rd (74) and n8n-nodes-rdsm (60).

Can I use RD Station CRM in n8n without OAuth?

Yes, with n8n-nodes-rdstation-crm-v1, which uses an RD Station CRM API token and API v1.

Is there an RD Station trigger for n8n?

Yes, in community packages: n8n-nodes-rdsm has an RD Station Marketing Trigger (Converted, Marked Opportunity) and n8n-nodes-rd has an RD Station CRM Trigger (contacts, deals and organizations created or updated).