Resources · Make integration

Growth-X Make integrationAutomate Growth-X with Make.

Can Make react to new Growth-X connections and move people into campaigns for you? Yes. The Growth-X Make integration offers 8 modules, 4 triggers and 4 actions. This guide links your account, builds a first scenario and explains each module.

Try the Growth-X integration on MakeSee the 8 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Growth-X Make integration let you automate?

The Growth-X Make integration links your Growth-X account to Make, a no-code tool where you build a scenario: an automation made of modules, each one a brick that watches, acts or searches. Growth-X brings 4 watch triggers and 4 actions, so tags, messages, connections and campaigns can feed or receive data from your other apps.

Enroll fresh contacts without copy and paste. Watch New Connections picks up each new connection in Growth-X, and Add Receiver to a Campaign places that person in the campaign you pick. Nobody has to open Growth-X to do it by hand.

Let a tag decide what happens next. A sales team that tags prospects in Growth-X can start a scenario with Watch Attached Tags, then pull the person out of a campaign with Remove Receiver from a Campaign once they are qualified.

Keep other tools in the loop. Watch Messages and Watch Updated Connections pass Growth-X activity to the rest of your stack, and Send Message to a Receiver writes back when an event elsewhere calls for a reply.

Two limits to know. Make's Growth-X documentation says it was generated by AI from the vendor's docs and may contain mistakes, so check anything critical with Growth-X. It also lists no fields for these modules: you discover them in the editor once the connection exists. If you are still choosing a tool, the n8n vs Make comparison lays out the criteria, Make pricing covers plans, and Make training helps you go further.

Connect

How do you connect Growth-X to Make?

  1. 01

    Copy your Growth-X API key

    You need an active Growth-X account. Open its Settings section, click the API tab, and copy the API key shown on screen. Keep it at hand: Make asks for it in the next step.

  2. 02

    Add a Growth-X module in Make

    In your Make account, open a scenario, add any Growth-X module and click Create a connection. A connection is your Growth-X account linked to Make once, then reused by every Growth-X module.

  3. 03

    Name it and paste the key

    The Connection name field is optional, but a clear label helps when a team shares scenarios. Paste the API key you copied, or follow the on-screen instructions, and save. The module can now read your Growth-X data.

First scenario

Your first scenario with Growth-X and Make

GoalWhen a new connection appears in Growth-X, Make adds that person to a campaign you choose.

  1. 01

    Create the scenario

    Go to the Scenarios page, create a new scenario and click the + to add the first module. Search for Growth-X and pick Watch New Connections.

  2. 02

    Link your account

    Click Create a connection and paste your API key. Once the connection exists, Make can list what it reads in Growth-X, which makes the module fields easier to fill.

  3. 03

    Add the campaign action

    Click the + on the right of the trigger and choose Add Receiver to a Campaign. Pick the campaign, then map the person from the bundle, the item the trigger hands over.

  4. 04

    Test with Run once

    Click Run once. Make executes the scenario one time and shows the bundles each module received, so you can confirm the right person landed in the right campaign.

  5. 05

    Schedule it and switch it on

    Open the clock on the first module. A new scenario checks every 15 minutes by default, and 15 minutes is also the shortest interval on the Free plan. Then switch the scenario on.

Triggers

Growth-X triggers: what starts your scenario

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

Growth-X1Watch Attached Tags

Watch Attached Tags

triggerIn the docs only

Turn a tag in Growth-X into a starting signal: each time a tag gets attached, your scenario receives it as a bundle and can act on it, whether that means updating a CRM record or pinging a colleague.

How it fires
scheduled. The docs give no type, but the Watch name points to a scheduled trigger: Make checks Growth-X on the scenario's schedule, and tags added between two checks arrive together. The clock badge on the module confirms it.
When to use it
your team already tags prospects by stage or interest and wants that label to trigger the follow-up.
Watch out
the docs list no filter for this trigger, so add a filter in Make if only one tag should matter.
Growth-X2Watch Messages

Watch Messages

triggerIn the docs only

Get every Growth-X message into the tools where your team already works. Each message the trigger picks up becomes a bundle you can log, forward or route to the right person.

How it fires
scheduled. Make queries Growth-X at the interval set on the scenario, not the moment a message lands.
When to use it
replies should reach a shared inbox, a spreadsheet or a sales channel without anyone watching Growth-X.
Watch out
avoid pairing it with Send Message to a Receiver in the same scenario unless a filter stops your own messages, or the scenario may react to what it just sent.
Growth-X3Watch New Connections

Watch New Connections

triggerIn the docs only

Catch each new connection recorded in Growth-X and hand it to the next module, which is the cleanest way to act on fresh contacts as soon as your scenario runs.

How it fires
scheduled. On every run, Make asks Growth-X what changed since the last check and passes each new connection along.
When to use it
you want new contacts added to a campaign, a CRM or a welcome routine without manual work.
Watch out
the connections this trigger watches live in Growth-X (going by the name, your contacts there). They have nothing to do with the Make connection that stores your API key.
Growth-X4Watch Updated Connections

Watch Updated Connections

triggerIn the docs only

Hear about changes to contacts you already have in Growth-X, so the copy of that person kept in another app stays in step with Growth-X instead of drifting.

How it fires
scheduled. Make polls Growth-X on the scenario's schedule and returns the connections that were updated.
When to use it
a CRM or a sheet mirrors your Growth-X contacts and must reflect edits made there.
Watch out
each updated connection is one bundle, and every module that handles it uses an operation, the unit Make counts on your plan. Keep only the modules you need.
Modules

Growth-X actions in Make

Growth-X gives you 4 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Growth-X1

Add Receiver to a Campaign

ActionIn the docs only

Put a person into an existing Growth-X campaign straight from your scenario, so enrollment happens the moment the data arrives rather than whenever someone finds the time.

When to use it
a trigger, a form or another app hands you a lead who belongs in a campaign you already run.
Watch out
the docs list no fields here, so open the module after connecting and check what it expects before mapping.
Growth-X2

Make an API Call

ActionIn the docs only

Reach any endpoint of the Growth-X API with the connection you already set up. This is your fallback for everything the seven ready-made modules leave out.

When to use it
you need a Growth-X operation that no listed trigger or action covers.
Watch out
you build the request yourself, so test the call with Run once and read the bundle it returns before relying on it.
Growth-X3

Remove Receiver from a Campaign

ActionIn the docs only

Take someone out of a Growth-X campaign automatically, which keeps people who already answered or bought from getting messages meant for cold prospects.

When to use it
a deal closes in your CRM, or a tag in Growth-X marks the person as done.
Watch out
place a filter before it, because a scenario that removes the wrong receiver stops their campaign without asking.
Growth-X4

Send Message to a Receiver

ActionIn the docs only

Send one Growth-X message to one receiver from inside a scenario, with text you can build from data gathered by earlier modules.

When to use it
an event outside Growth-X, like a signed quote or a booked call, deserves a direct note to that person.
Watch out
a message sent is gone. Run once with a test receiver first, and read the bundle before switching the scenario on.
Need help

Need help automating Growth-X with Make?

A person reads every message.

FAQ

Growth-X and Make: common questions

01Is the Growth-X Make integration free?
Yes, on the Make side. Growth-X is a standard app, 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 data transfer. Paid plans (Core, Pro, Teams, Enterprise) lower the interval to 1 minute and remove the cap on active scenarios. You still need an active Growth-X account with its own subscription; see the Growth-X pricing page for that part.
02What do you need to connect Growth-X to Make?
Two things: an active Growth-X account and its API key. You find the key in Growth-X under Settings, in the API tab, and copy it. In Make, add a Growth-X module, click Create a connection, give it a name if you like, and paste the key. That single connection then serves all 8 Growth-X modules, so you enter the key only once, even across several scenarios. If several people build scenarios, give the connection a clear name.
03Do Growth-X triggers in Make fire in real time?
Most likely not. Make's docs list the 4 Growth-X triggers without stating their type; their Watch names point to scheduled triggers, which Make checks on the scenario's schedule, not the instant something happens. The clock badge on the module in the editor confirms it (a lightning badge would mean instant). A new scenario runs every 15 minutes by default, which is also the shortest interval on the Free plan; paid plans go down to 1 minute. Events that happen between two checks are picked up together at the next run, one bundle per tag, message or connection.
04What if a Growth-X module you need is missing in Make?
Use Make an API Call. It reaches any endpoint of the Growth-X API with the same connection, so you can cover what the 7 other modules do not. You build the request yourself. Also note that Make's documentation for this app was generated by AI from Growth-X's docs and may contain mistakes: confirm anything important directly with Growth-X. Test every custom call with Run once before switching the scenario on.
05Should you use Make or n8n for Growth-X?
It depends on the tool your team already uses. On Make, Growth-X comes ready with 8 modules, a single API key connection and a Free plan to start. Many apps also have an n8n node, so check whether Growth-X does before deciding. Nothing here ranks the two: compare how each one fits your existing scenarios, who will maintain them, and which modules you actually need. The n8n vs Make comparison linked above goes through those criteria in detail.
Same platform

Other docs you might need on this stack.

Browse all integrations