Resources · Make integration

LionDesk Make integrationAutomate LionDesk with Make.

Can Make keep your LionDesk CRM up to date on its own? The LionDesk Make integration gives you 50 modules, 40 actions and 10 searches, for contacts, leads, campaigns and events. This page shows how to connect your account and build a first working scenario.

Try the LionDesk integration on MakeSee the 50 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the LionDesk Make integration do?

The LionDesk Make integration links your LionDesk account to Make, a no-code tool where you build a scenario: an automation made of modules, each one a brick that acts on one app. Data coming from your forms, calendars or sheets can then create, update or remove LionDesk records without anyone copying it by hand.

New signups become contacts in a campaign. A form tool hands over each entry, Create Contact records the person and Create Campaign Contact enrolls them, so the follow-up starts without a copy-paste.

Bookings stay in step with the CRM. Create Event writes an appointment taken in your scheduling tool, Update Event follows a reschedule and Delete Event clears a cancellation.

Lead ratings move with real signals. Create/Update/Delete Contact Hotness raises a prospect when they reply or book a call, and Get Lead gives your routing step what it needs.

LionDesk has no trigger in Make: no module starts a scenario when something changes in LionDesk. A scenario opens on another app or on a schedule, and the List modules read LionDesk data on each run. When a listed module is missing, Make an API Call reaches the rest of the API. The same app may also exist in n8n; the n8n vs Make comparison lays out the criteria, and the Make pricing page explains what each plan counts. If you prefer to be guided, see the Make training.

Connect

How do you connect LionDesk to Make?

  1. 01

    Add a LionDesk module

    Open your scenario, click the + and search for LionDesk. Pick any module, for example Create Contact, then click Create a connection. A connection is your LionDesk account linked to Make once and reused by every LionDesk module.

  2. 02

    Name and authorize

    Give the connection a name if you like, handy when you run several LionDesk accounts. Then authorize Make on the LionDesk page that opens, or paste the key LionDesk gives you if Make asks for one.

  3. 03

    Save and check

    Click Save. Back in the module, Make can now read your LionDesk data, and the next LionDesk module you add will offer the same connection instead of asking again.

First scenario

Your first LionDesk scenario in Make

GoalWhen someone fills in your signup form, Make creates the person in LionDesk and adds them to a campaign.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + to add the first module. Here it comes from the form tool where your signups arrive, since LionDesk has no trigger.

  2. 02

    Add Create Contact

    Click the + on the right of the form module, search LionDesk and choose Create Contact. Click Create a connection and link your account if it is not done yet.

  3. 03

    Map the form answers

    Fill the module fields by mapping the answers from the form module instead of typing anything. Each signup is a bundle, one item passing from a module to the next.

  4. 04

    Enroll the contact

    Click the + again and add Create Campaign Contact. Map the contact returned by Create Contact and pick the campaign that should welcome new signups.

  5. 05

    Test with Run once

    Click Run once, send a test entry through your form and read the bundles each module received. Check in LionDesk that the contact exists and sits in the campaign.

  6. 06

    Schedule and switch on

    Set the schedule on the first module, every 15 minutes by default, and switch the scenario on. Each module run on a bundle counts as one operation on your Make plan.

Modules

What can LionDesk do in Make?

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

LionDesk1

Create Campaign

Action

In Make“Creates a new campaign.”

Opens a fresh campaign in LionDesk from your scenario, so a new offer or mailing wave gets its own container without a trip to the LionDesk screen.

When to use it
A new product launch is approved in your project tool and the sales team needs a matching campaign ready to receive contacts.
Watch out
Keep the campaign it returns and map it into Create Campaign Contact further down the scenario, otherwise the contacts land nowhere.
LionDesk2

Create Campaign Contact

Action

In Make“Creates a campaign contact.”

Puts an existing contact inside a campaign, which is how a person starts receiving what that campaign sends. It links the two records rather than creating a new person.

When to use it
A lead fills in your webinar form, Create Contact records the person, and this module enrolls them in the webinar follow-up campaign.
Watch out
It needs both the contact and the campaign from earlier modules; map them instead of typing values by hand.
LionDesk3

Create Contact

Action

In Make“Creates a new contact.”

Adds a person to your LionDesk contacts with the data your scenario collected, so nobody has to retype a form entry or a spreadsheet row.

When to use it
Every new signup from a landing page, a chat or an event list should become a LionDesk contact the moment it reaches Make.
Watch out
Make will not check for duplicates on its own; run List Contacts first when the same person can come back twice.
LionDesk4

Create Contact Address

Action

In Make“Creates an address to be attached to a contact.”

Attaches a postal address to a contact who already exists, so the record carries where the person lives or works and your team stops chasing it by email.

When to use it
Your quote form asks for a street address and you want it stored on the contact right after Create Contact runs.
Watch out
The address hangs on a contact, so map the contact returned by the previous module before filling anything else.
LionDesk5

Create Custom Field

Action

In Make“Creates a new custom field.”

Defines a new custom field in LionDesk, giving your contacts a slot for information the standard record does not hold, such as a budget range or a preferred channel.

When to use it
You add a question to your intake form and want LionDesk ready to hold the answer before contacts start carrying it.
Watch out
This builds the field itself, not its value for a person; values go through Create/Update/Delete Custom Value.
LionDesk6

Create Event

Action

In Make“Creates a new event.”

Writes an event into LionDesk, so a meeting or a call booked elsewhere shows up where your sales team already looks.

When to use it
A prospect books a slot in your scheduling tool and the appointment should appear in LionDesk without anyone copying it over.
Watch out
Map the date from the booking module rather than typing it, or every event lands on the same day.
LionDesk7

Create Hotness

Action

In Make“Creates a new level of hotness.”

Adds a new level to your LionDesk hotness scale, the ladder you use to say how warm a lead is. Your scenarios can then sort people on that new rung.

When to use it
Your team decides to split warm leads into two stages and wants the extra level available before any scenario assigns it.
Watch out
It creates the level only; giving that level to a contact is the job of Create/Update/Delete Contact Hotness.
LionDesk8

Create Lead

Action

In Make“Creates a new lead.”

Records a new lead in LionDesk, the entry point for someone your team has not qualified yet. The person becomes visible to sales as soon as the scenario runs.

When to use it
Inquiries arrive from an ad form or a partner list and you want them handled as leads rather than finished contacts.
Watch out
Decide once whether a new person is a lead or a contact in your process, then stick to one module to avoid split records.
LionDesk9

Create Source

Action

In Make“Creates a new source.”

Adds a new source to LionDesk, the label that tells where contacts come from. Your reports can then separate a fresh channel from the old ones.

When to use it
You open a new acquisition channel, a directory listing or a podcast, and want its contacts tagged with their origin from day one.
Watch out
This creates the source in your account; attaching it to one contact goes through Create/Update/Delete Source.
LionDesk10

Create Tag

Action

In Make“Creates a new tag.”

Creates a tag in LionDesk, the short label you pin on records to group them. Once it exists, filtering people by interest or status becomes a single click.

When to use it
A new service line starts and you want a tag ready for every contact who asks about it through your forms.
Watch out
Two tags with near-identical names split your lists; check List Tags before creating one from a scenario.
LionDesk11

Create/Update/Delete Contact Hotness

Action

In Make“Creates, updates or deletes a contact's hotness.”

Sets, changes or removes how hot a given contact is, all from one module. Your pipeline view reflects what just happened in another tool.

When to use it
A prospect opens a pricing email or books a call, and you want their hotness raised without a salesperson touching the record.
Watch out
One module, three behaviors: pick the right one in the settings, because a delete here clears the level you meant to raise.
LionDesk12

Create/Update/Delete Custom Value

Action

In Make“Creates, updates or deletes a contact's custom values.”

Fills, edits or clears the value a contact holds in one of your custom fields. It is where the answer from a form or survey finally lands on the person.

When to use it
Your onboarding survey collects a preferred contact time and you want it written into the matching custom field of each contact.
Watch out
The custom field must exist first; create it once with Create Custom Field, then let this module handle the values.
LionDesk13

Create/Update/Delete Source

Action

In Make“Creates, updates or deletes a contact's source.”

Assigns, corrects or removes the source attached to one contact, so your origin reports stay honest when a person was first logged under the wrong channel.

When to use it
A contact first counted as a website visit turns out to come from a partner referral, and you want the record fixed automatically.
Watch out
This works on a contact's source, not on your list of sources; new channels are added with Create Source.
LionDesk14

Delete Campaign

Action

In Make“Deletes a campaign.”

Removes a campaign from LionDesk, which keeps your campaign list short when an operation is over and nobody should be added to it anymore.

When to use it
A promotion is archived in your project tool and the matching LionDesk campaign should disappear with it.
Watch out
By its logic a delete cannot be undone from Make; test with Run once on a throwaway campaign before switching the scenario on.
LionDesk15

Delete Contact

Action

In Make“Deletes a contact.”

Erases a contact from LionDesk, which is what you reach for when a person asks to be forgotten or a test record slipped into production.

When to use it
An unsubscribe or data-removal request arrives through your support inbox and the person must leave the CRM too.
Watch out
Put a filter before it so only the intended contact reaches this module; a wrong mapping removes someone real.
LionDesk16

Delete Contact Address

Action

In Make“Deletes an address of a contact.”

Drops one address from a contact while keeping the person and the rest of the record intact, so outdated locations stop confusing your team.

When to use it
A client moves, the new address is added with Create Contact Address, and the old one needs to go.
Watch out
Map the right address from Get Contact Address or List Contact Addresses; a contact can hold several.
LionDesk17

Delete Custom Field

Action

In Make“Deletes a custom field.”

Removes a custom field from your LionDesk account, useful when a question no longer exists on your forms and the empty slot clutters every record.

When to use it
You retire an old intake question and want its field gone across the CRM, not just hidden in one view.
Watch out
Deleting the field logically takes the values stored in it along; export them first if they still matter.
LionDesk18

Delete Event

Action

In Make“Deletes an event.”

Takes an event off LionDesk, so a cancelled meeting does not keep appearing in your team's agenda as if it were still happening.

When to use it
A prospect cancels through your booking tool and the appointment should vanish from LionDesk as well.
Watch out
Find the matching event with List Events or Get Event first; deleting the wrong one leaves a real meeting unannounced.
LionDesk19

Delete Hotness

Action

In Make“Deletes a level of hotness.”

Removes a level from your hotness scale, handy when your team simplifies how it rates leads and an old step no longer means anything.

When to use it
Your sales process drops an intermediate lead stage and the matching level should leave the account.
Watch out
Contacts may still sit on that level; move them with Create/Update/Delete Contact Hotness before deleting it.
LionDesk20

Delete Source

Action

In Make“Deletes a source.”

Deletes a source from LionDesk, which keeps your origin list readable once a channel is closed and should not be picked anymore.

When to use it
A partnership ends and its source should no longer be offered when new contacts come in.
Watch out
Past contacts may still point to that source; decide whether their history matters before removing it for good.
LionDesk21

Delete Tag

Action

In Make“Deletes a tag.”

Removes a tag from your LionDesk account, the clean-up move when a label was created by mistake or a theme is no longer tracked.

When to use it
A scenario created a misspelled tag and you want it gone once the right one is in place.
Watch out
Check with Get Tag which one you target; two similar labels are easy to mix up in a mapping.
LionDesk22

Get Campaign

Action

In Make“Retrieves a campaign.”

Fetches one campaign with its details so later modules can read them, for example to write the campaign name into a message or a report.

When to use it
A contact joins a campaign and you want its name in the team alert or the email your scenario sends next.
Watch out
It returns a single campaign you already point to; to browse all of them, List Campaigns is the right pick.
LionDesk23

Get Contact

Action

In Make“Retrieves a contact.”

Reads one LionDesk contact in full, so the rest of the scenario can reuse the person's current details without asking anyone.

When to use it
Before sending a follow-up from another tool, you need the up-to-date details of the contact tied to the event.
Watch out
It expects a contact you can point to; when you only have a name or an email, search with List Contacts.
LionDesk24

Get Contact Address

Action

In Make“Retrieves an address of a contact.”

Pulls one specific address of a contact, ready to feed a shipping label, a visit plan or a document your scenario prepares.

When to use it
A signed deal must trigger a welcome package, and your shipping tool needs the contact's address.
Watch out
A contact can have several addresses; when you do not know which one, start with List Contact Addresses.
LionDesk25

Get Custom Field

Action

In Make“Retrieves a custom field.”

Returns the definition of one custom field, which lets a scenario check how a field is set up before writing values into it.

When to use it
You sync answers from a form and want to confirm the target field before Create/Update/Delete Custom Value fills it.
Watch out
This reads the field, not what a contact stored in it; a person's values are handled by Create/Update/Delete Custom Value.
LionDesk26

Get Event

Action

In Make“Retrieves an event.”

Loads a single event from LionDesk with its details, so you can remind the contact or brief a colleague with accurate information.

When to use it
A booking changes in your calendar tool and you need the LionDesk event as it stands before updating it.
Watch out
Point it to a known event; to find one among many, List Events returns them as separate bundles.
LionDesk27

Get Hotness

Action

In Make“Retrieves a level of hotness.”

Retrieves one level of your hotness scale, useful when a message or a report should show the level's wording instead of a bare reference.

When to use it
Your scenario tells a salesperson that a lead just became hot and the alert must spell out the level name.
Watch out
It describes the level itself, not who holds it; to change a person's level, use Create/Update/Delete Contact Hotness.
LionDesk28

Get Lead

Action

In Make“Retrieves a lead.”

Reads one lead with its details, giving the next modules what they need to qualify it, route it or notify the right person.

When to use it
A new lead needs to go to a specific salesperson, and your routing step reads its details first.
Watch out
Leads and contacts have separate modules here; use Get Contact when the person is stored as a contact.
LionDesk29

Get Lead Source

Action

In Make“Retrieves a lead source.”

Fetches one lead source, so your scenario can write where a lead came from into a notification, a sheet or an ad report.

When to use it
You log every new lead into a shared sheet and want the origin spelled out next to each name.
Watch out
This is the source used for leads; a contact's source is read with Get Source.
LionDesk30

Get Source

Action

In Make“Retrieves a source.”

Reads one source from your LionDesk account, so the name of a channel can travel into messages, sheets or dashboards built by your scenario.

When to use it
When a new client signs, an alert naming the channel that brought them is exactly the job of this module.
Watch out
It returns the source you point to; to see every source at once, run List Sources.
LionDesk31

Get Tag

Action

In Make“Retrieves a tag.”

Retrieves a single tag with its details, which helps a scenario confirm it is using the right label before applying or deleting it.

When to use it
Before Delete Tag runs, you want to check the tag's name in the bundle that Run once shows you.
Watch out
One tag in, one tag out; when you need the full catalogue of labels, List Tags is the module.
LionDesk32

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Calls any endpoint of the LionDesk API from your scenario with the same connection, which covers what the 50 listed modules leave out.

When to use it
You need a LionDesk action that no module offers, and you are comfortable reading the app's API reference.
Watch out
You write the request yourself, so check the API documentation of LionDesk for the path and the body it expects.
LionDesk33

Update Campaign

Action

In Make“Updates a campaign.”

Changes an existing campaign in LionDesk, so a renamed offer or a shifted focus shows up without anyone editing the campaign by hand.

When to use it
The marketing brief of a promotion changes in your project tool and the LionDesk campaign should follow.
Watch out
Find the right campaign first with List Campaigns or Get Campaign; editing the wrong one changes what other contacts receive.
LionDesk34

Update Contact

Action

In Make“Updates a contact.”

Writes fresh information onto a contact who already exists, keeping LionDesk in step with the tool where the person last changed their details.

When to use it
A client edits their phone number in your customer portal and the LionDesk record should match.
Watch out
Find the contact first with List Contacts or Get Contact; updating the wrong record silently overwrites someone else.
LionDesk35

Update Contact Address

Action

In Make“Updates a contact's address.”

Corrects one address of a contact in place, so a typo or a new floor number does not force you to delete and recreate it.

When to use it
Your delivery tool flags an address as incomplete and the fixed version should flow back into LionDesk.
Watch out
It needs the exact address to change; take it from Get Contact Address or List Contact Addresses first.
LionDesk36

Update Custom Field

Action

In Make“Updates a custom field.”

Edits the definition of a custom field, for instance its label, so every contact shows the new wording at once.

When to use it
You reword a question on your forms and want the field in LionDesk to carry the same wording.
Watch out
This changes the field for the whole account, not a contact's answer; answers go through Create/Update/Delete Custom Value.
LionDesk37

Update Event

Action

In Make“Updates an event.”

Moves or edits an event already in LionDesk, so a rescheduled meeting keeps its history instead of becoming a duplicate.

When to use it
A prospect picks a new slot in your booking tool and the same LionDesk event should shift with it.
Watch out
Map the new date from the booking module, and locate the event with Get Event rather than creating a second one.
LionDesk38

Update Hotness

Action

In Make“Updates a level of hotness.”

Renames or adjusts a level of your hotness scale, which lets your team refine its lead rating without rebuilding the whole ladder.

When to use it
The sales team agrees on clearer names for its levels and wants them changed in one go from a scenario.
Watch out
It edits the level shared by every contact on it; to move one person, use Create/Update/Delete Contact Hotness.
LionDesk39

Update Source

Action

In Make“Updates a source.”

Edits a source in your account, so a channel that changed name or scope keeps one clean entry across all its contacts.

When to use it
A marketing channel is renamed after a rebrand and the LionDesk source should carry the new name.
Watch out
The change applies to every contact pointing to that source; to fix one contact only, use Create/Update/Delete Source.
LionDesk40

Update Tag

Action

In Make“Updates a tag.”

Renames or adjusts a tag, and every record carrying it follows, which saves you from retagging contacts one by one.

When to use it
A tag was named after an old offer and you want the label to match the current one across the CRM.
Watch out
Check List Tags first so the new name does not collide with a label that already exists.
LionDesk41

List Campaigns

Search

In Make“Lists all campaigns.”

You get every campaign of your LionDesk account in one pass, each one arriving as its own bundle that later steps can read.

When to use it
Before adding a contact to a campaign you only know by name, so you can map the right one instead of hunting for it.
Watch out
Every module placed after it runs once per campaign returned, and each run costs an operation.
LionDesk42

List Contact Addresses

Search

In Make“Lists all the addresses of a contact.”

This search hands back all the addresses stored on one contact, so a single buyer with a home and a rental property shows up as two separate bundles.

When to use it
Pick it over Get Contact Address when you do not know which address you need yet and want to check them all.
Watch out
A contact with no address returns zero bundles, and the rest of that route simply stops.
LionDesk43

List Contacts

Search

In Make“Lists all contacts.”

Pull your whole LionDesk contact base into a scenario and act on each person one by one, for example to copy them into a spreadsheet or a mailing tool.

When to use it
For a one-off export or cleanup, where Get Contact would only fetch a single known record.
Watch out
A large database means many bundles, and the modules after it spend operations on every single one.
LionDesk44

List Custom Fields

Search

In Make“Lists all custom fields.”

Here you see which custom fields your account defines, one bundle per field, which tells you exactly what extra data your team tracks on contacts.

When to use it
Ahead of a Create/Update/Delete Custom Value step, to confirm the field you want to fill actually exists.
Watch out
Run it with Run once first and read the output, rather than guessing field names inside later modules.
LionDesk45

List Events

Search

In Make“Lists all events.”

All your LionDesk events come out as a stream of bundles, ready to be pushed into a calendar app, a team chat or a report built in another tool.

When to use it
When an agent's schedule needs to appear somewhere outside LionDesk and you want the full set, not a single event.
Watch out
The search returns every event it finds, so each one costs an operation in the modules that follow.
LionDesk46

List Hotnesses

Search

In Make“Lists all levels of hotness.”

You get every hotness level defined in your LionDesk account, one bundle per level, so a scenario can reuse the exact values instead of guessing them.

When to use it
Right before the Create/Update/Delete Contact Hotness module, to map a real level instead of typing one by hand.
Watch out
Levels differ from one account to another, so check the output after Run once before mapping anything.
LionDesk47

List Leads

Search

In Make“Lists all leads.”

Every lead in LionDesk lands in the scenario as a separate bundle, which gives you a clean starting point to route new prospects to the right agent or tool.

When to use it
Since LionDesk has no trigger, place it first and let the scenario's schedule decide when Make checks the list.
Watch out
The list is complete on every run, so leads you already handled come back too; plan how the next module treats them.
LionDesk48

List Lead Sources

Search

In Make“Lists all lead sources.”

Find out where your leads come from: the module returns each lead source recorded in LionDesk, one per bundle, so you can compare channels in a sheet.

When to use it
To build a small reporting table, or to spot the right source before a Get Lead Source step.
Watch out
Lead sources and contact sources are two different lists in LionDesk, and List Sources covers the other one.
LionDesk49

List Sources

Search

In Make“Lists all sources.”

Your contact sources (the origin label attached to each person) come back as a full list, which keeps a scenario consistent with the names your team already uses.

When to use it
Before Create/Update/Delete Source, when a form or another app sends a source name that must match an existing one.
Watch out
An empty account returns zero bundles, and the modules after it will not run.
LionDesk50

List Tags

Search

In Make“Lists all tags.”

With this search, the scenario knows every tag defined in LionDesk and can check one before applying it, which avoids creating near-duplicates such as two spellings of the same label.

When to use it
Ahead of Create Tag, to see whether the label you need is already there.
Watch out
Each returned tag triggers the next modules separately, and each of those runs counts as an operation.
Need help

Need help automating LionDesk with Make?

A person reads every message.

FAQ

Frequently asked questions

01Is the LionDesk Make integration free?
Yes. LionDesk is a standard app in Make, so it works from the Free plan. That plan keeps 2 active scenarios, runs scheduled scenarios at most every 15 minutes, stops each run after 5 minutes, and caps files at 5 MB with 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 credits, which are operations, each month. Nothing on this page quotes a price for LionDesk itself.
02What do you need to connect LionDesk to Make?
A LionDesk account and a Make account are enough to start. The LionDesk documentation in Make lists no prerequisite. You add any LionDesk module, click Create a connection, optionally name it, then authorize Make on the LionDesk page or paste the key LionDesk provides, and click Save. The connection is created once and reused by all 50 LionDesk modules, so you never repeat the step for each module you add to a scenario.
03Does LionDesk have a trigger in Make?
No. None of the 50 LionDesk modules is a trigger, so LionDesk cannot start a scenario by itself when a record changes. There are two ways around it. Open the scenario with a trigger from another app, such as the form or calendar where the data first appears. Or start on a schedule set on the first module, every 15 minutes by default, and use a List module such as List Contacts or List Leads to read LionDesk on each run.
04What if a LionDesk module is missing in Make?
Use Make an API Call. This module calls any endpoint of the LionDesk API with the connection you already have, so it covers what the 40 actions and 10 searches do not. You write the request yourself, which means reading the LionDesk API reference for the path and the data it expects. The LionDesk documentation in Make gives no numbered limit, so there is no documented cap to plan around beyond the rules of your Make plan.
05Should you use Make or n8n for LionDesk?
It depends on the tool your team already runs. In Make, LionDesk comes with 50 ready modules covering contacts, leads, campaigns, events, tags, sources and hotness levels, plus Make an API Call for the rest, and it is available from the Free plan. The same app may also exist as an n8n node. Compare the modules each side offers for your use case and pick the tool where the rest of your automations live, so every workflow stays in one place.
Same platform

Other docs you might need on this stack.

Browse all integrations