Resources · Make integration

Candu Make integrationAutomate Candu with Make.

Can Make keep Candu informed about what your users do elsewhere? The Candu Make integration offers 3 action modules and no trigger. This guide is for product and growth teams: connect your key, then build a first scenario that sends events.

Try the Candu integration on MakeSee the 3 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Candu Make integration do for you?

The Candu Make integration lets a Make scenario (the automation you build, a chain of steps) push information into Candu without writing code. Each step is a module, one brick of the scenario. Candu brings three of them, all actions: Send an Identify Event, Send a Track Event and Make an API Call.

A known user, right when they sign up. A form tool or your CRM starts the scenario, then Send an Identify Event hands that person over to Candu, so the content you show can be built around people Candu already knows.

A product milestone recorded. When another app reports that a customer finished an onboarding step or upgraded, Send a Track Event passes that moment to Candu as an event.

Anything the two modules skip. Make an API Call reaches the rest of the Candu API with the same connection, which is the way out when neither event module covers your need.

What Make does not offer here: no Candu trigger, so Candu itself never starts a scenario, and no search module to read data back. Make also flags its own Candu documentation as AI-generated and possibly wrong, so check important details with Candu. For the wider picture, the Make review and the Make pricing page help you size the tool, and if you are weighing another platform, n8n vs Make lays out the criteria.

Connect

How do you connect your Candu account to Make?

  1. 01

    Copy your API key in Candu

    In Candu, open the workspace settings page and look for the Access Keys section. The API key sits right there on screen: copy it. You need an active Candu account for this key to exist.

  2. 02

    Open the connection window in Make

    Add any Candu module to your scenario, then click Create a connection. A connection is your Candu account linked to Make once, and every Candu module in your scenarios reuses it afterward.

  3. 03

    Name it and paste the key

    The Connection name field is optional, but a clear name helps when you manage several workspaces. Paste the API key you copied, confirm, and the module is ready to be filled in.

First scenario

Your first scenario with Candu

GoalWhen a new user appears in another app, Make identifies them in Candu, then records a first track event.

  1. 01

    Start from the app that knows your users

    On the Scenarios page, create a new scenario and click the +. Since Candu has no trigger, pick the trigger of the app where signups happen, such as your form tool or CRM.

  2. 02

    Add Send an Identify Event

    Click the + on the right of that first module, search for Candu and choose Send an Identify Event. Click Create a connection and paste your API key.

  3. 03

    Map the user data

    Fill the module fields with data coming from the first module. Each bundle, one item passing between modules, carries one person, so each new user becomes one identify event.

  4. 04

    Chain Send a Track Event

    Add Send a Track Event after the identify module and map the same person, so the milestone you record is attached to the user you just introduced to Candu.

  5. 05

    Test with Run once

    Click Run once. Make runs the scenario one time and shows the bundles each module received. Create a test user in your source app first, so there is something to send.

  6. 06

    Set the schedule and switch it on

    On the first module, check the schedule: a new scenario runs every 15 minutes by default, 15 minutes being the minimum on the Free plan. Then switch the scenario on.

Modules

What each Candu module does

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

Candu1

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Opens the whole Candu API to your scenario, reusing the connection you already created, so you are not stuck with the two event modules.

When to use it
a Candu feature you need has no dedicated module, and waiting for one is not an option for your workflow.
Watch out
you build the request yourself from the Candu API documentation, so test it with Run once before turning the scenario on.
Candu2

Send an Identify Event

Action

In Make“Sends an identify event.”

Tells Candu about a person through an identify event, built from data another app just handed to Make, with no export or import in between.

When to use it
right after a signup, a new CRM contact or an account change, before any track event about that person.
Watch out
one bundle means one identify event and one operation, so a trigger that returns many users at once counts many operations.
Candu3

Send a Track Event

Action

In Make“Sends a track event.”

Records something a user did as a track event in Candu, so a moment that happens in another tool, such as a paid invoice or a finished setup step, reaches Candu too.

When to use it
choose it over Send an Identify Event when you describe an action, not who the person is.
Watch out
place it after the identify module when the user may be new to Candu.
Need help

Need help automating Candu with Make?

A person reads every message.

FAQ

Candu and Make: frequent questions

01Is the Candu Make integration free?
Yes, on the Make side. Candu is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution per run and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute and remove the cap on active scenarios. Every module execution counts as one operation on your plan. You still need an active Candu account, and its subscription is a separate matter handled on the Candu side.
02What do you need to connect Candu to Make?
Two things: an active Candu account and its API key. You find the key in the workspace settings of Candu, in the Access Keys section, where it is displayed on screen. In Make, add a Candu module, click Create a connection, optionally give the connection a name, then paste the key. That single connection serves the three Candu modules in all your scenarios, so you only do this once per workspace.
03Can Candu trigger a Make scenario in real time?
No. Candu has no trigger module in Make, so it never starts a scenario on its own. The scenario begins with another app: an instant trigger of that app, which calls Make through a webhook as soon as something happens, or a scheduled trigger that Make checks on the scenario's schedule. A new scenario runs every 15 minutes by default. The Free plan cannot go below 15 minutes, while paid plans go down to 1 minute.
04What if the Candu module you need is missing in Make?
Use Make an API Call. It calls any endpoint of the Candu API from your scenario, with the same connection as the other modules, so it covers what Send an Identify Event and Send a Track Event leave out. You write the request from the Candu API documentation. Also keep in mind that Make marks its Candu documentation as AI-generated and possibly inaccurate: when a detail matters, confirm it with Candu directly.
05Should you use Make or n8n for Candu?
It depends on what you already run. On Make, Candu comes with two ready event modules plus Make an API Call, a key-based connection and access from the Free plan. Many apps also have an n8n node, so check whether Candu does before choosing. The n8n vs Make comparison linked earlier on this page sets out the criteria side by side, without declaring a winner, so the choice follows the way you already work and the tools your team runs.
Same platform

Other docs you might need on this stack.

Browse all integrations