Landin Zapier integrationAutomate Landin with Zapier.
The Landin Zapier integration has 2 triggers, 0 actions and 0 searches. Both are instant: as soon as a lead is captured on one of your Landin landing pages, Zapier can pass it to your CRM, your mailing list or your team chat, with no wait and no export.
Verified Trustpilot reviews · AI, automation & growth agency
What the Landin Zapier integration actually does
Landin is where you put a landing page online without calling in a developer. On Zapier, it reports new leads and nothing else: one trigger for standard leads, one for Game Leads. Each fires the moment Landin records the lead, then any other app can take over. Zapier writes nothing back into Landin.
Three things people set up with these two triggers:
Contacts that reach sales instantly. New Lead sends every sign-up to your CRM while the visitor is still on the page, which is when a callback lands best.
A separate track for game leads. New Game Lead lets you treat leads from your Game capture apart: a different list, a different tag, a different follow-up.
A ping for the team. Either trigger can post a message to a chat channel, so someone sees the lead without opening Landin.
What Zapier does not do here: it cannot create or edit a page, update a lead, or find one that already exists. There are no actions and no searches for Landin. Each trigger also watches one landing and one lead capture at a time, picked when you set it up, so a site with several forms means several Zaps.
Still comparing platforms? See our n8n vs Zapier comparison and our Zapier alternatives page. On Zapier, Landin offers two triggers, both instant, and no action.
Zapier words in one minute
The editor's vocabulary, one plain line per word.
- Zap
- The automation you build: one starting event, then one or more steps that run each time that event happens.
- Trigger
- The event that starts the Zap. Landin has two: a new lead, and a new Game Lead, each tied to one landing page.
- Action
- What the Zap does next, in another app here: create a contact, add a row, post a message. Landin itself offers none.
- Task
- The unit Zapier bills. Each action that completes successfully is one task, counted against your plan's monthly allowance.
- Instant trigger
- A trigger the app reports itself, the moment the event happens. Both Landin triggers work this way, with no timer.
- Polling trigger
- The opposite: Zapier checks the app on a timer set by your plan. Most apps work like this, but Landin does not.
- Filter
- A step that lets the Zap continue only when the lead meets your condition. Adding one makes the Zap multi-step, so paid.
What a Landin Zap costs you
Short version: receiving the lead is free. Each thing you do with it costs one task.
- Premium appNo, works on the free plan
- Free plan100 tasks a month, two-step Zaps only
- Both triggersInstant, free, no polling delay
- Each successful action after them1 task
The trigger never consumes a task. Each action that succeeds afterwards counts as one, and a failed one does not. Landin is not a premium app, so the free plan works: 100 tasks a month and two-step Zaps. Both triggers are instant, so the 15-minute check of the free plan does not slow them down. A filter, a second action or a search, though, turns the Zap into a multi-step one, which needs a paid plan.
Connect your Landin account
- 01
Open the Apps page
In your Zapier account, open the Apps page and click + Add connection. You need a Landin account that already holds a landing page with a lead capture on it.
- 02
Find Landin and start the link
Type Landin in the search box of the dialog, pick it from the results, then click Add connection. A new browser tab opens on the Landin side to finish the link.
- 03
Sign in and grant access
Log in to Landin in that tab and allow Zapier to reach the account. The connection is saved once under Apps, and every Zap built on Landin reuses it from then on.
Your first Landin Zap, step by step
GoalCreate a CRM contact for each new lead, but only when the visitor left a phone number.
- 01
Build: pick the trigger
Create a Zap, choose Landin and New Lead, then fill in the title and pick the landing and the lead capture you want to follow.
- 02
Test with a real sign-up
Fill in your own form once, then test the trigger. Zapier brings back the three most recent items, so you map fields on a real lead.
- 03
Add the filter
From the plus icon, add Filter: field Phone, rule "exists". Leads without a number stop there, and the Zap becomes multi-step, which needs a paid plan.
- 04
Add the CRM action
Pick your CRM and its contact action, then map name, email and phone from the lead to the matching fields of the new contact.
- 05
Test, then publish
Test the action and check the new contact. When it is right, click Publish to switch the Zap on. Leads captured before that moment stay in Landin.
The Landin triggers
2 events start a Zap when something happens in Landin, and 2 of them are instant: the app calls Zapier straight away, whatever your plan.
New Game Lead
Instant triggerIn Zapier“Triggers when a new Game Lead is created.”
Fires each time Landin records a new Game Lead on the landing page and lead capture you pointed it at, and passes that lead's details to the next step. Zapier lists it apart from the standard lead trigger, so game leads can get their own route.
New Lead
Instant triggerIn Zapier“Triggers when a new lead is created.”
Each new lead captured on the chosen Landin page starts your Zap, with what the visitor entered ready to map into the next app.
When a Landin Zap breaks
Zapier publishes no help article and no specific limit for Landin. What goes wrong comes from how Zaps behave in general.
Most surprises trace back to the page or capture picked in the trigger, to leads from before the Zap, or to the app that follows Landin. If you get stuck, see our Zapier troubleshooting guide.
Earlier leads never arrive
A Zap only reacts to what happens after it is published. Leads Landin captured before that stay where they are; moving them is a separate job.The wrong capture is watched
Each trigger follows the landing and lead capture you picked. Leads from another form or another page simply never reach that Zap.A loop drains your tasks
If the Zap writes somewhere that creates a new Landin lead, it sets itself off again and again, and burns through the task count fast.A sudden flood is held back
If a campaign brings a huge burst of leads at once, Zapier's flood protection can hold the batch back before the next app gets anything.
Need help automating Landin with Zapier?
A person reads every message.



