Resources · Make integration

ClubPlanner Make integrationAutomate ClubPlanner with Make.

Every lead that lands somewhere else can end up in ClubPlanner on its own. The ClubPlanner Make integration offers 2 action modules, one to add a prospect and one to call the API. This page shows how to link your account and build a first working scenario.

Try the ClubPlanner integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the ClubPlanner Make integration do for you?

The integration lets Make write into ClubPlanner for you. A scenario, which is the automation you build in Make, picks up data from another tool and hands it to a ClubPlanner module, so a new prospect appears in your club software without anyone typing it in again.

Leads from your website form, captured. Start the scenario with the trigger of your form tool, then let Add a Prospect push each new contact into ClubPlanner. Your sales staff see the lead where they already work.

Contacts from a campaign or a chat, in one place. The same pattern works with a messaging app or an ad platform: whatever collects the details, Add a Prospect is the step that files them in ClubPlanner.

Anything else the API allows. When you need more than adding prospects, Make an API Call reaches the ClubPlanner API with the connection you already set up.

Know the limits before you start. ClubPlanner has no trigger in Make, so a scenario never starts from something happening inside ClubPlanner; it starts from another app or from a schedule. Make also says its own documentation for this app is limited, because little public information about ClubPlanner is available. If you are still deciding on the platform, the n8n vs Make comparison and our Make review help, and Make pricing explains how operations are counted.

Connect

How do you connect ClubPlanner to Make?

  1. 01

    Add a ClubPlanner module

    In your scenario, click the +, search for ClubPlanner and pick Add a Prospect. Then click Create a connection. A connection is your ClubPlanner account linked to Make once and reused by every ClubPlanner module.

  2. 02

    Name the connection

    Giving it a name is optional, but it pays off when you manage several clubs or accounts: a clear label such as the club name tells you which account a module writes into.

  3. 03

    Authorize and save

    Depending on what ClubPlanner asks for, approve Make on the ClubPlanner page that opens or paste the key ClubPlanner gives you. Click Save, and the connection is ready for every ClubPlanner module.

First scenario

Build your first scenario with ClubPlanner

GoalWhen a new lead arrives in another app, Make adds that person to ClubPlanner as a prospect.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + to add the first module. Because ClubPlanner has no trigger, this first module comes from the app where your leads arrive.

  2. 02

    Pick the lead source

    Search for your form or messaging app, choose its trigger and connect that account. Each new lead becomes a bundle, meaning one item passed from module to module.

  3. 03

    Add the prospect step

    Click the + on the right of the first module, search ClubPlanner and choose Add a Prospect. Link your connection, then map the lead's details from the previous module into its fields.

  4. 04

    Test with Run once

    Send a test entry through your form, click Run once and open the bundles each module received. Check in ClubPlanner that the prospect showed up the way you expected.

  5. 05

    Schedule and switch on

    Set the schedule on the first module (every 15 minutes by default for a new scenario) and switch the scenario on. From then on, leads flow into ClubPlanner without a copy and paste.

Modules

What the ClubPlanner modules do

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

ClubPlanner1

Add a Prospect

ActionIn the docs only

This action puts a new person into ClubPlanner as a prospect, so every lead collected elsewhere lands in the tool your club already uses to follow up. Your team follows up from ClubPlanner instead of chasing leads in several tools.

When to use it
right after the step that captures a lead, such as a website form, a chat or a signup list from an event.
Watch out
each run adds one prospect per bundle, so test with Run once before switching on to avoid filling ClubPlanner with duplicates.
ClubPlanner2

Make an API Call

ActionIn the docs only

This module reaches any endpoint of the ClubPlanner API from your scenario, reusing the connection you already created. This is how you cover what Add a Prospect does not.

When to use it
when your process needs something other than adding a prospect and ClubPlanner's API offers it.
Watch out
you describe the request yourself, so keep ClubPlanner's API documentation at hand; Make's own documentation for this app is limited.
Need help

Need help automating ClubPlanner with Make?

A person reads every message.

FAQ

ClubPlanner and Make: common questions

01Is the ClubPlanner Make integration free?
Yes, ClubPlanner is a standard app in Make, so it is available on the Free plan. The Free plan lets you keep 2 active scenarios, with at least 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, remove the cap on active scenarios and allow 40 minutes of execution. Usage is counted in operations, one operation being one module run on one bundle.
02What does the ClubPlanner Make connection require?
You need a ClubPlanner account and a Make account. Make's documentation lists no prerequisite for this app and no specific connection steps, so the generic flow applies: add a ClubPlanner module, click Create a connection, optionally name it, then authorize Make on the ClubPlanner page or paste the key ClubPlanner provides, and click Save. If the screen asks for a value you do not have, ClubPlanner support is the right place to ask for API access.
03Can a ClubPlanner scenario react in real time?
Not from ClubPlanner itself, because the app has no trigger in Make: nothing that happens inside ClubPlanner can start a scenario. The scenario starts from another app instead. If that app has an instant trigger, which the app calls through a webhook as soon as something happens, the prospect is added right away. With a scheduled trigger, Make checks on the schedule you set, every 15 minutes by default, and you can change that interval.
04What if a ClubPlanner module is missing in Make?
It depends on the ClubPlanner API. Make offers only 2 modules for this app, but one of them is Make an API Call, which can reach any endpoint of the ClubPlanner API with the same connection. If the API offers the action you want, that module covers it. Keep in mind that Make describes its documentation for ClubPlanner as limited, so the API reference from ClubPlanner is the source to follow.
05Make or n8n for ClubPlanner: which one fits?
It depends on the tools the rest of your process already runs on. In Make, ClubPlanner comes with Add a Prospect and Make an API Call, and a scenario starts from another app because ClubPlanner has no trigger. The same app often has an n8n node too, so check which modules each platform offers for your exact need, and pick the tool your team will maintain. Our comparison of the two, linked above, sets out the criteria.
Same platform

Other docs you might need on this stack.

Browse all integrations