Resources · Make integration

Clientary Make integrationAutomate Clientary with Make.

Can Make take the busywork out of Clientary? The Clientary Make integration gives you 41 modules: 9 triggers, 25 actions and 7 searches. This guide is for freelancers and small agencies, and it walks you from connecting your account to a first working scenario.

Try the Clientary integration on MakeSee the 41 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Clientary Make integration do for you?

The Clientary Make integration links your Clientary account to Make, a visual tool where you build a scenario (the automation itself) out of modules (one brick each: a trigger, an action or a search). Make watches Clientary for new clients, invoices, payments or tasks, then creates, updates or looks up records for you, without a line of code.

Onboard clients without a checklist in your head. Watch New Clients spots each client you add, and Create a Task drops the first to-do into Clientary, so nobody forgets the welcome call.

Keep your books in sync. Watch New Payments picks up each payment you record, and a module from your accounting or messaging app can carry it where your team looks. Going the other way, Create an Expense logs a cost that arrives from another tool.

Turn a signed deal into paperwork. When a deal closes in your CRM, Create an Estimate or Create an Invoice drafts the document in Clientary with the amounts mapped from that deal.

A few limits worth knowing. The official Make documentation for Clientary lists the modules without describing them, and it warns that its own text is AI-generated and may contain mistakes, so check anything important with Clientary. No instant trigger is listed either: every Watch module runs on the scenario's schedule. For deeper questions, the Make review covers the tool itself, and Make pricing explains how operations are counted. Clientary may also have a node in n8n; the n8n vs Make comparison lays out the criteria side by side.

Connect

How do you connect Clientary to Make?

  1. 01

    Generate your API token in Clientary

    Log in to Clientary, open your user profile from the upper right corner and click Generate API Token. Copy the token shown on screen. You need an active Clientary account for this button to appear.

  2. 02

    Add a Clientary module in Make

    In your scenario, search for Clientary, pick any module and click Create a connection. A connection is your Clientary account linked to Make once, then reused by every Clientary module you add later.

  3. 03

    Paste the token and save

    Give it a clear label in Connection name if you run several accounts, which is optional. Then paste the API token you copied and confirm. Make can now read and write your Clientary data.

First scenario

Your first scenario: a to-do for every new Clientary client

GoalWhen a new client appears in Clientary, Make creates an onboarding task for it in Clientary.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the big + to place the first module on the canvas.

  2. 02

    Pick the trigger

    Search for Clientary, choose Watch New Clients and select the connection you just made, or click Create a connection if you skipped that part.

  3. 03

    Add the task module

    Click the + on the right of the trigger and add Create a Task. Map the client's name from the trigger into the task so each to-do says who it is for.

  4. 04

    Test with Run once

    Add a test client in Clientary, then click Run once. Open the bubble above each module to read the bundles it received: one bundle is one item, here one client.

  5. 05

    Schedule and switch it on

    Open the clock on the first module. A new scenario checks every 15 minutes by default; keep that or pick another interval your plan allows, then switch the scenario on.

Triggers

Clientary triggers: what can start a scenario

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

Clientary1Watch New Clients

Watch New Clients

triggerIn the docs only

Every client you add to Clientary becomes the starting point of a scenario, so welcome steps stop depending on memory. Each new client arrives as one bundle you can map into the next modules.

How it fires
scheduled. Make checks Clientary on the scenario's schedule and collects the clients added since the previous check.
When to use it
as the opening of an onboarding flow, for example a first task, a folder in your file storage or a note to the account manager.
Watch out
each client that comes through counts as operations for every module it touches, so keep the flow short on a small plan.
Clientary2Watch New Contacts

Watch New Contacts

triggerIn the docs only

People rather than companies: this trigger hands your scenario each new contact person saved in Clientary. It keeps a mailing list or a CRM aligned with the names your team actually works with.

How it fires
scheduled. Make looks at Clientary at the interval set on the scenario, not the moment the contact is saved.
When to use it
when a new contact should land in your newsletter tool or a shared address book without anyone copying it by hand.
Watch out
if the next step needs company details as well, add Get a Client or Search Clients after the trigger rather than guessing them.
Clientary3Watch New Estimates

Watch New Estimates

triggerIn the docs only

Your quotes become a signal: each estimate drafted in Clientary reaches the scenario as a bundle, ready to notify someone or to log in a pipeline sheet.

How it fires
scheduled. Make queries Clientary on the scenario's timetable and returns the estimates created since its last pass.
When to use it
when sales wants to see every new quote in a team channel, or a manager has to review it before it goes out.
Watch out
it reacts to new estimates only. An edit to an existing one will not start the scenario, so track later changes another way, such as List Estimates.
Clientary4Watch New Expenses

Watch New Expenses

triggerIn the docs only

Costs logged in Clientary no longer stay there alone. This trigger passes every new expense to your scenario so it can reach your accounting or your budget sheet.

How it fires
scheduled. Make polls Clientary on the scenario's schedule, which means an expense shows up at the next check rather than instantly.
When to use it
when project costs recorded by the team should also appear in the spreadsheet your finance person reads.
Watch out
if you also create expenses from Make with Create an Expense, avoid sending them back to the same place, or you will build a loop.
Clientary5Watch New Invoices

Watch New Invoices

triggerIn the docs only

Billing stops living only in Clientary: each invoice created in Clientary lands in your scenario as its own bundle, ready to copy, announce or archive.

How it fires
scheduled. Make checks Clientary for fresh invoices on the scenario's schedule, every 15 minutes unless you change it.
When to use it
to push each invoice to your accounting tool, to post it in the finance channel or to add a row to a revenue tracker.
Watch out
a new invoice is not a paid one. For money actually received, start from Watch New Payments instead.
Clientary6Watch New Payments

Watch New Payments

triggerIn the docs only

Cash in, signal out. Whenever a payment is recorded in Clientary, this trigger gives your scenario the payment as a bundle, so thank-you notes and bookkeeping follow on their own.

How it fires
scheduled. Make asks Clientary on the scenario's schedule for payments recorded since the previous run.
When to use it
to send a receipt message, to mark a deal as won in your CRM or to tell the project lead that work can start.
Watch out
on the Free plan the shortest gap between two checks is 15 minutes, so a client may pay a little before your message leaves.
Clientary7Watch New Projects

Watch New Projects

triggerIn the docs only

New work, set up everywhere at once. The trigger hands over each project opened in Clientary so the scenario can prepare the space your team needs around it.

How it fires
scheduled. Make reads Clientary at the scenario's interval and brings back the projects created since the last read.
When to use it
to create a board in your project tool, a shared folder or a kickoff message for each new project.
Watch out
Clientary offers no Create a Project module in Make, so this flow works one way: projects start in Clientary, then spread out.
Clientary8Watch New Staff

Watch New Staff

triggerIn the docs only

A teammate added in Clientary can get the rest of their setup without a ticket. This trigger passes each new staff member to the scenario as a bundle.

How it fires
scheduled. Make polls Clientary on the scenario's schedule and returns the staff members added since its previous check.
When to use it
when onboarding a colleague means an invitation in your chat tool, a welcome email and an entry in the team directory.
Watch out
Make lists no module to create or edit staff, so account changes for a person stay manual inside Clientary.
Clientary9Watch New Tasks

Watch New Tasks

triggerIn the docs only

Tasks created in Clientary can follow people into the tools where they actually plan their day. Each new task becomes a bundle your scenario can forward.

How it fires
scheduled. Make looks for new tasks at the scenario's interval rather than being alerted by Clientary.
When to use it
to copy a task to a calendar, to ping the person in charge or to mirror it in another to-do app.
Watch out
if the same scenario also runs Create a Task in Clientary, each copy is a new task for this trigger and the flow can loop. Keep the two apart.
Modules

Clientary modules: what Make can do in your account

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

Clientary1

Create a Client

ActionIn the docs only

Adds a new client record to Clientary from data that lives elsewhere, so a signed form or a CRM deal becomes a real account without retyping.

When to use it
after a lead form is submitted or a deal is marked won in your CRM.
Watch out
run Search Clients first, or the same company can end up in Clientary twice.
Clientary2

Create a Contact

ActionIn the docs only

Saves a person in Clientary, the one you will email and call, with the details mapped from an earlier module in your scenario.

When to use it
when a new name arrives from a form, a meeting booking tool or a signature request and should sit next to the client record in Clientary.
Watch out
run Search Clients before it, so you know which client the new person relates to.
Clientary3

Create a Task

ActionIn the docs only

Puts a to-do inside Clientary so the follow-up lives next to the client and the billing, not in a separate app.

When to use it
after a new client, a new payment or a form answer that someone on the team must act on.
Watch out
do not pair it with Watch New Tasks in the same flow, or each task created will start the scenario again.
Clientary4

Create an Estimate

ActionIn the docs only

Drafts a quote in Clientary from amounts and items you map in, which spares you from rebuilding the same document by hand for each request.

When to use it
when a request form or a CRM stage already holds what the client asked for.
Watch out
check the first few drafts carefully with Run once before letting the scenario send anything to a client.
Clientary5

Create an Expense

ActionIn the docs only

Logs a cost in Clientary from a receipt or a purchase recorded in another tool, so project costs stay complete without double entry.

When to use it
when a card transaction, an emailed receipt or a row in a spending sheet should count against a client or project.
Watch out
keep it out of any scenario that starts with Watch New Expenses, to avoid an endless circle.
Clientary6

Create an Invoice

ActionIn the docs only

Produces an invoice in Clientary from data mapped in the scenario, which turns a finished job or a closed deal into a bill with no copy and paste.

When to use it
when a project is marked done in your project tool or a subscription renews in your sales app.
Watch out
test with a dummy client first; an invoice with wrong amounts is harder to explain than a late one.
Clientary7

Delete a Client

ActionIn the docs only

Removes a client from Clientary as part of a cleanup flow, for example when an account is closed in your main system and should disappear here too.

When to use it
only for records you are sure are obsolete, such as test clients created while building scenarios.
Watch out
treat the deletion as final and add a filter in front of the module so only the right record reaches it.
Clientary8

Delete a Contact

ActionIn the docs only

Takes a person off a client's contact list in Clientary, which keeps reminders and emails from reaching someone who has left the company.

When to use it
when an unsubscribe or a departure is recorded in your CRM or your mailing tool.
Watch out
pick the contact with Get a Contact or a search first, and run it once on a test record before switching the scenario on.
Clientary9

Delete a Task

ActionIn the docs only

Clears a task from Clientary once it no longer makes sense, so the list your team reads stays short and honest.

When to use it
when the same to-do was cancelled in another tool and should vanish here as well, or to clean up tasks from your tests.
Watch out
once the scenario is switched on it acts alone, so filter carefully on what reaches this module.
Clientary10

Delete an Estimate

ActionIn the docs only

Removes a quote from Clientary, useful when an estimate was created by mistake by a scenario or is replaced by a new version.

When to use it
during testing, to wipe the drafts your Run once sessions left behind, or when a deal is dropped in your CRM.
Watch out
treat the deletion as final; archive what you need to keep before this step.
Clientary11

Delete an Expense

ActionIn the docs only

Erases a cost line in Clientary, which fixes duplicates or entries a scenario created wrongly before you tuned it.

When to use it
when a refund or a cancelled purchase in your finance tool means the expense should no longer count.
Watch out
treat the deletion as final, so check with whoever tracks expenses before automating removals.
Clientary12

Delete an Invoice

ActionIn the docs only

Removes an invoice from Clientary. It exists mainly to undo invoices a test scenario produced, or drafts that should never have been created.

When to use it
while building and testing, right after a Run once that created junk records.
Watch out
billing records often matter for your accounts; think twice before letting a live scenario delete them.
Clientary13

Get a Client

ActionIn the docs only

Fetches the full record of one client you already point to, which gives later modules the company details a trigger bundle may not carry.

When to use it
after Watch New Invoices or Watch New Contacts, when the next step needs the client's own information.
Watch out
it returns one client only; to find a client by name, use Search Clients instead.
Clientary14

Get a Contact

ActionIn the docs only

Reads a single contact from Clientary so your scenario can use that person's details in an email, a message or another app.

When to use it
when an earlier module already tells you which contact is involved and you need the rest of the record.
Watch out
you must map which contact to read; if you only have a list to browse, List Contacts fits better.
Clientary15

Get a Task

ActionIn the docs only

Pulls one task from Clientary with its current state, which helps a scenario decide what to do next before it touches anything.

When to use it
ahead of Update a Task, to check the task still needs the change you are about to make.
Watch out
it reads a known task and does not search; to go through several tasks, use List Tasks.
Clientary16

Get an Estimate

ActionIn the docs only

Retrieves one estimate so its content can travel on, to a PDF tool, a CRM note or an approval message for a manager.

When to use it
after Watch New Estimates when you want the latest version of the quote rather than what the trigger saw.
Watch out
each call is one operation; skip it when the trigger bundle already holds what you need.
Clientary17

Get an Expense

ActionIn the docs only

Loads one expense from Clientary, handy when a scenario must look at a cost again before copying it into your books.

When to use it
when a message or a spreadsheet row tells you which expense to review, and you want the record as it stands now.
Watch out
to find expenses by criteria rather than by a known record, Search Expenses is the right tool.
Clientary18

Get an Invoice

ActionIn the docs only

Brings back a single invoice with its current details, which lets you confirm what a client owes before sending a reminder or a thank-you.

When to use it
after Watch New Payments, to read the invoice that payment relates to.
Watch out
it needs to know which invoice to read, mapped from an earlier module; it will not guess it for you.
Clientary19

List Contacts

SearchIn the docs only

Returns the contacts stored in Clientary as a series of bundles, one per person, so you can copy them elsewhere or check them in bulk.

When to use it
for a first sync of your address book into a CRM or a mailing tool.
Watch out
every contact is a bundle and each module after it runs once per bundle, which multiplies operations quickly.
Clientary20

List Estimates

SearchIn the docs only

Pulls your estimates out of Clientary in one go, which gives you material for a pipeline report or a check on quotes still waiting for an answer.

When to use it
when a scenario needs an overview of quotes rather than one fresh estimate at a time.
Watch out
the result can be empty, one item or many; build the next modules so they cope with all three.
Clientary21

List Projects

SearchIn the docs only

Hands your scenario the projects saved in Clientary, one bundle each, so you can mirror them in a project tool or a status sheet.

When to use it
to build a first copy of your projects elsewhere, before Watch New Projects takes over for the new ones.
Watch out
a long list costs operations on every following module, so filter as early as you can.
Clientary22

List Tasks

SearchIn the docs only

Gathers the tasks in Clientary so a scenario can review what is open, send a digest or copy the work into another planner.

When to use it
when someone asks for an overview of pending to-dos in a team channel.
Watch out
it may return no task at all; add a filter so an empty result does not send an empty message.
Clientary23

Make an API Call

ActionIn the docs only

Opens the rest of the Clientary API to your scenario, with the same connection, when none of the listed modules does what you need.

When to use it
for a Clientary feature that has no module of its own, one you found in Clientary's API documentation.
Watch out
you write the request yourself, so keep Clientary's API documentation open while you set it up.
Clientary24

Search Clients

SearchIn the docs only

Looks through your Clientary clients and returns the matches, which is how a scenario finds out whether a company already exists before doing anything.

When to use it
right before Create a Client, to update the existing record instead of adding a duplicate.
Watch out
a search can return zero, one or several clients; plan a route for each case with a filter.
Clientary25

Search Expenses

SearchIn the docs only

Finds the expenses that match what you ask for, which helps with checks such as spotting a cost that was already logged.

When to use it
before Create an Expense, when receipts can reach the scenario twice from your email or card tool.
Watch out
several matches mean several bundles, and every module after the search runs for each of them.
Clientary26

Search Invoices

SearchIn the docs only

Returns the invoices matching your criteria, a practical way to find the bill behind a payment or a client question.

When to use it
when a message from a client or a bank line has to be matched with an invoice in Clientary.
Watch out
no match is a normal result; decide in advance what the scenario should do when nothing comes back.
Clientary27

Update a Client

ActionIn the docs only

Changes the details of an existing client in Clientary, so a new address or a new name entered in your CRM shows up on the next invoice.

When to use it
when your CRM or a customer form is the place where client data gets corrected first.
Watch out
map only what actually changed, and test the result on a sample client with Run once.
Clientary28

Update a Contact

ActionIn the docs only

Edits a person already stored in Clientary, keeping phone numbers and emails right without anyone opening the app.

When to use it
when a contact updates their details through a form or your mailing tool, and Clientary should follow.
Watch out
find the right person first with Get a Contact or List Contacts, then map that contact into this module.
Clientary29

Update a Task

ActionIn the docs only

Modifies a Clientary task from outside, for instance to reflect progress made in another planner your team prefers.

When to use it
when a card moves to done in your project board and the matching task in Clientary should say so too.
Watch out
two tools editing the same task in both directions can overwrite each other; choose one source.
Clientary30

Update an Estimate

ActionIn the docs only

Adjusts a quote already saved in Clientary, which keeps it in line with a deal whose scope moved in your CRM.

When to use it
when the amount or the items of a deal change after the first estimate was drafted.
Watch out
if the client already has the estimate, tell them it changed; the module will not do that for you.
Clientary31

Update an Expense

ActionIn the docs only

Corrects an expense in Clientary from data held elsewhere, so it matches what your finance tool says.

When to use it
when a receipt is revised or a purchase amount is fixed after the first entry.
Watch out
use Get an Expense or Search Expenses before it, so the scenario edits the right line.
Clientary32

Update an Invoice

ActionIn the docs only

Edits an invoice that already exists in Clientary, keeping it aligned with an order or a contract that changed after billing started.

When to use it
when a sales app changes an order and the related invoice has not been paid yet.
Watch out
an invoice the client has already received deserves a note to them; test the change with Run once first.
Need help

Need help automating Clientary with Make?

A person reads every message.

FAQ

Clientary and Make: common questions

01Is the Clientary Make integration free?
Yes. Clientary is a standard app in Make, available on the Free plan. That plan allows 2 active scenarios, at least 15 minutes between two scheduled runs, up to 5 minutes per execution, 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 allow 40 minutes per run. Usage is counted in operations, one per module per bundle. You still need your own Clientary subscription.
02What does Clientary need to connect to Make?
An active Clientary account and a personal API token. Log in to Clientary, open your user profile from the upper right corner, click Generate API Token and copy the token. In Make, add any Clientary module, click Create a connection, optionally name it, then paste the token. The connection is saved once and reused by all 41 Clientary modules, so you only go through this step again if you generate a new token.
03Do the Clientary triggers in Make fire instantly?
No. The nine Clientary triggers are scheduled: Make checks Clientary on the scenario's schedule and collects what is new since the last check. A new scenario checks every 15 minutes by default. On the Free plan 15 minutes is also the shortest interval, while paid plans go down to 1 minute. No instant trigger, the kind an app calls through a webhook, is listed for Clientary, so plan your flows for a short delay.
04What if a Clientary module is missing in Make?
Use Make an API Call. It is part of the Clientary app in Make and lets a scenario reach any endpoint of the Clientary API with your existing connection, which covers what the 41 listed modules leave out. You write the request yourself, so keep Clientary's API documentation at hand. Keep in mind that the Make documentation for Clientary is marked as AI-generated and may contain mistakes; check important details with Clientary.
05Should you use Make or n8n for Clientary?
It depends on the tool your team already runs. Make gives Clientary 41 ready modules, 9 scheduled triggers and Make an API Call for the rest, all built in a visual editor where every module appears as a bubble on the canvas. The same app often has a node in n8n too, so check its node list before you choose. Compare on the modules you actually need and on how your team likes to build, rather than on the name of the tool.
Same platform

Other docs you might need on this stack.

Browse all integrations