Resources · Make integration

RD Station Make integrationAutomate RD Station with Make.

Can Make react the moment a lead converts in RD Station? Yes. The RD Station Make integration offers 46 modules, including 2 instant triggers, 34 actions and 10 searches. This page shows marketing and sales teams how to connect the account and build a first working scenario.

Try the RD Station integration on MakeSee the 46 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the RD Station Make integration do for you?

The RD Station Make integration links your RD Station account to Make, a visual tool where you build a scenario: an automation made of modules, each module being one brick such as a trigger, an action or a search. RD Station then sends leads, contacts and deals to your other apps, with no code.

Hand hot leads to sales without copy and paste. Watch New Opportunities fires when a lead is marked as an opportunity, and a Create task module can put the follow-up on a salesperson's list right away.

Keep contact records complete. When a form tool or a spreadsheet collects new information, Get a Contact finds the record and Update a Contact writes the change back, so marketing and sales read the same data.

Close the loop on results. Mark a Lead as Won / Lost records whether a lead was won or lost, which keeps your funnel honest when the sale happens in another tool.

One limit to know before you start: Make publishes only partial documentation for RD Station CRM, and many modules come without an official description. Test each new module with Run once before you rely on it. If you want guided practice, see the Make training, or check the n8n vs Make comparison when you are still choosing a tool. The Make troubleshooting guide helps when a run fails.

Connect

How do you connect RD Station to Make?

  1. 01

    Add an RD Station module

    In your scenario, click the + and search for RD Station. Pick any module, then click Create a connection. A connection is your RD Station account linked to Make once, then reused by every RD Station module.

  2. 02

    Name the connection

    This step is optional, but a clear name such as the team or the account owner helps when several people share the same Make organization and each one links a different RD Station account.

  3. 03

    Authorize Make and save

    Make sends you to RD Station to approve access, or asks for the key the app gives you. Approve, come back to Make and click Save. The module can now read your RD Station data.

First scenario

Your first scenario: a follow-up task for every converted lead

GoalWhen a new lead converts in RD Station, Make creates a follow-up task for the sales team.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + in the middle of the canvas to add the first module.

  2. 02

    Add the conversion trigger

    Search for RD Station and pick Watch New Lead Conversions. Click Create a connection if this is your first RD Station module, then fill the fields Make shows.

  3. 03

    Add the task

    Click the + on the right of the trigger and pick Create task. Map the lead data the trigger received into the task fields.

  4. 04

    Test with Run once

    Click Run once. Each module shows the bundles it received, so you can check that the lead data reached the task before going live.

  5. 05

    Switch it on

    Save the scenario and switch it on. The trigger is instant, so RD Station calls Make each time a lead converts, with no polling to set.

Triggers

What starts an RD Station scenario?

2 modules start a scenario when something happens in RD Station. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by RD Station as soon as it happens.

RD Station1Watch New Lead Conversions

Watch New Lead Conversions

Instant trigger

In Make“Triggers when a new lead is created. Conversions generated by import or by manually entering leads will not activate the trigger.”

Your scenario starts as soon as a new lead converts in RD Station, so a form submission or a landing page signup can reach your CRM, your spreadsheet or your team chat without waiting. Each conversion arrives as one bundle, one item passed to the next module.

How it fires
instant, RD Station calls Make through a webhook as soon as it happens.
When to use it
you want every inbound lead from your forms routed or acknowledged the moment it lands.
Watch out
leads you import or enter by hand do not fire this trigger, so a bulk upload will not start the scenario.
RD Station2Watch New Opportunities

Watch New Opportunities

Instant trigger

In Make“Triggers when a lead is marked as opportunity.”

This trigger tells you when marketing hands a lead over: it starts the scenario each time a lead is marked as an opportunity in RD Station. That is the moment a salesperson should pick it up, and Make can make sure nobody misses it.

How it fires
instant, RD Station calls Make through a webhook as soon as it happens.
When to use it
you want a deal, a task or a chat alert created for sales at the handover itself.
Watch out
it reacts to the opportunity flag only, not to every new lead; pair it with Watch New Lead Conversions if you need both.
Modules

What can Make do in RD Station?

RD Station gives you 44 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

RD Station1

Create a Contact

Action

In Make“Creates a contact.”

You get a new contact in RD Station from data collected elsewhere, such as a signup in a webinar tool or a row in a shared sheet. Each run adds one record, filled with the values you map from earlier modules.

When to use it
leads arrive through a channel that RD Station does not capture on its own.
Watch out
check first with Get a Contact if the person may already exist, to avoid duplicates.
RD Station2

Create a Conversion Event

Action

In Make“Registers a new conversion event for a contact.”

Records a conversion for an existing contact, so RD Station counts actions that happened outside its own forms. A demo booked in a calendar tool or a purchase in a shop can then appear in the contact's history.

When to use it
an important step of the buyer journey happens in another app and marketing wants it tracked in RD Station.
Watch out
the event attaches to a contact, so make sure the contact exists before this module runs.
RD Station3

Create a Custom Field

Action

In Make“Creates a field for the current account.”

Adds a new field to your RD Station account, giving you a place to store data the standard fields do not cover. The field belongs to the account, not to one contact, so every record gains it at once.

When to use it
a setup scenario prepares an account before other scenarios start writing to that field.
Watch out
running it inside a busy scenario would try to create the same field again; keep it for one-off setup work.
RD Station4

Delete a Custom Field

Action

In Make“Deletes a field from the current account.”

Removes a field from your RD Station account, which cleans up leftovers from old campaigns or tests. The whole account loses the field, not only one contact, and the values stored in it go with it.

When to use it
you retire a field after moving its data somewhere else.
Watch out
a delete does not come back; run List Custom Fields first and double-check the field you target before switching the scenario on.
RD Station5

Get Account Information

Action

In Make“Returns the account name from your RD Station Marketing account.”

Returns the name of the RD Station Marketing account behind your connection. It sounds minor, yet it tells you which account a scenario is actually talking to when your team manages several.

When to use it
you label reports or alerts with the account name, or you want a quick check that a new connection points to the right place.
Watch out
it only returns the account name, so it cannot replace a search for contacts or deals.
RD Station6

Get a Contact

Action

In Make“Returns data about a specific contact.”

Fetches the details of one specific contact, so later modules can use its data: to personalize an email, enrich a deal, or decide which branch of the scenario to follow. It is the lookup you place before any update.

When to use it
you know which person you need and want their current record.
Watch out
when you are not sure who matches, List contact is the better choice, since it can return several results.
RD Station7

Get a Funnel

Action

In Make“Returns a funnel associated to the given contact.”

Tells you where a contact stands in your funnel by returning the funnel linked to that contact. Your scenario can then treat a fresh lead differently from someone close to buying.

When to use it
a follow-up message or a sales alert should depend on the contact's current stage.
Watch out
it reads one contact at a time, so place it after a module that already identified the person.
RD Station8

Get a Tracking Code

Action

In Make“Returns the RD Station Marketing tracking code so it can be embedded on websites or CMS.”

Hands you the RD Station Marketing tracking code, ready to be embedded on a website or a CMS. Tracking then reports visits back to RD Station without anyone copying the code by hand from the settings.

When to use it
a scenario sets up new sites or landing pages and needs to insert the code as part of the process.
Watch out
the module returns the code; placing it on the site still takes a module from your CMS app.
RD Station9

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Covers what the listed modules do not: it calls any endpoint of the RD Station API from your scenario, using the same connection as the other modules. You do not need a second login or a separate key.

When to use it
you need an operation that has no dedicated module on this page.
Watch out
you build the request yourself from the RD Station API documentation, so test it with Run once and read the response before going live.
RD Station10

Mark a Lead as Won / Lost

Action

In Make“Marks a specified Lead as Won or Lost.”

Closes the story of a lead by marking it as won or lost in RD Station. Marketing then sees which campaigns turned into customers, even when the deal was signed in another tool.

When to use it
a payment, a signed contract or a closed deal elsewhere should update the lead's outcome.
Watch out
map the outcome carefully; a won lead wrongly flagged as lost skews every report built on it.
RD Station11

Update a Contact

Action

In Make“Updates the properties of a contact.”

Writes new values on an existing contact, so the record in RD Station follows what happens in your other apps. A new job title, a phone number collected by sales or a changed company can all land on the same profile.

When to use it
another tool holds fresher information than RD Station.
Watch out
you target a precise contact, so place Get a Contact or List contact before it to find the right one.
RD Station12

Update a Custom Field

Action

In Make“Updates a field for the current account. It supports partial updates.”

Changes the settings of a custom field in your account, and it accepts partial updates: you send only what changes, and the rest of the field stays as it is. No need to resend the full definition.

When to use it
a field needs a new label or an adjusted setting after your data model evolves.
Watch out
this edits the field itself, not the value stored on a contact; for that, use Update a Contact.
RD Station13

Update a Funnel

Action

In Make“Updates the funnel information about the current contact.”

Moves a contact within your funnel by updating its funnel information. When a lead books a call or requests a quote in another app, the stage in RD Station can follow on its own.

When to use it
a signal outside RD Station proves the lead has progressed.
Watch out
read the current stage with Get a Funnel first if you want to avoid moving a contact backwards.
RD Station14

List Custom Fields

Search

In Make“Returns a list of fields and their attributes from the current account.”

Returns every field of your account with its attributes, which gives you a full picture of the data model before you write anything. As a search, it can send several bundles, one per field.

When to use it
you audit fields, or you need a field's details before updating or deleting it.
Watch out
each returned field feeds the next module separately, so later modules run once per field and count operations accordingly.
RD Station15

Create company

ActionIn the docs only

Adds a company to RD Station CRM, so deals and contacts can hang off a proper account record. Make publishes no description for this module; its name and fields are your guide.

When to use it
a new customer account is signed or registered in another tool and sales needs it in the CRM.
Watch out
run it once on a test company and read the result, since the documentation is limited.
RD Station16

Create deal

ActionIn the docs only

Opens a deal in RD Station CRM from data your scenario already holds, such as a qualified lead or a quote request. Make gives no official description here, so rely on the fields the module shows once connected.

When to use it
after Watch New Opportunities, to turn the handover into something sales can work.
Watch out
List pipelines helps you see where deals can go before mapping this module.
RD Station17

Create product

ActionIn the docs only

Adds a product to your RD Station CRM catalog, so deals can reference what you actually sell. The official documentation says nothing more about it, which makes a test run the fastest way to learn its fields.

When to use it
a new offer appears in your shop or billing tool and should exist in the CRM too.
Watch out
check with List Product first if the item may already exist.
RD Station18

Create task

ActionIn the docs only

Puts a to-do in RD Station CRM, so the next action on a lead or a deal does not depend on someone's memory. Make lists no description for it; the connected module shows which fields it expects.

When to use it
a new conversion or opportunity should turn into a call or an email for a salesperson.
Watch out
test with Run once to confirm the task lands where your team looks for it.
RD Station19

Create webhook

ActionIn the docs only

Registers a webhook in RD Station CRM from inside a scenario, so the app can notify another address when something happens. Make does not document the module further, so treat its fields as the only reference.

When to use it
you manage the CRM's outgoing notifications through automation rather than by hand.
Watch out
List webhooks shows what is already registered, which helps avoid two webhooks doing the same job.
RD Station20

Delete webhook

ActionIn the docs only

Removes a webhook registered in RD Station CRM, which stops the notifications it was sending. Make publishes no description for it beyond the name.

When to use it
an integration is retired and its webhook should not keep firing into an empty address.
Watch out
a deleted webhook cannot be restored by the module; confirm the target with Get webhook before switching the scenario on.
RD Station21

Get company

ActionIn the docs only

Retrieves one company record from RD Station CRM so the following modules can use its details. No official description exists, but the connected module lists the data it returns after a first run.

When to use it
you already know which company you need, for example from a deal, and want its current data.
Watch out
when you only have a partial name, List company fits better.
RD Station22

Get deal

ActionIn the docs only

Reads a single deal from RD Station CRM, handy before an update or before sending its status to another tool. Make leaves this module undocumented, so a Run once test shows exactly what comes back.

When to use it
a scenario must check a deal's current state before acting on it.
Watch out
it targets one known deal; to browse several, use List deal.
RD Station23

Get product

ActionIn the docs only

Brings back one product from your RD Station CRM catalog, for instance to copy its details into a quote or an invoice built by another app. There is no official description to lean on.

When to use it
a deal references a product and you need that product's information downstream.
Watch out
read the output of a test run to see which product details the module actually returns.
RD Station24

Get task

ActionIn the docs only

Looks up one task in RD Station CRM, which lets a scenario check whether a follow-up is still open before sending a reminder. Make provides no description beyond the module name.

When to use it
you track a specific task and want its latest state.
Watch out
List task suits better when you need every task matching a situation rather than one.
RD Station25

Get webhook

ActionIn the docs only

Shows the setup of one webhook registered in RD Station CRM, a quick way to verify where notifications go. Make does not describe the module officially.

When to use it
you audit an integration, or confirm a target before Update webhook or Delete webhook.
Watch out
it reads one webhook you already identified; List webhooks gives you the full set.
RD Station26

List Product

SearchIn the docs only

Returns the products of your RD Station CRM catalog. As a search module, it can send zero, one or several bundles, and the next modules run once for each product found.

When to use it
you sync your catalog to a spreadsheet or check whether a product exists before creating it.
Watch out
a large catalog means many bundles, and each module after it counts operations per product.
RD Station27

List company

SearchIn the docs only

Pulls several companies from RD Station CRM at once, one bundle per company. It is the right search when you do not know the exact record yet or want to process a batch.

When to use it
you export accounts to a reporting tool, or look for a company before creating a duplicate.
Watch out
an empty result is possible, so plan what the scenario does when no company matches.
RD Station28

List contact

SearchIn the docs only

Searches the contacts of RD Station CRM and returns every match as its own bundle. That makes it the starting point for bulk work, such as copying a segment to an ad audience or a mailing tool.

When to use it
you need several contacts, or you are not sure which record matches.
Watch out
each contact triggers the following modules separately, which adds up in operations.
RD Station29

List deal

SearchIn the docs only

Returns deals from RD Station CRM, one bundle per deal, which feeds dashboards and pipeline reviews built in other tools. Make gives no description beyond this search behavior.

When to use it
you want a view of open deals outside the CRM, or you need to process several at once.
Watch out
test it and check how many bundles come back before chaining costly modules behind it.
RD Station30

List pipelines

SearchIn the docs only

Shows the sales pipelines configured in RD Station CRM, so you know where deals can live before you create or move one. Each pipeline comes out as a separate bundle.

When to use it
you set up a Create deal module and need to see which pipelines exist.
Watch out
the module is undocumented by Make; read a test run to see the pipeline details it provides.
RD Station31

List product in deal

SearchIn the docs only

Returns the products attached to a deal, one bundle each. When a deal closes, this is how your scenario learns what was sold, for billing or fulfillment in another app.

When to use it
an invoice, an order or a delivery depends on the exact contents of a deal.
Watch out
a deal with no products returns nothing, so plan for that branch.
RD Station32

List source

SearchIn the docs only

Lists the sources recorded in RD Station CRM, one bundle per source. It helps when a scenario should label or route deals according to where they came from.

When to use it
you map a lead origin from another tool to a source your CRM already knows.
Watch out
Make does not describe what a source contains; run it once and read the bundles before relying on them.
RD Station33

List task

SearchIn the docs only

Returns tasks from RD Station CRM as separate bundles, a good base for a digest of open follow-ups sent to a chat channel or an email. No official description completes the name.

When to use it
a manager wants the pending work of the sales team gathered in one place.
Watch out
many tasks mean many bundles; add an aggregator from Make if you want one message instead of dozens.
RD Station34

List webhooks

SearchIn the docs only

Returns every webhook registered in RD Station CRM, so you can see at a glance which outside services receive notifications. Each webhook arrives as one bundle.

When to use it
you audit integrations, or check for an existing webhook before Create webhook adds another.
Watch out
the module is not documented by Make, so compare its output with what you expect before cleaning anything up.
RD Station35

Update company

ActionIn the docs only

Changes an existing company in RD Station CRM, keeping the account record aligned with your billing or support tool. Make publishes no description, so the connected module's fields show what you can edit.

When to use it
an address, a segment or an owner changes elsewhere and the CRM should follow.
Watch out
find the right company first with Get company or List company.
RD Station36

Update deal

ActionIn the docs only

Edits a deal in RD Station CRM when something happens outside it: a quote signed, a payment received, a meeting booked. The deal then reflects reality without a salesperson retyping it.

When to use it
another app holds the event that should move or enrich the deal.
Watch out
the module has no official description; test it on a sample deal before touching the live pipeline.
RD Station37

Update task

ActionIn the docs only

Modifies an existing task in RD Station CRM, for example to reflect that a follow-up happened in another tool. Your team's list stays accurate without manual cleanup.

When to use it
a call logged in your phone system or an email sent elsewhere completes a CRM task.
Watch out
Make documents nothing beyond the name, so check the fields after connecting and target the task with Get task or List task.
RD Station38

Update webhook

ActionIn the docs only

Changes a webhook already registered in RD Station CRM, typically to point notifications to a new address. It saves you from deleting and recreating the webhook.

When to use it
the service receiving RD Station events moves, and the webhook must follow.
Watch out
confirm the webhook with Get webhook first; there is no official description of this module.
RD Station39

Webhook company create

ActionIn the docs only

Listed by Make as an action tied to company creation in RD Station CRM, with no official description. Its name suggests it concerns the notification sent when a company is created, but the documentation does not confirm it.

When to use it
only after a Run once test shows what it does in your account.
Watch out
do not treat it as a trigger; Make classifies it as an action, and the page cannot promise more than that.
RD Station40

Webhook company update

ActionIn the docs only

This is the counterpart of Webhook company create, this time about company updates, and Make lists it as an action without any description. What it returns or sets up is not documented.

When to use it
once a test run in your own account has shown you its fields and output.
Watch out
for a scenario that starts on its own, the documented instant triggers on this page are the safer choice.
RD Station41

Webhook contact create

ActionIn the docs only

On the contact side, its name ties it to contact creation in RD Station CRM. Make lists it as an action with no official description, so it runs inside a scenario rather than starting one.

When to use it
only after a Run once test has shown you its output. To start a scenario on a new lead, pick Watch New Lead Conversions instead.
Watch out
the documentation is limited, so read the returned bundle before you map anything from it.
RD Station42

Webhook contact update

ActionIn the docs only

Same family, different moment: its name points at edited contacts, not new ones. It is an action without an official description, so its exact behavior is yours to check in the editor.

When to use it
in a scenario that follows existing contacts, once a test has shown you its fields and output.
Watch out
an action never starts a scenario by itself; test with Run once before you rely on it.
RD Station43

Webhook deal created

ActionIn the docs only

On the sales side, its name links it to newly created deals in RD Station CRM. Make lists it as an action with no official description, so what it returns is not documented.

When to use it
in a flow built around a new deal, for instance after Create deal, once you have checked its output.
Watch out
to react to a lead becoming an opportunity, the instant trigger Watch New Opportunities is the documented route.
RD Station44

Webhook deal updated

ActionIn the docs only

Its name ties it to deals that change after creation. Like its neighbors, it is an action without an official description, so confirm its output on your own account first.

When to use it
alongside Update deal or Get deal, when your scenario works on an existing deal rather than a brand new one.
Watch out
run it once, read the bundle, and only then map its data to the next module.
Need help

Need help automating RD Station with Make?

A person reads every message.

FAQ

RD Station and Make: frequent questions

01Is the RD Station Make integration free?
Yes, RD Station is a standard app in Make, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of transfer. Paid plans (Core, Pro, Teams and Enterprise) lift the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution, with usage counted in operations per month. Your RD Station subscription is a separate matter.
02What do you need to connect RD Station to Make?
An RD Station account and a Make account. The documentation lists no other prerequisite. You add an RD Station module, click Create a connection, optionally name it, then authorize Make on the RD Station side or paste the key the app provides, and click Save. The same connection then serves all 46 RD Station modules, so you only do it once per account. Make marks its RD Station CRM documentation as limited, so test each module after connecting.
03Does the RD Station trigger in Make react in real time?
Yes. Both RD Station triggers are instant: Watch New Lead Conversions and Watch New Opportunities. RD Station calls Make through a webhook as soon as the event happens, so there is no polling interval to set, unlike scheduled triggers that Make checks every 15 minutes by default. One exception matters: leads created by import or entered by hand do not fire Watch New Lead Conversions. In the editor, you spot them by the lightning badge on the module. And Watch New Opportunities fires only when a lead is marked as an opportunity.
04What if the RD Station module you need is missing in Make?
Use Make an API Call. It calls any endpoint of the RD Station API with the connection you already have, which covers operations the 46 listed modules do not. You write the request from RD Station's API documentation, then test it with Run once. Keep in mind that Make's own documentation for RD Station CRM is limited and many modules have no description, so reading test output is the reliable way to learn what each one does.
05Should you use Make or n8n for RD Station?
It depends on what you need. On the Make side, the facts are clear: 46 modules, 2 of them instant triggers for conversions and opportunities, plus Make an API Call for anything missing, all available from the Free plan. The same app often has an n8n node too, so compare the operations each tool covers for your exact case. Pick the tool whose modules match your scenario with the least custom work, rather than a general ranking.
Same platform

Other docs you might need on this stack.

Browse all integrations