Resources · Make integration

lc.cx Make integrationAutomate lc.cx with Make.

Can Make handle your lc.cx short links for you? Yes: the lc.cx Make integration gives you 7 modules, one trigger and six others, to create, read, list, edit and remove links. This guide connects your account and walks you through a first working scenario.

Try the lc.cx integration on Make See the 7 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the lc.cx Make integration let you automate?

The lc.cx Make integration links your lc.cx account to Make, so short links get created, updated, looked up or deleted inside a scenario (the automation you build in Make, a chain of modules) instead of by hand. Each module is one brick of that chain: a trigger that starts it, an action that does something, or a search that finds items.

Short links made from data you already have. A marketing team keeps its campaign pages in a spreadsheet or a form tool. A scenario reads each new entry there and passes it to Create a Short Link, so the link exists without anyone opening lc.cx. The 123FormBuilder Make integration is one possible starting point.

A running log of every new link. Watch New Short Links picks up links created in lc.cx and hands each one to the next module, for example a row in a shared sheet, so the whole team can see what was published.

A cleanup pass on old links. List Short Links pulls your links out, a filter keeps the ones you no longer need, and Update a Short Link or Delete a Short Link acts on them.

Keep the limits in mind. The Make documentation for lc.cx gives no official description of the modules and warns that its content may contain errors, so check important details with lc.cx. When a listed module does not cover your case, Make an API Call reaches the rest of the lc.cx API. If you are also weighing n8n, the n8n vs Make comparison sets out the criteria, and the Make training covers scenario building from scratch.

Connect

How do you connect your lc.cx account to Make?

01
Generate an API key in lc.cx
You need an active lc.cx account and an API key. In lc.cx, open the API Integration section, click Generate a new API key, describe the usage, click Next and copy the key that appears.
02
Add an lc.cx module and open the connection window
In your Make scenario, add any lc.cx module and click Create a connection. A connection is your lc.cx account linked to Make once; every lc.cx module in your scenarios reuses it afterwards.
03
Name the connection and paste the key
The Connection name field is optional, but a clear name helps when you run several accounts. Paste the API key you copied, or follow the on-screen instructions, then confirm to save the connection.

First scenario

Your first scenario: turn new entries into lc.cx short links

GoalWhen a new entry lands in another app you use, Make creates an lc.cx short link for it.

01
Create the scenario
From the Scenarios page, create a new scenario and click the +. The first module is the app where your long URLs live, such as a sheet or a form tool.
02
Set up the starting module
Search that app by name, pick its module, link your account with Create a connection and fill its fields. Make lists the sheets or objects it can read once the connection exists.
03
Add Create a Short Link
Click the + on the right of the first module, search lc.cx and pick Create a Short Link. Use the connection from the previous section, then map the URL from the first module into it.
04
Test with Run once
Click Run once. Make executes the scenario one time and shows the bundles each module received; a bundle is one item passed along, here one entry and then one new short link.
05
Schedule and switch it on
Open the clock on the first module to set the schedule, which is every 15 minutes by default on a new scenario, then switch the scenario on. From now on, each new entry gets its short link.

Triggers

What can start an lc.cx scenario?

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

lc.cx1Watch New Short Links

Watch New Short Links

triggerIn the docs only

Watch New Short Links gives you a scenario that reacts to links you or your team create in lc.cx, handing each new one to the modules that follow. It is the only lc.cx trigger, so it is where any scenario built around fresh links begins.

How it fires

scheduled: Make checks lc.cx on the scenario's schedule, every 15 minutes by default, with 15 minutes as the shortest interval on the Free plan and 1 minute on paid plans.

When to use it

when every link published in lc.cx should also show up somewhere else, like a shared sheet or a team channel.

Watch out

nothing happens between two checks, so a link created just after a run waits for the next one.

Modules

What can lc.cx do inside a scenario?

lc.cx gives you 6 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

lc.cx1

Create a Short Link

ActionIn the docs only

Create a Short Link produces a new lc.cx link from data flowing through your scenario, so nobody has to paste URLs into lc.cx by hand anymore.

When to use it

right after the module that brings in a new page, product or campaign, when that item needs its own link to share.

Watch out

the module runs once per bundle it receives, so a search upstream that returns several rows creates one link per row.

lc.cx2

Delete a Short Link

ActionIn the docs only

Delete a Short Link removes a link from your lc.cx account, which keeps expired campaign links from piling up without a manual sweep.

When to use it

after List Short Links and a filter, once you are sure which links should go.

Watch out

treat deletion as final and test the scenario with Run once on a throwaway link before pointing it at real ones.

lc.cx3

Get a Short Link

ActionIn the docs only

Get a Short Link fetches one specific link and its details, so the next module can work with fresh information rather than an old copy.

When to use it

when you already know which link you want, for example one stored in a sheet row, and need its current state.

Watch out

it targets a single link; to scan many, List Short Links is the better fit.

lc.cx4

List Short Links

SearchIn the docs only

List Short Links returns the links in your account as separate bundles, giving you a base for reports, cleanups or bulk edits.

When to use it

when you do not know in advance which links matter and want to sort through them with a filter.

Watch out

it can return zero, one or many bundles, and every module after it runs once per bundle, which adds operations on your plan.

lc.cx5

Make an API Call

ActionIn the docs only

Make an API Call lets you reach any endpoint of the lc.cx API from your scenario, with the connection you already set up, for the jobs the other modules do not cover.

When to use it

when the lc.cx API offers something you need and none of the six named modules does it.

Watch out

you write the request yourself, so keep the lc.cx API documentation open beside the editor.

lc.cx6

Update a Short Link

ActionIn the docs only

Update a Short Link edits a link that already exists in your lc.cx account, so you correct it from the scenario instead of recreating it by hand.

When to use it

when a source record changes, such as a page that moved, and the matching lc.cx link has to follow.

Watch out

the module needs to know which link to change, so place Get a Short Link or List Short Links before it when the link is not already in your data.

Need help

Need help automating lc.cx with Make?

A person reads every message.

FAQ

Questions people ask about lc.cx and Make

01Is the lc.cx Make integration free?

Yes, lc.cx is a standard app in Make, so it works on the Free plan. That plan allows 2 active scenarios, a shortest interval of 15 minutes 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) drop the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes per execution. Usage is counted in operations each month, one per module run on one bundle. You still need your own lc.cx account.

02What do you need to connect lc.cx to Make?

You need an active lc.cx account and an lc.cx API key. Generate the key in the API Integration section of lc.cx by clicking Generate a new API key, describing its usage and clicking Next, then copy it. In Make, add any lc.cx module, click Create a connection, give the connection a name if you like and paste the key. The connection is saved once and every lc.cx module in your scenarios can reuse it, so you do not repeat this for each new scenario.

03Does the lc.cx trigger in Make fire in real time?

No. Watch New Short Links works as a scheduled trigger (the documentation does not describe it, so look for the clock badge on the module): Make checks lc.cx on the schedule of the scenario rather than being notified by lc.cx the moment a link appears. 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. If you need a link handled faster, shorten the schedule on a paid plan or start the scenario from another app and let lc.cx modules do the work.

04What if the lc.cx module you need is missing in Make?

Use Make an API Call. It sends a request to any endpoint of the lc.cx API with the same connection as the other modules, so anything the lc.cx API allows is within reach even without a dedicated module. The catch is that you build the request yourself from the lc.cx API documentation. Also keep in mind that the Make documentation for lc.cx warns its content may contain errors, so confirm important details with lc.cx before relying on them.

05Make or n8n for lc.cx?

It depends on your criteria, not on a winner. On Make, lc.cx offers 7 modules: one scheduled trigger, five actions including Make an API Call, and one search, all usable from the Free plan with no code. n8n often has a node for the same app, so check whether lc.cx has one there before you choose. The n8n vs Make comparison linked above sets out the general criteria to weigh, and Make remains the tool this guide walks you through step by step.

Generate an API key in lc.cx

Add an lc.cx module and open the connection window

Name the connection and paste the key

Create the scenario

Set up the starting module

Add Create a Short Link

Test with Run once

Schedule and switch it on

Need help automating lc.cx with Make?