lc.cx Zapier integrationAutomate lc.cx with Zapier.
lc.cx Zapier integration: 1 trigger, 1 action and 0 searches. Small, but it covers both directions: Zapier can spot each new short link generated on lc.cx, and it can create one for you, on the lc.cx domain or on your own branded domain.
Verified Trustpilot reviews · AI, automation & growth agency
What the lc.cx Zapier integration actually does
The lc.cx Zapier integration links a URL shortener to your other tools. lc.cx turns long links into short ones, either on its own domain or on a branded domain you set up. Through Zapier, a new short link can start an automation, and any automation can ask lc.cx for a fresh short link without you pasting anything.
Two outcomes come out of it. A short link made on the fly: Generates a lc.cx or Brandred Shortlink takes a destination URL handed over by an earlier step and returns its short version, on the domain you pick. A record of every link created: New Generated Shortlink notices each new short link on your account, so another app can store it, share it or log it. That is the whole list, and the editor shows the action name with its spelling exactly like that.
What Zapier does not do here: there is no search, so a Zap cannot look up an existing short link or its stats. No action edits or deletes a link either. And the trigger is a polling one, which means it is not immediate; how long you wait depends on your plan. One more trap: a Zap that starts on a new short link and also creates one sets itself off in a loop.
Before committing to a plan, our Zapier review and the n8n vs Zapier comparison are worth a read.
Zapier vocabulary in one minute
Seven words carry the rest of the page. Each one is explained here once, then used as is.
- Zap
- The automation you build: one trigger, then one or more actions that run every single time that trigger event happens.
- Trigger
- The event in an app that starts the Zap. Once the Zap is switched on, Zapier waits for it. lc.cx offers one.
- Action
- What the Zap does after it starts: the step that writes, sends or moves something for you, like generating a short link.
- Task
- The unit Zapier bills. One task equals one action your Zap completes successfully; your plan counts those, nothing else.
- Polling vs instant
- A polling trigger is checked on a timer for new items. An instant trigger is reported by the app itself the moment the event happens.
- Filter
- A step that lets the Zap continue only when the incoming data meets a condition you set, and quietly stops it otherwise.
- Connection
- Your lc.cx account linked to Zapier once, then reused by every lc.cx step of every Zap you build.
What an lc.cx Zap really costs
lc.cx is not a premium app, so it works from the free plan. Zapier bills in tasks, and only actions that go through are counted.
- Premium appNo, available on the free plan
- Free plan100 tasks a month, unlimited Zaps
- Free plan Zap sizeTwo steps: one trigger, one action
- lc.cx triggerPolling, checked on your plan's interval
The New Generated Shortlink trigger never costs a task, and Zapier checking lc.cx for new links costs nothing either, however often it looks. Each short link the action generates successfully counts once; a failed attempt is not billed. The free plan gives 100 tasks a month and unlimited Zaps, limited to two steps: one trigger, one action. Add a filter or a second action and the Zap becomes multi-step (anything beyond one trigger and one action), which needs a paid plan. Because the trigger is a polling one, the grid below sets how often Zapier checks.
Connect lc.cx to Zapier in three steps
- 01
Open the Apps page
In your Zapier account, go to Apps and click + Add connection. You need an lc.cx account, plus access to any branded domain you did not set up yourself but want the Zap to use.
- 02
Pick lc.cx
Type lc.cx in the search box of the dialog, select it, then click Add connection. A new tab opens on the lc.cx side, where the actual sign-in to your account takes place.
- 03
Sign in and allow access
Log in to lc.cx in that tab and grant Zapier access to the account. The connection then shows up in your list, and every lc.cx step of every Zap reuses it.
Your first lc.cx Zap, step by step
GoalSend each new lc.cx short link to another app, but only when it meets a condition you choose.
- 01
Create the Zap
Create a new Zap, pick lc.cx as the app that starts it and choose New Generated Shortlink as the event. Select your lc.cx connection and fill in Destination and Domains.
- 02
Test the trigger
Run the test. Zapier brings back the three most recent short links of the connected account, so you build the rest on a real link instead of a guess.
- 03
Add a filter
Click the plus icon, add Filter, open Configure & test and set the field, the rule and the value. Use a text rule on a link, or the filter never lets anything through.
- 04
Add the action
Add the app that should receive the link and choose its action. Map the short link from the trigger into it, then test the step. Do not add an lc.cx action here, or the Zap loops.
- 05
Publish
Read what each test sent back, then click Publish. With the filter, this Zap is multi-step and needs a paid plan; without it, the free plan is enough.
lc.cx triggers in Zapier
1 event starts a Zap when something happens in lc.cx. Zapier checks for them at the interval your plan allows.
New Generated Shortlink
Polling triggerIn Zapier“Triggers when a new shortlink with lc.cx or a custom branded domain is generated.”
Starts a Zap each time a new short link is created on your lc.cx account, whether it uses the lc.cx domain or one of your branded domains. The Zap receives the new link, ready to be stored, shared or logged in another app.
lc.cx actions in Zapier
lc.cx gives you 1 action. For each one: what it does for you, when to reach for it, and what to watch out for.
Generates a lc.cx or Brandred Shortlink
ActionIn Zapier“Generates a lc.cx or branded shortlink.”
Shortens a URL handed over by an earlier step and returns the short version, on the lc.cx domain or on a branded domain of yours. The spelling in the name is the one Zapier shows, so search for it as is.
When an lc.cx Zap breaks
Zapier links no help article to lc.cx and no limit specific to the app is documented. What breaks is what breaks on any Zap, and one case is especially likely here.
Four situations explain most surprises. None of them shows a red error on day one, which is why they are worth knowing before you publish. For anything deeper, our Zapier troubleshooting page is the place to start.
A Zap that sets itself off
Start a Zap on New Generated Shortlink and generate a short link in the same Zap, and each new link fires it again, burning through your task count fast.The past is never picked up
A Zap only reacts to what happens after you switch it on. Short links created before are ignored, so moving them elsewhere is a separate job.A big batch gets held back
When a trigger suddenly returns a huge batch, after a bulk import or a migration, Zapier's flood protection can hold it back instead of running everything.The same link never runs twice
On a polling trigger like this one, Zapier remembers what it has already seen, so the same short link does not start the Zap a second time.
Need help automating lc.cx with Zapier?
A person reads every message.
