Resources · Make integration

LeadSquared Make integrationAutomate LeadSquared with Make.

Can Make keep your LeadSquared CRM moving without manual copy and paste? The LeadSquared Make integration gives you 21 modules: one instant trigger, 17 actions and 3 searches. This guide walks sales ops teams through the connection, a first scenario and every module.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the LeadSquared Make integration do for your team?

The LeadSquared Make integration links your LeadSquared account to Make, a no-code tool where you build a scenario: the automation itself, a chain of modules that runs on a schedule or when an app calls Make. Each module is one brick, such as a trigger, an action or a search, and here they cover leads, activities, sales activities, tasks and users.

Follow-ups nobody has to remember. Watch New Events fires as soon as LeadSquared reports something new, and Create a Task writes the next step into LeadSquared without anyone opening the CRM.

One clean lead record from every form. Leads arriving from another tool go through Create or Update a Lead, so an existing contact gets refreshed instead of duplicated. Pair it with a booking app such as the Acuity Scheduling Make integration for booked calls.

A pipeline you can report on elsewhere. Search Sales Activities pulls deals out of LeadSquared so a spreadsheet or a base like the Airtable Make integration can hold the numbers your managers read.

The listed modules do not cover everything the LeadSquared API offers. When you hit a gap, Make an API Call reaches any endpoint with the same connection. The doc also carries a warning of its own: it is AI-generated from LeadSquared material, so check important details with LeadSquared directly.

If you are weighing tools, the n8n vs Make comparison lays out the criteria, since the same app often has an n8n node too.

Connect

How do you connect LeadSquared to Make?

  1. 01

    Copy your keys from LeadSquared

    In LeadSquared, open Settings, then API and Webhooks. Copy the Access Key, the Secret Key and the API host shown in the same section. You need an active LeadSquared account with API access for this screen to help.

  2. 02

    Add a LeadSquared module in Make

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

  3. 03

    Name it and paste the credentials

    The Connection name field is optional, but a clear name helps when several accounts live in one Make workspace. Paste the keys and host you copied, or follow the on-screen instructions, then save.

First scenario

Build your first scenario with LeadSquared

GoalWhen LeadSquared reports a new event, Make creates a task so a rep knows what to do next.

  1. 01

    Create the scenario

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

  2. 02

    Add Watch New Events

    Search for LeadSquared, pick Watch New Events, then click Create a webhook and Create a connection with the keys you copied earlier.

  3. 03

    Add Create a Task

    Click the + on the right of the trigger, choose LeadSquared again and select Create a Task. Map data from the event into the task fields Make shows you.

  4. 04

    Test with Run once

    Click Run once, then trigger an event in LeadSquared. Each module shows the bundles it received: a bundle is one item passing from one module to the next.

  5. 05

    Switch it on

    Once the task looks right in LeadSquared, switch the scenario on. From then on every new event runs the flow, and each module execution counts as one operation on your plan.

Triggers

What starts a LeadSquared scenario

1 module starts a scenario when something happens in LeadSquared. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by LeadSquared as soon as it happens.

LeadSquared1Watch New Events

Watch New Events

Instant trigger

In MakeTriggers on a new event.

Watch New Events gives your scenario a starting signal straight from LeadSquared: every new event lands in Make as a bundle, ready for the modules that follow. It is the only trigger this app offers, so every automated flow that reacts to LeadSquared begins here.

How it fires
instant: the app calls Make through a webhook as soon as it happens, which is why the module carries the lightning badge and not the clock.
When to use it
any flow that should react to what happens in the CRM, like turning an event into a task or copying it to a sheet.
Watch out
the doc asks for Create a webhook before Create a connection on instant modules, so follow that order.
Modules

Every LeadSquared module in Make

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

LeadSquared1

Cancel a Sales Activity

Action

In MakeCancels an existing sales activity.

This module marks an existing sales activity as cancelled, so a deal that fell through shows as called off in LeadSquared instead of still looking active.

When to use it
a refund or a cancelled order in another tool should cancel the matching sale in the CRM.
Watch out
Delete a Lead removes the whole contact, a far bigger step; Cancel only touches the sale.
LeadSquared2

Create an Activity

Action

In MakeCreates an activity for existing lead.

Log what just happened on a lead's timeline without a rep typing it: Create an Activity attaches a new activity to a lead that already exists in LeadSquared.

When to use it
a webinar attendance, a signed quote or a support ticket in another app should appear on the lead's history.
Watch out
the lead must exist first, so place Create or Update a Lead or Search Leads earlier in the scenario when you are unsure.
LeadSquared3

Create a Sales Activity

Action

In MakeCreates a sales activity for existing lead.

Record a sale against a lead directly from your scenario. Create a Sales Activity adds that deal to an existing lead, which keeps revenue tracking inside LeadSquared accurate.

When to use it
a paid order in your shop or billing tool should show up as a sale on the right contact.
Watch out
this is different from Create an Activity, which logs a generic event; choose this one only when the record is a sale.
LeadSquared4

Create a Task

Action

In MakeCreates a new task.

Nobody forgets the next step when Make writes it for them. Create a Task adds a new task in LeadSquared, ready for a rep to pick up in their usual view.

When to use it
right after Watch New Events, to turn a fresh event into a call or email the team must handle.
Watch out
a scenario that fires on many events creates many tasks, so check the volume in Run once before switching the scenario on.
LeadSquared5

Create a User

Action

In MakeCreates a new user.

Onboarding a new colleague gets shorter: Create a User opens a LeadSquared user account from data held somewhere else, such as your HR tool or an approval form.

When to use it
a hire confirmed in another system should get CRM access without waiting on an admin.
Watch out
user accounts touch access rights, so test this one with Run once on a dummy colleague before switching the scenario on.
LeadSquared6

Create or Update a Lead

Action

In MakeCreates or updates an existing lead.

Your lead list stays free of duplicates: this module creates the lead when it is new and updates it when it already exists, in a single step.

When to use it
any form, booking tool or ad platform feeding contacts into LeadSquared, where the same person may sign up twice.
Watch out
it writes to the CRM on every run; when you only need to check whether a contact exists, Search Leads is the lighter choice.
LeadSquared7

Delete a Lead

Action

In MakeDeletes an existing lead.

Remove a lead from LeadSquared automatically when it should no longer live in the CRM, for example after a deletion request handled in another tool.

When to use it
a privacy request or a clean-up list in a spreadsheet names contacts that must go.
Watch out
treat a delete as permanent and test on a throwaway record; if you only want the lead out of the pipeline, updating it is the safer move.
LeadSquared8

Delete an Activity

Action

In MakeDeletes an existing activity.

Wrong entries vanish from a lead's timeline: Delete an Activity removes an existing activity that was logged by mistake or duplicated by an earlier run.

When to use it
you notice a scenario logged the same activity twice and want a repair flow that tidies the history.
Watch out
sales records have their own module; for a sale that fell through, Cancel a Sales Activity describes what happened more accurately.
LeadSquared9

Delete a Task

Action

In MakeDeletes an existing task.

Stale to-dos disappear from reps' lists when this module removes an existing task that no longer makes sense.

When to use it
a meeting booked elsewhere means the reminder task created earlier is now pointless.
Watch out
removing is not closing; if the team wants to see that the task was handled, reach for Update a Task instead and keep the record.
LeadSquared10

Get an Activity

Action

In MakeRetrives an existing activity.

Pull the full content of one existing activity into your scenario, so later modules can read its details and act on them.

When to use it
an earlier module only gives you a reference to the activity and the next module needs the rest of the record, for instance to post a summary in a team chat.
Watch out
a Get module returns one item; when you need several activities at once, a search module fits better.
LeadSquared11

Get a Task

Action

In MakeRetrives an existing task.

Read one task back from LeadSquared before deciding what to do with it: Get a Task fetches an existing task and exposes it to the rest of the flow.

When to use it
you want to check what a task currently says before Update a Task or Delete a Task runs.
Watch out
it reads, it never changes anything, so pair it with an action module when the goal is to modify.
LeadSquared12

Get a User

Action

In MakeRetrives an existing user.

Knowing who owns a record is often the missing piece. Get a User brings one existing LeadSquared user into the scenario, with the details the CRM holds about that person.

When to use it
you need the owner's details to address an alert or copy them into a report.
Watch out
for the whole team rather than one person, List Users is the right module.
LeadSquared13

Make an API Call

Action

In MakePerforms an arbitrary authorized API call.

Anything the listed modules miss stays reachable: Make an API Call sends an authorized request to any LeadSquared API endpoint, using the connection you already set up.

When to use it
the object or action you need has no dedicated module among the 21.
Watch out
you write the request yourself, so keep LeadSquared's API reference open and check the answer in Run once before going live.
LeadSquared14

Update an Activity

Action

In MakeUpdates an existing activity.

Correct or enrich an activity already on a lead's timeline, so the history reflects what really happened after the first entry.

When to use it
an event logged at sign-up later gets a result, like a demo that moved from planned to attended.
Watch out
sales activities are a separate object, so a sale needs Update a Sales Activity, not this module.
LeadSquared15

Update a Sales Activity

Action

In MakeUpdates an existing sales activity.

Keep a deal's record current when its details change outside the CRM: this module edits an existing sales activity in place.

When to use it
an order amended in your billing tool should be reflected on the matching sale in LeadSquared.
Watch out
if the sale is off entirely, Cancel a Sales Activity says so more clearly than editing its values.
LeadSquared16

Update a Task

Action

In MakeUpdates an existing task.

Tasks follow reality without a rep editing them by hand. Update a Task changes an existing task, so the CRM shows where each follow-up really stands.

When to use it
a reply received in another tool means the follow-up task can move forward.
Watch out
you need the task first; Get a Task or the bundle from an earlier module usually supplies it.
LeadSquared17

Update a User

Action

In MakeUpdates an existing user.

Team changes reach the CRM on their own when Update a User edits an existing LeadSquared user from data held elsewhere.

When to use it
a rep's details change in your HR system and LeadSquared should match.
Watch out
it edits a real colleague's account, so run the scenario once on a test account before trusting it with the whole team.
LeadSquared18

List Users

Search

In MakeLists all existing users.

Get the whole LeadSquared team as a list inside your scenario. List Users returns every existing user, each one as its own bundle.

When to use it
you want to sync the sales team to a sheet, or build a per-rep report.
Watch out
every user becomes a bundle, and each module after it runs once per bundle, which multiplies operations.
LeadSquared19

Search Leads

Search

In MakeSearches for existing leads or lists them all.

Find the leads you need, or all of them, and hand them to the next module. Search Leads can return zero, one or many results.

When to use it
check whether a contact already exists before logging an activity, or export leads to a report.
Watch out
zero results means no bundle to pass on, so decide what the scenario should do when the contact is new.
LeadSquared20

Search Sales Activities

Search

In MakeSearches for sales activities.

Pull sales out of LeadSquared for reporting or cross-checks: Search Sales Activities returns the matching deals, one bundle each.

When to use it
building a revenue table in a spreadsheet, or finding the sale to cancel after a refund.
Watch out
several matches mean several bundles, so an aggregator helps when you want one summary row rather than one row per sale.
Need help

Need help automating LeadSquared with Make?

A person reads every message.

FAQ

LeadSquared and Make: common questions

01Is the LeadSquared Make integration free?
Yes, on the Make side. LeadSquared is a standard app, so it works on the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between 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) drop the interval to 1 minute, remove the cap on active scenarios and count usage in credits each month. You still need your own LeadSquared subscription with API access.
02What do you need to connect LeadSquared to Make?
An active LeadSquared account with valid API access. In LeadSquared, go to Settings, then API and Webhooks, and copy the Access Key, the Secret Key and the API host. In Make, add a LeadSquared module, click Create a connection, optionally name it, and paste those three values. The connection is then reused by every LeadSquared module in your scenarios, so this setup happens only once per account. If you manage several LeadSquared accounts, give each connection a clear name.
03Does the LeadSquared trigger in Make fire in real time?
Yes. Watch New Events is an instant trigger: LeadSquared calls Make through a webhook as soon as a new event happens, instead of Make checking on a schedule. That is why the module shows a lightning badge. When you add it, click Create a webhook first and then Create a connection. All the other modules are actions and searches, so they run only when a trigger or a schedule starts the scenario.
04What if a LeadSquared module you need is missing in Make?
Use Make an API Call. It sends an authorized request to any endpoint of the LeadSquared API with the connection you already have, so objects without a dedicated module stay reachable. You write the request yourself from LeadSquared's API reference. Keep in mind that the Make doc for this app is AI-generated from LeadSquared material, so verify important details with LeadSquared before relying on them. Test every custom call with Run once first.
05Should you use Make or n8n for LeadSquared?
It depends on your criteria, not on a winner. In Make, LeadSquared offers 21 modules: one instant trigger, 17 actions and 3 searches, plus Make an API Call for the rest, and it runs on the Free plan. The same app often has an n8n node too, so check the node list there and compare the modules each side covers for your use case. Pick the tool whose modules match the flow you want to build.