Resources · Make integration

CrowdPower Make integrationAutomate CrowdPower with Make.

What if every new customer reached CrowdPower without anyone typing it in? The CrowdPower Make integration gives you 5 action modules to push customers, events, tags and charges from your other tools. This guide shows how to connect your account and build a first scenario step by step.

Try the CrowdPower integration on MakeSee the 5 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the CrowdPower Make integration do for you?

The CrowdPower Make integration lets Make write into your CrowdPower account for you: it adds or updates customers, records events, tags and charges on them, and can call the rest of the CrowdPower API. You build this as a scenario, the automation you assemble in Make from small bricks called modules.

A customer base that stays current. When a lead fills out a form in another tool, Upsert a Customer sends that person to CrowdPower, creating the record or refreshing it if it already exists. Nobody copies contacts by hand anymore.

A history of what people actually do. Pair it with Create a Customer Event so a download, a booking or a signup shows up on the customer's timeline, then use Create a Customer Tag to sort people into segments your marketing team can target.

Revenue tied to each profile. When your shop or billing tool confirms a sale, Create a Customer Charge records it on the matching customer, so purchases and campaigns sit side by side.

What Make does not give you here: CrowdPower has no trigger module, so the app cannot start a scenario on its own. The flow always begins in another app or on a schedule. Make also warns that its CrowdPower documentation is limited because little public information exists, so test each module with real data before relying on it. The Make troubleshooting guide helps when a run fails.

New to the tool? Our Make review covers the basics, and n8n vs Make helps if you are weighing both platforms.

Connect

How do you connect CrowdPower to Make?

  1. 01

    Add a CrowdPower module

    In your scenario, add any CrowdPower module, for example Upsert a Customer, then click Create a connection. A connection is your CrowdPower account linked to Make once, then reused by every CrowdPower module.

  2. 02

    Name the connection

    Give the connection a name if you like, such as the workspace or client it belongs to. This step is optional, but it saves guesswork later when several accounts sit side by side in the same Make organization.

  3. 03

    Authorize and save

    Either approve Make on the CrowdPower page that opens, or paste the key CrowdPower gives you, depending on what the window asks for. Then click Save, and the module is ready to fill in.

First scenario

Your first scenario with CrowdPower

GoalWhen a new signup lands in another app, Make adds that person to CrowdPower and logs a matching event on their profile.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + to add the first module. It will come from the app where signups start, such as your form tool, since CrowdPower has no trigger.

  2. 02

    Add Upsert a Customer

    Click the + to the right of that first module, search for CrowdPower and pick Upsert a Customer. Create the connection, then map the person's details coming from the previous module.

  3. 03

    Log the event

    Add Create a Customer Event right after. Map the customer from the step before and describe what happened, for instance a completed signup, so the timeline tells the story.

  4. 04

    Test with Run once

    Click Run once to execute the scenario a single time. Open each module to read the bundles it received, a bundle being one item passed along, then check the customer in CrowdPower.

  5. 05

    Schedule and switch on

    Set the schedule on the first module, which is every 15 minutes by default, and turn the scenario on. From then on, each new signup travels to CrowdPower without you.

Modules

What each CrowdPower module does

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

CrowdPower1

Create a Customer Charge

ActionIn the docs only

Records a charge on a CrowdPower customer, so the money a person has paid shows up next to the rest of their profile and your campaigns can be read against real revenue.

When to use it
right after a payment or order is confirmed in your shop or billing app, to copy that sale onto the right customer.
Watch out
run Upsert a Customer first in the same scenario, so the charge always lands on a customer that exists.
CrowdPower2

Create a Customer Event

ActionIn the docs only

Adds an event to a customer's history in CrowdPower, giving you a trace of what that person did: a webinar joined, a quote requested, a trial started.

When to use it
whenever an action happening outside CrowdPower should become part of the customer's timeline, typically after a form, booking or product action.
Watch out
each event costs one operation, a single run of one module that Make counts on your plan, so filter out noise before this step.
CrowdPower3

Create a Customer Tag

ActionIn the docs only

Puts a tag on a CrowdPower customer, which gives your team a quick label to group people, build segments and aim a campaign at exactly the right list.

When to use it
when a detail from another tool, such as the product bought or the source of a lead, should decide which segment someone joins.
Watch out
keep tag names consistent from one scenario to the next; two spellings of the same idea split your segment in half.
CrowdPower4

Make an API Call

ActionIn the docs only

Lets you reach any endpoint of the CrowdPower API from your scenario, using the same connection as the other modules, which covers whatever the four ready-made modules leave out.

When to use it
when you need a CrowdPower feature that has no dedicated module, for example reading data back, if CrowdPower's API offers it.
Watch out
you have to know the endpoint and the request format yourself, from CrowdPower's own API reference, since Make's documentation stays limited here.
CrowdPower5

Upsert a Customer

ActionIn the docs only

Creates the customer in CrowdPower when they are new and updates the existing record when they are already there, so one module keeps your base clean without duplicates to sort out.

When to use it
as the first CrowdPower step of almost any scenario, before an event, a tag or a charge is attached to that person.
Watch out
Make's documentation does not say which field CrowdPower uses to spot an existing customer, so test with a known contact before switching on.
Need help

Need help automating CrowdPower with Make?

A person reads every message.

FAQ

CrowdPower and Make: common questions

01Is the CrowdPower Make integration free?
Yes, CrowdPower is a standard app in Make, available from the Free plan. That plan gives you 2 active scenarios, runs scheduled at least 15 minutes apart, up to 5 minutes of execution per run, files up to 5 MB 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. Usage is counted in operations each month, one per module run on one bundle.
02What do you need to connect CrowdPower to Make?
A CrowdPower account and a Make account. Make's documentation lists no specific prerequisite for this app. You add a CrowdPower module, click Create a connection, optionally name it, then either authorize Make on the CrowdPower page or paste the key CrowdPower provides, and save. The same connection then serves all five CrowdPower modules, including Make an API Call, so you only do this once per account. If authorization fails, check in your CrowdPower account which access or key it actually provides.
03Does the CrowdPower Make integration have a real-time trigger?
No. CrowdPower has no trigger module in Make, scheduled or instant, so a scenario never starts from CrowdPower itself. You start it from another app instead: a trigger in your form tool, shop or CRM, or a schedule set on the first module, every 15 minutes by default. CrowdPower modules then come after that first step and receive the data it passes along. To see it work, click Run once and read what each CrowdPower module received.
04What if the CrowdPower module you need is missing?
Use Make an API Call. It reaches any endpoint of the CrowdPower API with the connection you already set up, so you can cover what the four dedicated modules do not, such as reading data if CrowdPower's API allows it. You will need the endpoint details from CrowdPower's own API reference: Make states that its documentation for this app is limited because too little public information exists about it. Test each call with Run once before you switch the scenario on.
05Should you use Make or n8n for CrowdPower?
It depends on the tool your team already works in. On the Make side, CrowdPower offers five modules, all actions: customers, events, tags, charges and a generic API call. Many apps also have an n8n node, so check whether one exists for CrowdPower before you choose. Compare the modules available on each side against your scenario rather than the platform name, and start with the one that covers your flow.
Same platform

Other docs you might need on this stack.

Browse all integrations