Resources · Make integration

Clientjoy Make integrationAutomate Clientjoy with Make.

Can Make keep your Clientjoy leads, customers and invoices moving without copy and paste? The Clientjoy Make integration gives you 19 modules: 9 triggers, 8 actions and 2 searches. This page shows how to link your account, build a first scenario and pick the right module.

Try the Clientjoy integration on MakeSee the 19 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Clientjoy Make integration do for you?

The Clientjoy Make integration links your Clientjoy account to Make so that leads, customers, proposals and invoices can start or feed a scenario, the automation you build in Make as a chain of modules. A module is one brick of that chain: a trigger that watches, an action that writes, or a search that looks something up.

Leads that arrive on their own. A contact form or a chat tool sits upstream, and Create a Lead drops each new prospect into Clientjoy. Your sales pipeline fills up while nobody retypes a name or an email address.

A clean handover once a deal closes. Watch Lead Status notices when a lead moves forward, and Create Customer from Lead turns that record into a customer, so the account team starts from the same data sales worked with.

Billing that follows the work. Watch Invoice Sent and Watch Invoice Paid each start a scenario at a different moment of the invoice life, which lets you tell your accounting tool or your team channel exactly what changed.

Know the limits before you build. Make's own doc for Clientjoy is short: it lists the module names but gives no field details, no connection steps specific to the app and no troubleshooting notes. When a listed module does not cover your case, Make an API Call reaches the rest of the Clientjoy API with the same connection. Our Make troubleshooting guide helps once a run fails, and Make pricing explains how operations are counted.

Weighing tools first? The n8n vs Make comparison puts the two side by side, without taking this page's word for it.

Connect

How do you connect Clientjoy to Make?

  1. 01

    Add a Clientjoy module

    In your scenario, click the + and search for Clientjoy. Pick any of its modules, then click Create a connection. A connection is your Clientjoy account linked to Make once, and every Clientjoy module reuses it afterwards.

  2. 02

    Name the connection

    This step is optional, yet a clear name such as the workspace or the client it belongs to saves confusion later, especially if a colleague adds a second Clientjoy account to the same Make team.

  3. 03

    Authorize and save

    Depending on what Clientjoy asks, either approve Make on the Clientjoy page that opens or paste the key Clientjoy gives you. Then click Save. The module now lists what it can read from your account.

First scenario

Build your first scenario with Clientjoy

GoalWhen a prospect fills in the form on your website, Make creates the matching lead in Clientjoy.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the big + to choose the first module. Here it comes from your form tool, since that is where new prospects show up.

  2. 02

    Set the form trigger

    Search for your form app, pick the module that watches new responses and connect your account. Make then lists the forms it can read; choose the one on your contact page.

  3. 03

    Add Create a Lead

    Click the + on the right of the form module, search for Clientjoy and pick Create a Lead. Link your account with Create a connection if you have not done it yet.

  4. 04

    Map the answers

    Fill the lead fields Make shows by clicking into each one and picking the matching answer from the form module. Each response travels as a bundle, one item passed from a module to the next.

  5. 05

    Test with Run once

    Submit a test entry on your form, then click Run once. Make runs the scenario one time; open the bubble above each module to read the bundle it received and check the new lead in Clientjoy.

  6. 06

    Schedule and switch on

    Click the clock on the first module to set the schedule, every 15 minutes by default, then switch the scenario on. From now on, each module run counts as one operation on your Make plan.

Triggers

Which Clientjoy triggers can start a scenario?

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

Clientjoy1Watch Customers

Watch Customers

triggerIn the docs only

Start a scenario from each customer that appears in your Clientjoy account, so onboarding tasks, welcome emails or a folder in your file storage follow without anyone opening the CRM.

How it fires
scheduled. Make checks the app on the scenario's schedule, the clock badge on the module, rather than hearing from Clientjoy the moment a customer is added.
When to use it
your team creates customers by hand in Clientjoy and you want the rest of your tools to learn about each one.
Watch out
it reacts to new customers only; changes to an existing record belong to Watch Updated Customers.
Clientjoy2Watch Invoice Paid

Watch Invoice Paid

triggerIn the docs only

Get a scenario going each time Make finds a Clientjoy invoice marked as paid, which is the right signal to close a follow-up task, thank the client or tell your bookkeeper that money came in.

How it fires
scheduled. On each scheduled run, Make asks Clientjoy which invoices were paid since its last check.
When to use it
payment matters more to you than sending, for example when work only starts after the deposit clears.
Watch out
the delay between the payment and your scenario depends on the schedule you set, 15 minutes at the shortest on the Free plan.
Clientjoy3Watch Invoice Sent

Watch Invoice Sent

triggerIn the docs only

Follow every invoice as it leaves Clientjoy, and let Make log it in a sheet, post a note to your team or add a reminder in your task tool so nobody forgets to chase it.

How it fires
scheduled. Make polls Clientjoy on the scenario's clock and picks up the invoices that went out in the meantime.
When to use it
you want a trace of what was billed, before anyone knows whether it will be paid.
Watch out
a sent invoice is not a paid one. If your next step depends on the money, pair this scenario with Watch Invoice Paid rather than guessing.
Clientjoy4Watch Invoices

Watch Invoices

triggerIn the docs only

Catch invoices as a whole in Clientjoy, without waiting for a particular stage, so a scenario can copy each one into your accounting tool or a shared spreadsheet as soon as Make finds it.

How it fires
scheduled. Make looks at Clientjoy each time the schedule comes round and passes along what is new.
When to use it
you need one list of every invoice, whatever its stage, rather than a reaction to sending or payment.
Watch out
the doc gives no description of this module, so run it once and read the bundles to see exactly which invoices it returns.
Clientjoy5Watch Lead Status

Watch Lead Status

triggerIn the docs only

React when a lead moves through your pipeline in Clientjoy, so a status change can hand the record to the right person or kick off the paperwork that comes with that stage.

How it fires
scheduled. At every run on the scenario's schedule, Make asks Clientjoy for leads whose status changed.
When to use it
your pipeline stages mean something outside the CRM, like a proposal to draft or a contract to prepare once a lead qualifies.
Watch out
without a description in the doc, test it with Run once after moving a lead yourself, and check what the bundle tells you before building on it.
Clientjoy6Watch Leads

Watch Leads

triggerIn the docs only

Hear about each lead that lands in Clientjoy and put it to work elsewhere: a message in your sales channel, a row in a tracking sheet, or a draft proposal prepared through Create a Proposal.

How it fires
scheduled. Make checks Clientjoy for fresh leads on the scenario's schedule instead of receiving a push from the app.
When to use it
leads enter Clientjoy from several places and you want one scenario that reacts to all of them.
Watch out
if the same scenario also creates leads with Create a Lead, it will pick its own records up on the next run.
Clientjoy7Watch Proposals

Watch Proposals

triggerIn the docs only

Keep the rest of your stack informed about proposals written in Clientjoy, for instance by filing each one in your project tool or alerting the person who will deliver the work if it is accepted.

How it fires
scheduled. Make queries Clientjoy each time the scenario's schedule runs and collects the proposals it had not seen.
When to use it
proposals are the point where sales and delivery meet, and you want delivery to see them early.
Watch out
the doc does not say whether this module follows new proposals only or changes too, so run a test before you rely on it.
Clientjoy8Watch Updated Customers

Watch Updated Customers

triggerIn the docs only

Pick up edits to customer records in Clientjoy and copy them wherever the same customer lives, so a new phone number or company name does not stay trapped in one tool.

How it fires
scheduled. Make checks the app on the scenario's schedule and brings back customers changed since the previous run.
When to use it
your billing or support tool keeps its own copy of each customer and drifts out of date.
Watch out
never end this scenario with Update a Customer on the same record. Your own update would count as a change and start the scenario again, in a loop that burns operations.
Clientjoy9Watch Updated Leads

Watch Updated Leads

triggerIn the docs only

Notice any edit to a lead in Clientjoy, not only status moves, and push the new details to the tools that follow your prospects, like an email list or a shared tracking sheet.

How it fires
scheduled. On the schedule you give the scenario, Make asks Clientjoy which leads were edited.
When to use it
the change you care about is in the contact details or notes rather than the pipeline stage, where Watch Lead Status is the sharper choice.
Watch out
pairing it with Update a Lead on the same record creates a loop, since each update looks like a new edit to Make.
Modules

What can Clientjoy do inside a scenario?

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

Clientjoy1

Create Customer from Lead

ActionIn the docs only

Turns a lead you already have into a customer in one step, so nobody has to retype the same person into a fresh customer record.

When to use it
right after Watch Lead Status reports that a lead has signed, to start onboarding from the converted record.
Watch out
it needs the lead to exist; if you only hold the person's details, place Find a Lead before it.
Clientjoy2

Create a Customer

ActionIn the docs only

Adds a brand new customer to Clientjoy from data coming out of another app, such as a signed contract in your e-signature tool or an order in your shop.

When to use it
the person never went through your lead pipeline, so there is nothing to convert.
Watch out
nothing in the doc says this module checks for duplicates, so run Find a Customer first when the same client might come back.
Clientjoy3

Create a Lead

ActionIn the docs only

Places a new prospect in your Clientjoy pipeline from whatever captured it first: a website form, a booking tool, a chat conversation or a list of event contacts.

When to use it
leads start outside Clientjoy and someone currently copies them in by hand.
Watch out
a visitor who fills your form twice becomes two leads unless Find a Lead looks for the existing one first.
Clientjoy4

Create a Proposal

ActionIn the docs only

Drafts a proposal in Clientjoy from details gathered elsewhere, which gives your salesperson a starting document rather than a blank page when a deal gets serious.

When to use it
a qualified lead, flagged through Watch Lead Status or a form answer, should get a proposal without delay.
Watch out
review the draft in Clientjoy before it reaches the client; the doc does not say whether this module sends it.
Clientjoy5

Create an Invoice

ActionIn the docs only

Produces an invoice in Clientjoy from an event in another tool, for example a project marked as delivered or a milestone ticked off, so billing no longer waits on memory.

When to use it
work is tracked outside Clientjoy but invoices still go out from it.
Watch out
test with Run once on a dummy customer first, because a real invoice created by mistake will need cleaning up by hand.
Clientjoy6

Find a Customer

SearchIn the docs only

Looks up customers in Clientjoy and returns what it finds, which lets the rest of your scenario work on the right record instead of creating a second one.

When to use it
before Create a Customer or Update a Customer, to check whether the client is already there.
Watch out
a search can return zero, one or several bundles, and each bundle runs the next modules once, so narrow your search.
Clientjoy7

Find a Lead

SearchIn the docs only

Searches your Clientjoy leads so a scenario can reuse an existing prospect, for instance to update it or convert it, rather than adding a duplicate to the pipeline.

When to use it
data from another tool points to a prospect and you need the matching lead before acting.
Watch out
when nothing matches, the modules after it receive no bundle and simply do not run; plan for that case.
Clientjoy8

Make an API Call

ActionIn the docs only

Opens the rest of the Clientjoy API to your scenario, using the connection you already set up, for anything the listed modules leave out.

When to use it
you need an object or an operation that no Clientjoy module offers, such as a record type none of the 19 modules touch.
Watch out
you write the request yourself from Clientjoy's API documentation, so this is the one module where some technical reading is required.
Clientjoy9

Update a Customer

ActionIn the docs only

Changes an existing customer in Clientjoy with fresh details from another tool, which keeps the CRM in step when a client edits their profile in your billing or support app.

When to use it
the change happens outside Clientjoy and the CRM should reflect it.
Watch out
you need the customer first, usually from Find a Customer; do not feed it from Watch Updated Customers on the same record.
Clientjoy10

Update a Lead

ActionIn the docs only

Edits a lead already in Clientjoy, so answers from a follow-up form, a booked call or an email reply end up on the prospect's record without manual entry.

When to use it
a lead gives you more information after the first contact and your sales team should see it.
Watch out
fetch the lead with Find a Lead first, and keep this module away from scenarios started by Watch Updated Leads.
Need help

Need help automating Clientjoy with Make?

A person reads every message.

FAQ

Questions about the Clientjoy Make integration

01Is the Clientjoy Make integration free?
Yes, Clientjoy is a standard app in Make, available from the Free plan. That plan allows 2 active scenarios, a scheduled run every 15 minutes at the shortest, 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, remove the cap on active scenarios and count usage in credits each month. Clientjoy's own subscription is a separate matter this page does not cover.
02What do you need to connect Clientjoy to Make?
A Clientjoy account and a Make account. Make's doc lists no prerequisite for Clientjoy and no app-specific connection steps, so the generic path applies: add a Clientjoy module, click Create a connection, give it a name if you like, then either approve Make on Clientjoy's page or paste the key Clientjoy provides, and click Save. The connection is then shared by every Clientjoy module in your scenarios, so you only do this once per account.
03Do Clientjoy triggers fire instantly in Make?
No, going by what is known. The 9 Clientjoy triggers are watch modules, and none is marked as instant, so Make polls Clientjoy on the scenario's schedule: every 15 minutes by default, and down to 1 minute on paid plans. Note that Make's directory had no Clientjoy listing when this page was written, so these types come from the module names. When you add a trigger, look for the clock badge, which marks a scheduled one.
04What if a Clientjoy module you need is missing in Make?
Use Make an API Call. It sends any request the Clientjoy API accepts, with the connection you already have, so you are not limited to the 19 listed modules. Expect to read Clientjoy's API documentation to build the request. Keep in mind that Make's own doc for Clientjoy is limited: it names the modules but gives no field details or troubleshooting, so a test with Run once is the fastest way to see what each module returns.
05Should you use Make or n8n for Clientjoy?
It depends on what you already run. On Make, Clientjoy comes with 19 modules, including 9 triggers, and works from the Free plan, which is enough to judge whether the automation fits your sales process. Many apps also have an n8n node, but the sources behind this page do not confirm one for Clientjoy, so check that first. The n8n vs Make comparison on this site sets out the criteria without ranking either tool.
Same platform

Other docs you might need on this stack.

Browse all integrations