Resources · Make integration

Klenty Make integrationAutomate Klenty with Make.

What if every reply, bounce and click in Klenty moved your other tools for you? The Klenty Make integration gives you 25 modules, including 9 instant triggers. This guide is for sales teams running outbound, and it walks you from connection to a working first scenario.

Try the Klenty integration on MakeSee the 25 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Klenty Make integration do?

The Klenty Make integration links your Klenty account to Make, a visual tool where you chain apps together without code. Each automation is called a scenario. Klenty can start one the moment a prospect replies, clicks or bounces, and Make can also push prospects and cadence changes back into Klenty.

A clean list after every bounce. Watch Mail Bounce fires when an address fails, and Change Status to DoNotContact takes that prospect out of future outreach. Nobody has to comb through delivery reports by hand.

Warm leads in front of the right rep. Watch Replies and Watch Cadence First Reply tell Make that a conversation has started. From there, Make can alert the account owner in another app, or end the sequence with Stop a Cadence so the prospect stops receiving follow-ups.

New prospects straight into a sequence. When a lead arrives from a form or a CRM, Create a Prospect adds the contact to Klenty and Start a Cadence enrolls it. Search Prospects checks first whether the person is already there.

Klenty has 14 action modules and 2 search modules in Make. When you need an endpoint that none of them covers, Make an API Call reaches the Klenty API with the same connection. The same app often has an n8n node as well; the n8n vs Make comparison helps you pick. To learn the editor properly, see the Make training, and if a scenario breaks, the Make troubleshooting guide lists the usual fixes.

Connect

How do you connect Klenty to Make?

  1. 01

    Copy your Klenty API key

    You need an active Klenty account. Inside Klenty, open Settings, go to the API section and copy the key shown on screen. Keep it at hand: Make asks for it in the next step.

  2. 02

    Add a Klenty module and open the connection

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

  3. 03

    Name it and paste the key

    The Connection name field is optional, but a clear name helps when several people share the workspace. Paste your API key where Make asks for it, or follow the instructions on screen, then save.

First scenario

Your first scenario: clean up bounced prospects

GoalWhen an email bounces in Klenty, Make marks that prospect as DoNotContact.

  1. 01

    Create the scenario

    Open the Scenarios page in Make, create a new scenario and click the big +. That empty circle becomes the first module, the brick that starts everything.

  2. 02

    Add Watch Mail Bounce

    Search for Klenty, pick Watch Mail Bounce, click Create a webhook and then Create a connection with your API key. The lightning badge on the module means Klenty will call Make itself.

  3. 03

    Chain Change Status to DoNotContact

    Click the + on the right of the trigger, pick Klenty again and choose Change Status to DoNotContact. Map the prospect the trigger received so Make knows which contact to update.

  4. 04

    Test with Run once

    Click Run once, then let a test email bounce in Klenty. Each module shows the bundles it got, a bundle being one item passed along, here one bounced prospect.

  5. 05

    Switch it on

    When the test looks right, turn the scenario on. Because the trigger is instant, Make does not wait for a schedule: Klenty calls it through the webhook as soon as a bounce happens.

Triggers

What can start a Klenty scenario?

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

Klenty1Watch Cadence First Reply

Watch Cadence First Reply

Instant trigger

In Make“Triggers when a cadence receives first reply.”

This trigger starts your scenario the first time a prospect answers inside a cadence, Klenty's name for an email sequence. It is the moment a cold contact turns into a conversation, and the one your reps care about most.

How it fires
instant: Klenty calls Make through a webhook as soon as it happens.
When to use it
a rep wants a single alert, or a single CRM update, when a cold prospect finally engages.
Watch out
this module is about the first reply of a cadence; if you need every reply a prospect sends, pick Watch Replies instead.
Klenty2Watch Clicks

Watch Clicks

Instant trigger

In Make“Triggers when a prospect clicks on a tracked link.”

Watch Clicks hands Make a bundle whenever a prospect clicks a tracked link in one of your Klenty emails. It turns interest into something a scenario can act on, such as a note for the account owner.

How it fires
instant: Klenty calls Make through a webhook as soon as it happens.
When to use it
the email points to a pricing or demo page and you want the click logged in your CRM.
Watch out
only tracked links count, so a plain untracked link will never reach Make.
Klenty3Watch Complete Cadence

Watch Complete Cadence

Instant trigger

In Make“Triggers when a cadence is completed.”

You learn the moment a prospect reaches the end of a cadence, and your scenario can decide what happens next instead of leaving that contact idle in Klenty.

How it fires
instant: Klenty calls Make through a webhook as soon as it happens.
When to use it
send finished prospects to a nurture list in another app, or hand them to a teammate for a phone call.
Watch out
a completed cadence is not an unsubscribe; if the prospect opted out along the way, Watch Prospect Unsubscribe is the signal to follow.
Klenty4Watch Mail Bounce

Watch Mail Bounce

Instant trigger

In Make“Triggers when an email is bounced.”

Your scenario gets a bundle each time an email from Klenty bounces. That is the earliest point to protect your sender reputation, because Make can react before the next step of the sequence goes out.

How it fires
instant: Klenty calls Make through a webhook as soon as it happens.
When to use it
pair it with Change Status to DoNotContact, or flag the bad address in the CRM the lead came from.
Watch out
run the scenario once with Run once and read the bundle, so you map the right prospect before any status change.
Klenty5Watch Opens

Watch Opens

Instant trigger

In Make“Triggers when a prospect opens an email.”

Watch Opens reports each time a prospect opens one of your emails. It gives you a light engagement signal to feed scoring or reporting in another tool.

How it fires
instant: Klenty calls Make through a webhook as soon as it happens.
When to use it
you track engagement in a spreadsheet or dashboard and want every open added as a row.
Watch out
every open starts a run, and each module in that run costs an operation, the unit Make counts on your plan. Keep this scenario short.
Klenty6Watch Prospect Unsubscribe

Watch Prospect Unsubscribe

Instant trigger

In Make“Triggers when a prospect is unsubscribed.”

When a prospect is unsubscribed in Klenty, this trigger passes the news to Make so the rest of your stack can respect the choice too.

How it fires
instant: Klenty calls Make through a webhook as soon as it happens.
When to use it
mirror the opt-out in your newsletter tool or CRM, so marketing does not email someone sales just lost.
Watch out
avoid calling Unsubscribe a Prospect in the same scenario on that person; the status is already set and you would only spend an operation.
Klenty7Watch Replies

Watch Replies

Instant trigger

In Make“Triggers when a prospect replies to an email sent from Klenty.”

Every answer a prospect sends to an email that left Klenty lands in your scenario as a bundle. It is the broadest reply signal the app gives Make.

How it fires
instant: Klenty calls Make through a webhook as soon as it happens.
When to use it
post each reply to a shared sales channel, or copy it into the deal record so the whole team sees the thread.
Watch out
for a single alert per cadence rather than one per message, Watch Cadence First Reply is the lighter choice.
Klenty8Watch Send Prospect

Watch Send Prospect

Instant trigger

In Make“Triggers when a prospect is manually sent to a webhook from the interface.”

This one puts a person in charge: the scenario runs when someone in your team manually sends a prospect to the webhook from the Klenty interface. It is a button for on-demand handoffs.

How it fires
instant: Klenty calls Make through a webhook as soon as it happens.
When to use it
a rep decides a lead is ready and pushes it to the CRM or to a partner tool in one gesture.
Watch out
nothing happens on its own here; if nobody sends prospects, the scenario stays silent.
Klenty9Watch Start Cadence

Watch Start Cadence

Instant trigger

In Make“Triggers when a cadence is started.”

Make hears about it whenever a cadence starts for a prospect, which lets you record who entered which sequence without exporting anything from Klenty.

How it fires
instant: Klenty calls Make through a webhook as soon as it happens.
When to use it
update a lifecycle stage in your CRM, or tell the account owner that outreach has begun.
Watch out
keep Start a Cadence out of a scenario that begins here, since a new cadence could start this trigger all over again.
Modules

What can Make do in Klenty?

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

Klenty1

Change Status to DoNotContact

Action

In Make“Changes prospect status to DoNotContact.”

Protect a contact from further outreach: this action switches the prospect's status to DoNotContact in Klenty, so your sequences leave them alone.

When to use it
right after Watch Mail Bounce, or when a prospect asks another channel to stop contacting them.
Watch out
this is different from unsubscribing; if you only want the unsubscribed status, use Unsubscribe a Prospect.
Klenty2

Create a Prospect

Action

In Make“Creates a new prospect.”

Add a brand new contact to Klenty from any other app in your scenario, without retyping a single line in the Klenty interface.

When to use it
a demo form, an event list or a CRM stage produces leads your outbound team should work.
Watch out
run Search Prospects first when the same person might already exist, or you risk duplicates in your lists.
Klenty3

Get an Email Engagement

Action

In Make“Retrieves an email engagements details for the selected cadence.”

Pull the email engagement details of a chosen cadence into Make, so another tool can show how that sequence is performing.

When to use it
when a cadence completes, copy its engagement into the report your sales manager reads.
Watch out
it reads one cadence at a time; for a step by step breakdown, Get a StepWise Metric Engagement is the better fit.
Klenty4

Get a Prospect

Action

In Make“Retrieves a specific prospect.”

Fetch the full record of one specific prospect, so later modules can use its details when the trigger's bundle lacks a detail you need.

When to use it
after Watch Clicks, to enrich the CRM note with the prospect's profile from Klenty.
Watch out
you must already know which prospect you want; to find people by criteria, reach for Search Prospects.
Klenty5

Get a Prospect Status

Action

In Make“Retrieves a specified prospect status.”

Check where a given prospect stands in Klenty before your scenario does anything to them, and branch on the answer.

When to use it
before Start a Cadence, to confirm the contact is not already marked DoNotContact or unsubscribed.
Watch out
reading the status costs an operation too, so place it only where the decision really depends on it.
Klenty6

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Reach any endpoint of the Klenty API from your scenario, reusing the connection you already set up, when none of the ready modules does what you need.

When to use it
an operation you use in Klenty has no dedicated module in Make yet.
Watch out
you write the request yourself, so keep the Klenty API documentation open and test each call with Run once.
Klenty7

Remove Prospect Tags

Action

In Make“Removes tags from prospect.”

Keep your segments accurate by taking tags off a prospect in Klenty as soon as they no longer describe that person.

When to use it
a lead tagged for a campaign replies or converts, and should drop out of that segment.
Watch out
this module only removes tags; to change other prospect details, use Update a Prospect.
Klenty8

Resume a Cadence

Action

In Make“Resumes a paused cadence for a prospect.”

Restart the outreach where it stopped: this action picks up a paused cadence for a prospect, so follow-ups continue without a manual click in Klenty.

When to use it
a deal in your CRM goes back to open after a pause, and the sequence should carry on.
Watch out
it only works on a paused cadence; for a prospect with no cadence running, use Start a Cadence.
Klenty9

Revert from DoNotContact Status

Action

In Make“Reverts prospect from DoNotContact status.”

Bring a prospect back into play by lifting the DoNotContact status that was set on them in Klenty.

When to use it
a contact once blocked after a bounce shares a new, working address through a form.
Watch out
make sure the reason for the block is gone before you revert, otherwise the next sequence hits the same wall.
Klenty10

Start a Cadence

Action

In Make“Starts a cadence for a prospect.”

Enroll a prospect in one of your Klenty cadences directly from Make, so outreach starts the moment the lead is qualified elsewhere.

When to use it
right after Create a Prospect, for leads from a webinar sign-up or a CRM stage change.
Watch out
check the prospect with Get a Prospect Status first, so you never enroll someone marked DoNotContact.
Klenty11

Stop a Cadence

Action

In Make“Stops a cadence for a prospect.”

End the cadence a prospect is in, so no further steps of that sequence reach them once the situation has changed.

When to use it
a meeting gets booked in your calendar tool, and the prospect should stop getting cold follow-ups.
Watch out
if you want to continue later rather than end it, check whether Resume a Cadence fits your flow better.
Klenty12

Stop Mails

Action

In Make“Stops any scheduled emails from being sent to the prospect.”

Cancel every email already scheduled for a prospect in Klenty, so nothing leaves the queue after the situation has changed.

When to use it
a support ticket opens for that contact and sales emails would feel out of place.
Watch out
it targets scheduled emails for the prospect; to end the whole sequence, Stop a Cadence is the clearer choice.
Klenty13

Unsubscribe a Prospect

Action

In Make“Changes a prospect status to Unsubscribed.”

Record an opt-out made outside Klenty: the prospect's status becomes Unsubscribed, and your sequences respect it.

When to use it
someone unsubscribes in your newsletter tool, and sales should honor the same choice.
Watch out
Unsubscribed and DoNotContact are two separate statuses; pick the one your team reports on.
Klenty14

Update a Prospect

Action

In Make“Updates a prospect.”

Keep a Klenty prospect in step with your other tools by rewriting its details from data your scenario already holds.

When to use it
a contact changes job title or company in your CRM, and the next email should reflect it.
Watch out
map only the details that really changed, and test with Run once before switching the scenario on.
Klenty15

Get a StepWise Metric Engagement

Search

In Make“Retrieves a stepwise delailed list of metric engage,ents for the selcted cadence.”

See which step of a cadence performs: this search returns engagement metrics step by step for the cadence you select.

When to use it
you rewrite a sequence and want each step's numbers in a sheet first.
Watch out
a search can hand back several bundles, one per result, and the next modules then run once for each of them.
Klenty16

Search Prospects

Search

In Make“Searches for the prospects. At least one filter field is required.”

Find prospects already in Klenty that match your criteria, and pass each one down the scenario for the next move.

When to use it
before Create a Prospect, to check whether an incoming lead is already in your lists.
Watch out
Make requires at least one filter field, and a search can return zero, one or many bundles.
Need help

Need help automating Klenty with Make?

A person reads every message.

FAQ

Klenty and Make: common questions

01Is the Klenty Make integration free?
Yes, on the Make side. Klenty is a standard app, so it works from the Free plan. That plan allows 2 active scenarios, 15 minutes minimum between scheduled runs, 5 minutes per execution, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lift those limits and count usage in credits, meaning operations, each month. Your Klenty subscription is a separate matter: you need an active Klenty account with an API key, and Klenty sets its own pricing.
02What does it take to connect Klenty to Make?
An active Klenty account and its API key. In Klenty, go to Settings, open the API section and copy the key. In Make, add a Klenty module, click Create a connection, give it a name if you like, and paste the key. For a trigger, Make first asks you to create a webhook, then the connection. One connection serves every Klenty module in your scenarios, so you only do this once per account.
03Do Klenty triggers in Make react in real time?
Yes. All 9 Klenty triggers are instant: Klenty calls Make through a webhook as soon as a reply, a click, an open, a bounce, an unsubscribe or a cadence event happens. The 15 minute minimum of the Free plan applies to scheduled triggers, not to these. The only trigger that waits on a person is Watch Send Prospect, which fires when someone in your team sends a prospect to the webhook from the Klenty interface.
04What if a Klenty module is missing in Make?
Use Make an API Call. It reaches any endpoint of the Klenty API with the connection you already created, so you are not stuck with the 14 actions and 2 searches on offer. You write the request yourself, which means keeping the Klenty API documentation open. Test it with Run once and read the bundle it returns before you chain other modules. If the data lives in another tool, that app's own Make modules may be simpler.
05Is Make or n8n better for Klenty?
It depends on the tool your team already uses. In Make, Klenty comes with 25 modules, including 9 instant triggers and Make an API Call, all set up through a visual editor. The same app often has an n8n node too, so if you already build in n8n, check what that node covers before moving. Compare the modules you need on each side, then pick the tool where you will maintain the scenario.
Same platform

Other docs you might need on this stack.

Browse all integrations