Resources · Make integration

Rudderstack Make integrationAutomate Rudderstack with Make.

Need the events from your other tools to land in Rudderstack without writing tracking code? The Rudderstack Make integration gives you 3 action modules: Identify, Track and Group. This guide is for ops and growth people, and it walks you from the write key to a working first scenario.

Try the Rudderstack integration on MakeSee the 3 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Rudderstack Make integration do?

It lets Make push people and their actions into Rudderstack. A scenario (the automation you build in Make, a chain of modules) takes data from another app, then a Rudderstack module sends it to your source: who the user is, what they did, or which account they belong to.

Your CRM feeds your customer data. When a deal closes in a sales tool, Identify creates or refreshes the person in Rudderstack, and Track records the purchase as an event. Your downstream destinations get the same story your sales team sees.

Offline actions become events. A webinar attendance, a signed form, a support ticket: none of them fire from your website. Track turns each one into a Rudderstack event, so product analytics no longer misses what happens outside the app.

Accounts stay grouped. For B2B teams, Group ties a user to a company or workspace, which keeps account-level reports honest when a new teammate joins a customer.

What Make does not offer here: there is no trigger, so Rudderstack cannot start a scenario, and there is no module to read data back. The app only sends. Rudderstack often has an n8n node too; the n8n vs Make comparison helps you pick. For a structured start, see the Make training, or check Make pricing before scaling up.

Connect

How do you connect Rudderstack to Make?

  1. 01

    Copy your source write key

    Log in to Rudderstack, open the dashboard and find the source that should receive the events. Note its source write key: that is the only secret Make needs. A connection (your Rudderstack account linked to Make once) is then reused by all 3 modules.

  2. 02

    Add a module and create the connection

    In your scenario, add any Rudderstack module and click Create a connection. The Connection name field is optional, but a clear name helps when you have several sources, one per website or app.

  3. 03

    Paste the key and save

    Enter the write key you copied, or follow the on-screen instructions, then save. The connection appears in the module and you can fill the fields right away, starting with the event you want to send.

First scenario

Your first scenario with Rudderstack

GoalWhen a new lead arrives in another app, Make identifies the person in Rudderstack, then tracks the signup as an event.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + to add the first module. Rudderstack has no trigger, so start with the app where your leads appear, such as a form or a CRM.

  2. 02

    Add Identify

    Click the + on the right of the first module, search Rudderstack and pick Identify. Create the connection with your write key, then map the lead data from the previous module.

  3. 03

    Add Track

    Add one more module with the +, choose Track and describe the action, for example a signup. Map the same person as in Identify so both calls describe one user.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario one time and shows the bundles (one item passed between modules, here one lead) that each module received. Check the event in Rudderstack.

  5. 05

    Schedule and switch it on

    Set the schedule on the first module, every 15 minutes by default, and turn the scenario on. Each module run on a bundle counts as one operation on your Make plan.

Modules

What can Rudderstack do in Make?

Rudderstack gives you 3 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Rudderstack1

Group

Action

In Make“Associates an individual user with a group.”

Group attaches a user to a company, a team or a workspace in Rudderstack, so your tools can report on accounts and not only on single people.

When to use it
a B2B customer adds a teammate in your billing tool, and you want that new seat counted under the right company.
Watch out
send the person through Identify first, so the group points to a profile your destinations already know.
Rudderstack2

Identify

Action

In Make“Identifies a user.”

Identify tells Rudderstack who a person is and what you know about them, so every later event lands on a known profile instead of an anonymous visitor.

When to use it
a lead fills a form, signs a contract or updates their details in your CRM, and the profile needs to follow.
Watch out
it only sends data, it cannot read a profile back, so keep your source of truth in the app that feeds the scenario.
Rudderstack3

Track

Action

In Make“Records a user's actions.”

Track records something a user did as a named event in Rudderstack, which is how actions from tools without tracking code reach your analytics.

When to use it
an invoice is paid, a demo is booked or a ticket is closed outside your product, and you want it in the same timeline as in-app clicks.
Watch out
name events the same way your website does, or reports will split one action into two.
Need help

Need help automating Rudderstack with Make?

A person reads every message.

FAQ

Rudderstack and Make: common questions

01Is the Rudderstack Make integration free?
Yes, Rudderstack is a standard app, so you can use it on the Make Free plan. The Free plan limits you to 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute and remove the cap on active scenarios. Usage is counted in operations: one module run on one bundle. Your Rudderstack plan is a separate matter.
02What do you need to connect Rudderstack to Make?
An active Rudderstack account and the source write key of the source that should receive your events. You find the key in the Rudderstack dashboard, on that source. In Make, you add a Rudderstack module, click Create a connection, give it a name if you like and paste the key. The same connection then serves Identify, Track and Group. If you send events to several sources, create one connection per source so each scenario writes to the right place.
03Can the Rudderstack Make integration react in real time?
No, not on its own: Rudderstack has no trigger in Make, only 3 action modules. A scenario therefore starts elsewhere. Either another app launches it, such as a form or a CRM with an instant trigger that calls Make through a webhook as soon as something happens, or Make runs it on a schedule, every 15 minutes by default. The Rudderstack modules then send the data at the end of the chain, once the first module has passed its bundles along.
04What if a Rudderstack module is missing in Make?
It depends on what you need. The app has only three modules, Identify, Track and Group, and no Make an API Call module, so you cannot call other Rudderstack endpoints from this app. Everything here goes one way: into Rudderstack. If you need to read data back or trigger a scenario from Rudderstack, the answer lies in another app of your stack, or in a scenario built around your data pipeline. The Hackceleration team can look at your case and suggest a route.
05Make or n8n for Rudderstack?
It depends on your team. Rudderstack is available in Make with three action modules, and the same app often has an n8n node as well, so both tools can send your events. The choice comes down to where your other automations already live and which editor your team prefers to maintain. Compare the modules each tool offers for Rudderstack against the calls you need, then test a small scenario in each before moving your event flows.
Same platform

Other docs you might need on this stack.

Browse all integrations