Resources · Make integration

Convercus Loyalty Make integrationAutomate Convercus Loyalty with Make.

Can your loyalty program run itself while your other tools do the talking? The Convercus Loyalty Make integration gives you 27 modules: 26 actions and 1 search. This page shows ops and CRM teams how to connect the account and build a first working scenario.

Try the Convercus Loyalty integration on MakeSee the 27 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Convercus Loyalty Make integration do for you?

The Convercus Loyalty Make integration lets a Make scenario (the automation you build, a chain of bricks called modules) create users, accounts, coupons and bookings in your loyalty program, then read balances and levels back. Your shop, CRM and support tools feed the program, and nobody retypes a customer by hand.

Welcome rewards that follow the signup. A lead completes a form in another app. Create a User adds the person, Create a Membership enrolls them, and Assign a Coupon hands over the welcome offer in the same run.

Support tickets answered with real figures. An agent opens a request about rewards. Get the Account Balance and Get Account Level fetch the numbers and drop them into the ticket, so nobody switches screens.

Levels that move without a spreadsheet. Get Program Rating Levels reads the levels your program defines, and Update Account Rating Level moves a customer when your own rule says so.

What Make does not do here: the app has no trigger, so a scenario starts on a schedule or on another app's event. Make also states that its documentation for Convercus Loyalty is limited, which means every field is something you discover in the editor. When a request falls outside the listed modules, Make an API call reaches the rest of the API with the same connection. The Make review covers the editor itself, Make troubleshooting helps when a run fails, and n8n vs Make puts both tools side by side.

Connect

How do you connect Convercus Loyalty to Make?

  1. 01

    Add a Convercus Loyalty module

    In your scenario, click the +, search for Convercus Loyalty and pick any module, for example Get a User. Then click Create a connection. A connection is your Convercus account linked to Make once and reused by every module of the app.

  2. 02

    Name the connection

    Give it a name you will recognize later, such as the program or the environment it points to. This step is optional, but it helps the day you run a test program and a live one side by side in the same Make organization.

  3. 03

    Authorize and save

    Follow what the window asks: either approve Make on the Convercus page or paste the key your Convercus account gives you. The doc does not say which method this app uses. Click Save, and the module can now list what it reads.

First scenario

Your first scenario with Convercus Loyalty

GoalWhen a new customer arrives from another app, Make creates the user in Convercus Loyalty and assigns them a coupon.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the +. Pick the app where new customers show up first, a form tool or your shop, since Convercus Loyalty has no trigger of its own.

  2. 02

    Add Create a User

    Click the + on the right of the first module, search Convercus Loyalty and choose Create a User. Select your connection, then map the customer data coming from the previous module into the fields Make shows.

  3. 03

    Hand over the coupon

    Add Assign a Coupon after it. Map the user returned by Create a User, so the reward goes to the person you just added rather than to a fixed value typed once.

  4. 04

    Test with Run once

    Click Run once with a test customer. Each module shows the bundles it received (a bundle is one item passed along, here one customer). Check that the user and the coupon appear in Convercus.

  5. 05

    Schedule and switch on

    Open the clock on the first module. A new scenario checks every 15 minutes by default, and the Free plan cannot go below that. Set the schedule, then switch the scenario on.

Modules

What each Convercus Loyalty module does

Convercus Loyalty gives you 27 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Convercus Loyalty1

Assign a Coupon

ActionIn the docs only

Hands a coupon to a member of your program from inside a scenario, so a reward reaches the right person without anyone opening Convercus.

When to use it
a customer finishes a signup in another app and the welcome reward should be attached during the same run.
Watch out
map the user from an earlier module rather than typing a value, or every run rewards the same person.
Convercus Loyalty2

Create a Booking

ActionIn the docs only

Records a booking in Convercus Loyalty straight from your scenario, so an event captured in another tool shows up on the loyalty side without retyping it.

When to use it
an order gets paid in your online store and the program should hear about it without anyone typing it in again.
Watch out
Make does not describe what a booking holds for this app, so connect first and read the fields the module proposes.
Convercus Loyalty3

Create a Membership

ActionIn the docs only

Enrolls someone in a membership, which puts them inside your loyalty program the moment the scenario runs.

When to use it
right after Create a User, when a new person should join a program in the same pass instead of waiting for a manual step.
Watch out
run it once on a test user and check the membership in Convercus before you let real signups flow through.
Convercus Loyalty4

Create a Transaction

ActionIn the docs only

Logs a transaction in Convercus Loyalty from any event Make can catch, which keeps the program history in line with your sales tools.

When to use it
a sale closes in your checkout app and you want it written to the loyalty side.
Watch out
Create an Account Transaction also exists, and the doc does not explain the difference, so compare both in the editor before choosing.
Convercus Loyalty5

Create a User

ActionIn the docs only

Adds a new user to Convercus Loyalty, giving every customer captured elsewhere a place in your program.

When to use it
a form, a CRM or a shop app hands you a new customer and nobody should copy the details by hand.
Watch out
if the same customer can come through twice, add a check before this module so repeated runs do not pile up copies.
Convercus Loyalty6

Create an Account

ActionIn the docs only

Opens an account in Convercus Loyalty, the record that the balance, level and booking modules on this page are named after.

When to use it
onboarding a new customer in one run, together with Create a User and Create a Membership.
Watch out
Delete an Account can remove it later, so keep a dedicated test account for your trials rather than touching a live one.
Convercus Loyalty7

Create an Account Transaction

ActionIn the docs only

Writes a transaction against one specific account, as its name says, so the movement is tied to that account inside the program.

When to use it
the scenario already holds the account from Get an Account or Create an Account and you want to record something on it.
Watch out
pick between this and Create a Transaction after reading the fields Make shows for each one.
Convercus Loyalty8

Create an Identifier

ActionIn the docs only

Creates an identifier in Convercus Loyalty, so a customer can be recognized by one more reference than before.

When to use it
another system issues a new reference for a customer and Convercus should know about it without a manual update.
Watch out
call Get the Account Identifiers earlier in the run to see what the account already carries and avoid adding the same reference twice.
Convercus Loyalty9

Delete a User

ActionIn the docs only

Removes a user from Convercus Loyalty, which lets a scenario handle an erasure request without a manual cleanup in the back office.

When to use it
a customer asks your support tool to erase their data and the loyalty record should go too.
Watch out
a delete cannot be undone, so check the user with Get a User first and test with Run once on a dummy record.
Convercus Loyalty10

Delete an Account

ActionIn the docs only

Clears an account you no longer need out of Convercus Loyalty, straight from your scenario and without a trip to the program settings.

When to use it
an account opened for a test, or tied to a closed customer file, must disappear.
Watch out
nothing brings it back, so confirm the target with Get an Account in the same run before this module fires.
Convercus Loyalty11

Get Account Bookings

ActionIn the docs only

Pulls the bookings tied to one account, so you can reuse that history in a report, a message or a spreadsheet.

When to use it
a support agent needs a customer's recent activity pasted into a ticket before replying.
Watch out
the doc does not say how the bookings come back; read the output after Run once before you map anything into the next module.
Convercus Loyalty12

Get Account Level

ActionIn the docs only

Tells you which level an account sits at, the value you need to personalize a message or send a customer down a different path.

When to use it
your email tool should greet top-level members with a different message than newcomers.
Watch out
Update Account Rating Level changes this value; keep reading and writing in separate modules so you can compare before and after.
Convercus Loyalty13

Get Program Rating Levels

ActionIn the docs only

Lists the rating levels your program defines, so the scenario works with the real names instead of values typed from memory.

When to use it
just before Update Account Rating Level, to confirm the level you are about to set actually exists in the program.
Watch out
run it once and look at the bundle, since the doc gives no detail on what each level carries.
Convercus Loyalty14

Get User Registration Data

ActionIn the docs only

Fetches the data a user gave when registering, handy when another tool needs that profile and you would rather skip an export.

When to use it
a CRM contact is incomplete and you want to fill the gaps from what the customer entered at signup.
Watch out
the doc does not list what this data contains; inspect the bundle after Run once before mapping.
Convercus Loyalty15

Get a Membership

ActionIn the docs only

Reads one membership so the scenario knows where a person stands in the program before it acts on them.

When to use it
a coupon or a message should only go to people whose membership you have just checked.
Watch out
run it once and read the bundle, since the doc does not describe what a membership record holds for this app.
Convercus Loyalty16

Get a User

ActionIn the docs only

Returns one user's record, the starting point when you already know exactly who you are after.

When to use it
a previous module gave you the user's reference and the next step needs their details.
Watch out
with only partial information, Search is the better pick, because it can return zero, one or several results instead of a single record.
Convercus Loyalty17

Get an Account

ActionIn the docs only

Brings back a single account, which gives the rest of the scenario the details it needs to credit, update or delete it safely.

When to use it
before Delete an Account or an account transaction, to make sure the scenario targets the right one.
Watch out
map the account reference from an earlier module; a value typed by hand ties every run to the same account.
Convercus Loyalty18

Get the Account Balance

ActionIn the docs only

Gives you an account's current balance, ready to drop into an email, a dashboard or a condition in your scenario.

When to use it
a reminder message should quote what the customer has saved up so far.
Watch out
a separate module returns the balance in a currency; stay with this one when the raw figure is enough for your use.
Convercus Loyalty19

Get the Account Balance in Currency

ActionIn the docs only

Expresses an account's balance in a currency, as the name says, which reads more naturally in a message sent to a customer.

When to use it
a receipt or a newsletter should show the balance as money rather than as a bare count.
Watch out
the doc does not say which currencies are handled, so check the options Make proposes once the connection works.
Convercus Loyalty20

Get the Account Identifiers

ActionIn the docs only

Lists the identifiers attached to an account, so you see every reference under which a customer is known.

When to use it
before Create an Identifier, to avoid adding a reference that the account already has.
Watch out
the result may hold more than one identifier; read the output after Run once to see how Make hands them over.
Convercus Loyalty21

Instant Webhook

ActionIn the docs only

Gives you a Convercus Loyalty module named Instant Webhook, which Make files with the actions of the app rather than with its triggers.

When to use it
you want to explore it on a test scenario once the connection exists, to see what it asks for.
Watch out
the doc has no description for it, so before building a scenario that should start on a Convercus event, confirm in the editor that this module can play that role.
Convercus Loyalty22

Make an API call

ActionIn the docs only

Opens any endpoint of the Convercus Loyalty API to your scenario, reusing the connection you already created.

When to use it
none of the other 26 modules covers the request you need, and you still want to stay inside Make.
Watch out
you build the request yourself here, so test it with Run once and read the response before mapping its output.
Convercus Loyalty23

Redeem coupon

ActionIn the docs only

Redeems a coupon from a scenario, closing the loop that Assign a Coupon opened earlier for that customer.

When to use it
your checkout shows that a customer used their reward and Convercus should record it without a manual step.
Watch out
test on a dummy coupon; a redemption fired during a test run still affects a real customer.
Convercus Loyalty25

Update Account Rating Level

ActionIn the docs only

Moves an account to another rating level without anyone touching the Convercus back office.

When to use it
your own rule, computed from shop data in an earlier module, says a customer should go up or down a level.
Watch out
check the valid levels with Get Program Rating Levels first, so the scenario never tries to set a level the program does not know.
Convercus Loyalty26

Update a Coupon

ActionIn the docs only

Changes an existing coupon, so a correction reaches Convercus from the tool where the decision was actually made.

When to use it
marketing edits a campaign row in a spreadsheet and the matching coupons should follow.
Watch out
the doc does not list which coupon details can change; open the module after connecting and read what it proposes.
Convercus Loyalty27

Update a User

ActionIn the docs only

Keeps a Convercus Loyalty user in step with the rest of your tools by writing the changes you mapped.

When to use it
a customer edits their profile in your CRM or your online store, and the loyalty record should match.
Watch out
map only the values that really changed, and run it once on a test user before switching the scenario on.
Need help

Need help automating Convercus Loyalty with Make?

A person reads every message.

FAQ

Convercus Loyalty and Make: common questions

01Is the Convercus Loyalty Make integration free?
Yes, Convercus Loyalty is a standard app in Make, so you can use it on the Free plan. That plan has limits: 2 active scenarios, 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. Every module run on one bundle counts as an operation, and paid plans (Core, Pro, Teams, Enterprise) count those operations as monthly credits. Paid plans also allow a 1 minute interval and unlimited active scenarios.
02What do you need to connect Convercus Loyalty to Make?
A Convercus Loyalty account and a Make account. The doc lists no other prerequisite and gives no app-specific steps, so the generic path applies: add any Convercus Loyalty module, click Create a connection, name it if you like, then either authorize Make on the Convercus page or paste the key your account provides, and click Save. The connection is then reused by all 27 modules. If the window asks for something you do not have, the Convercus side of your account is the place to look.
03Does Convercus Loyalty trigger Make scenarios in real time?
No, not through a trigger: Make lists no trigger for Convercus Loyalty, only 26 actions and 1 search. You still have two ways to start. Open the scenario on another app, such as your form tool or shop, and let its event drive the run. Or set a schedule on the first module: every 15 minutes by default, down to 1 minute on paid plans. A module called Instant Webhook exists, but Make classes it as an action, so check in the editor what it does before counting on it.
04What if a Convercus Loyalty module is missing in Make?
Use Make an API call. It reaches any endpoint of the Convercus Loyalty API with the connection you already set up, so you can cover what the listed modules do not. You write the request yourself, which means testing with Run once and reading the response before mapping it. Keep in mind that Make says its documentation for this app is limited, so field names are something you confirm in the editor rather than in a guide. If a request still does not fit, the data can pass through another app first.
05Should you use Make or n8n for Convercus Loyalty?
It depends on your criteria. On the Make side, the facts are clear: 27 modules, no trigger, a generic API call module for the rest, and the app works from the Free plan. n8n often has a node for the same app, but whether one exists for Convercus Loyalty is worth checking in n8n itself before deciding. Compare what each tool actually offers for your program, the way you want to start scenarios, and where your team is already comfortable. There is no ranking to give here.
Same platform

Other docs you might need on this stack.

Browse all integrations