Resources · Make integration

LeadTable Make integrationAutomate LeadTable with Make.

Your leads can update themselves while your team keeps selling. The LeadTable Make integration gives you 14 modules: 3 triggers that watch your leads and 11 modules that create, update, search or enrich them. This page shows you how to link your account and build a first scenario.

Try the LeadTable integration on MakeSee the 14 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the LeadTable Make integration do for your pipeline?

The LeadTable Make integration links your LeadTable account to Make so your leads move without copy and paste. In Make you build a scenario, the automation itself, out of modules: each module is one brick, such as a trigger that watches LeadTable or an action that changes a lead.

Every form contact becomes a lead. A contact collected in another app goes through Create a new Lead, then Add a Note to the History of a Lead records where it came from. Your sales reps open a lead that already tells its story.

A status change sets the next task in motion. Watch Lead Status Changes spots the lead that moved, and the next module in the scenario takes over: a message to the account owner, a row in a report, a file attached with Upload a File to a Lead.

A whole campaign, handled in one pass. Get all Leads in a Campaign pulls the leads of one campaign so you can export them or push them into another tool.

Know the limits before you start. The three triggers are scheduled, so Make checks LeadTable on the scenario's schedule instead of hearing from it at once. The Make documentation for LeadTable is AI-generated from the vendor's docs and says so, so check anything critical with LeadTable directly. If the Make editor is new to you, the Make training starts from zero, and the Make pricing page explains how operations are counted. Weighing another tool? Read n8n vs Make.

Connect

How do you connect LeadTable to Make?

  1. 01

    Copy your API key in LeadTable

    In LeadTable, find your agency email address in the sidebar, then go to Settings > Account. Click the button that creates a new API key and copy the key shown on screen. Make needs it to act in your name.

  2. 02

    Open the connection window in Make

    In your scenario, add any LeadTable module and click Create a connection. The Connection name field is optional, but a clear name helps when several accounts live in the same Make organization.

  3. 03

    Paste the key and save

    Paste the API key you copied, or follow the instructions Make shows on screen, then save. The connection is now stored: every other LeadTable module reuses it, so you only do this once.

First scenario

Your first scenario: form contacts turned into LeadTable leads

GoalWhen a contact comes in through another app, Make creates the lead in LeadTable and adds a note that tells your team where it came from.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the +. Pick the app where your contacts arrive, such as your form tool, and choose its module that watches new entries.

  2. 02

    Add Create a new Lead

    Click the + on the right, search for LeadTable and pick Create a new Lead. Select your connection, then map the contact details from the first module into the fields Make shows for the lead.

  3. 03

    Log where the lead came from

    Add Add a Note to the History of a Lead. Map the lead returned by the previous module and write a short note naming the form, so your reps see the origin at a glance.

  4. 04

    Test with Run once

    Click Run once, then submit a test entry in your form. Open each module's bubble to read the bundle it received, meaning the item passed along, and check the new lead in LeadTable.

  5. 05

    Schedule and switch on

    Open the clock on the first module: a new scenario runs every 15 minutes by default, and 15 minutes is also the shortest interval on the Free plan. Save, then switch the scenario on.

Triggers

What can start a LeadTable scenario?

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

LeadTable1Watch Lead Status Changes

Watch Lead Status Changes

triggerIn the docs only

You get a scenario that reacts when a lead moves from one status to another, so the right follow-up happens without anyone checking the list by hand. Each lead that changed arrives as one bundle you can map into the next module.

How it fires
scheduled, Make checks LeadTable on the scenario's schedule and picks up the changes since the last check.
When to use it
a lead reaches the stage where a contract, a reminder or a handover to another rep should follow.
Watch out
pairing it with Update a Lead Status in the same scenario can make a lead trigger its own run again, so add a filter or keep the two apart.
LeadTable2Watch New Lead Creations

Watch New Lead Creations

triggerIn the docs only

This gives you a starting point for every lead added to LeadTable, whoever created it. Make hands over each fresh lead as a bundle, ready to be enriched, announced to the team or copied into another tool.

How it fires
scheduled, Make asks LeadTable for new leads at the pace set on the scenario, not at the instant the lead appears.
When to use it
a welcome note on the lead, an alert to the rep who owns the account, or a copy into a reporting sheet.
Watch out
each new lead costs at least one operation per module it goes through, so a busy import can use a large share of your plan.
LeadTable3Watch New Lead Updates

Watch New Lead Updates

triggerIn the docs only

With this trigger your scenario hears about any edit on a lead, not only status moves. It is the widest of the three watchers and suits jobs where the whole record must stay in sync elsewhere.

How it fires
scheduled, Make checks LeadTable for edited leads each time the scenario's clock comes around.
When to use it
you mirror your leads in another CRM or a spreadsheet and want every change carried over.
Watch out
a LeadTable module that edits the same lead in this scenario will likely register as an update too, which can start a loop; if only statuses matter, Watch Lead Status Changes is the calmer choice.
Modules

What can the LeadTable modules do?

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

LeadTable1

Update a Lead Description

ActionIn the docs only

Keeps the description of a lead current by writing new text into it from your scenario. Your reps open the lead and read the latest context instead of an outdated summary.

When to use it
a call summary or a form answer from another app should become the lead's description.
Watch out
the module needs to know which lead to edit, so place a search or a trigger before it and map the lead it returns.
LeadTable2

Update a Lead Status

ActionIn the docs only

Moves a lead to another status without anyone opening LeadTable. The pipeline reflects what really happened, for example a meeting booked or a quote signed in another tool.

When to use it
an event outside LeadTable, such as a signed document, should push the lead forward.
Watch out
a scenario that also starts on Watch Lead Status Changes will see its own change, so keep them apart.
LeadTable3

Add a Note to the History of a Lead

ActionIn the docs only

Writes a trace into the lead's history, so anyone opening the record knows what happened and where it came from. Unlike the description, a note adds to the history instead of replacing text.

When to use it
logging an email sent, a form submitted or a call booked by another app.
Watch out
you need the lead first, so place a search or a create module before it.
LeadTable4

Create a new Lead

ActionIn the docs only

Turns a contact from anywhere into a LeadTable lead, filled from the data of the previous module. No more retyping names and emails collected by a form or an event tool.

When to use it
a sign-up, a demo request or a trade show scan should land in LeadTable.
Watch out
to avoid a second record for the same person, run Search a Lead by its Email Address before it.
LeadTable5

Delete a Lead by its ID

ActionIn the docs only

Removes a lead for good once you give it the lead's ID. It helps you keep LeadTable clean when a contact asks to be forgotten or turns out to be a test entry.

When to use it
a removal request arrives through a form and must be applied in LeadTable too.
Watch out
the lead is gone for good, so test on a dummy lead first and add a filter before this module.
LeadTable6

Get all Leads in a Campaign

ActionIn the docs only

Pulls the leads of one campaign into your scenario so you can act on the whole group at once: export them, score them elsewhere or send them to another tool.

When to use it
a campaign ends and its leads must be shared with the sales team or a reporting sheet.
Watch out
when several leads come back, the next modules run once per lead, and each run counts as an operation.
LeadTable7

Make an API Call

ActionIn the docs only

Reaches any endpoint of the LeadTable API from your scenario, with the same connection as the other modules. This is how you cover a need that none of the listed modules handles.

When to use it
you need a LeadTable operation that has no dedicated module in Make.
Watch out
you write the request yourself, so check the LeadTable API documentation for the path and the expected data.
LeadTable8

Search a Lead by its Email Address

SearchIn the docs only

Finds the lead that matches an email address, the detail you usually have when a contact writes in or fills a form. It gives you the lead's ID for the modules that follow.

When to use it
before creating a lead, to check whether that person is already in LeadTable.
Watch out
a search can return zero, one or several bundles, so plan what happens when nothing is found.
LeadTable9

Search a Lead by its ID

SearchIn the docs only

Fetches one precise lead when you already hold its ID, for instance stored in a spreadsheet or returned by another module. You get its current data to reuse further down.

When to use it
another tool keeps the LeadTable ID and needs fresh details before acting.
Watch out
an ID copied from a test account will not match your live leads, so map it from real data.
LeadTable10

Update or Create an Answer in the Lead Profile

ActionIn the docs only

Stores an answer in the lead's profile, updating it if one is there and adding it if not. The profile fills up with what you learn about the lead without you sorting new from existing.

When to use it
a qualification form or survey in another app collects answers that belong on the lead.
Watch out
try it with Run once on a single lead and read the profile in LeadTable before letting it run on many.
LeadTable11

Upload a File to a Lead

ActionIn the docs only

Attaches a file to a lead, so a quote, a brief or a signed document sits with the record instead of in someone's inbox. The file comes from a previous module, such as a storage or email app.

When to use it
a document generated or received elsewhere must follow the lead.
Watch out
on the Make Free plan, files are capped at 5 MB, so large attachments need a paid plan.
Need help

Need help automating LeadTable with Make?

A person reads every message.

FAQ

Questions about the LeadTable Make integration

01Is the LeadTable Make integration free?
Yes, on the Make side. LeadTable is a standard app, so its modules are available from the Make Free plan. That plan allows 2 active scenarios, 15 minutes at least between two scheduled runs, 5 minutes 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, allow unlimited active scenarios and count usage in credits per month. You still need an active LeadTable account, which LeadTable bills on its own pricing page.
02What do you need to connect LeadTable to Make?
An active LeadTable account and its API key. In LeadTable, find your agency email address in the sidebar, go to Settings, then Account, click the button that creates a new API key and copy it. In Make, add a LeadTable module, click Create a connection, give the connection a name if you like, and paste the key. The connection is saved once and reused by all 14 modules, so every new scenario starts with your account already linked.
03Do the LeadTable triggers fire instantly?
No. The three LeadTable triggers are scheduled: the Make docs give no instant version, and their type is read from their names. Make checks LeadTable at the pace set on the scenario, every 15 minutes by default and never more often than every 15 minutes on the Free plan. Paid plans can go down to 1 minute. A lead created or updated just after a check is therefore picked up at the next one. If a delay matters, run the scenario on a paid plan with a shorter interval.
04What if a LeadTable module is missing in Make?
Use Make an API Call. It sends a request to any endpoint of the LeadTable API with the same connection as the other modules, so you are not limited to the 11 listed actions and searches. You build the request yourself, which means reading the LeadTable API documentation for the path and the data it expects. Keep in mind that the Make documentation for this app is AI-generated from the vendor's docs, so confirm important details with LeadTable directly.
05Should you use Make or n8n for LeadTable?
It depends on the tool your automations already live in. On Make, LeadTable comes with 14 modules, 3 scheduled triggers and Make an API Call for the rest, all available from the Free plan. The same app often has an n8n node too, so check its availability there before choosing. The n8n vs Make comparison linked on this page sets out the criteria side by side, without ranking one tool above the other.
Same platform

Other docs you might need on this stack.

Browse all integrations