- Home
- Resources
- Integrations
- LanderLab
LanderLab Zapier integrationAutomate LanderLab with Zapier.
The LanderLab Zapier integration has 1 trigger, 0 actions and 0 searches. It picks up every form submission on a landing page you built in LanderLab and passes the lead on to your CRM, your email tool or a spreadsheet, without exports.
Verified Trustpilot reviews · AI, automation & growth agency
What the LanderLab Zapier integration actually does
LanderLab is where marketers put together their campaign landing pages, no developer needed. On Zapier it offers one thing, a trigger called New Lead. Each time someone submits the form on a chosen page, Zapier collects that entry and can hand it to any other app. Nothing travels the other way.
Three results people build on New Lead:
A list that grows on its own. Every sign-up from a campaign page joins your email tool, tagged with the page it came from, ready for the welcome sequence.
Leads in the CRM, not in an inbox. Each submission becomes a contact or a deal, so sales can follow up from the tool they already live in.
A campaign log for the ads team. Each lead goes into a spreadsheet row with its page name, which is often enough to compare two landing pages side by side.
What Zapier does not do here: it cannot create, edit or publish a page in LanderLab, and it cannot look up a lead you already have. There are no actions and no searches. The trigger also watches one page at a time, so several pages mean several Zaps or one page per campaign.
Choosing between tools? See our Make vs Zapier comparison. If you would rather have the setup done for you, see our Zapier agency page.
Zapier words in one minute
The editor uses these words. One plain line each.
- 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. For LanderLab, it is a new form submission on the landing page you picked.
- Action
- What the Zap does next, in another app: add a subscriber, create a contact, add a row. LanderLab itself offers none.
- Task
- The unit Zapier bills. Each action that completes successfully is one task, counted against your plan's monthly allowance.
- Polling trigger
- A trigger Zapier checks on a timer, asking the app for new items. New Lead works this way, so the wait depends on your plan.
- Instant trigger
- The opposite: the app reports the event itself, right away. LanderLab's trigger is not one of these.
- Filter
- A step that lets the Zap carry on only when the lead meets your condition. Adding one makes the Zap multi-step, so paid.
What a LanderLab Zap costs you
Short version: catching the lead is free. Sending it somewhere costs one task.
- Premium appNo, works on the free plan
- Free plan100 tasks a month, two-step Zaps only
- New Lead triggerPolling, free to run
- Each successful action after it1 task
The trigger never consumes a task, and the regular checks Zapier runs on your page cost nothing either. Each action that succeeds afterwards counts as one task, and a failed one does not. LanderLab is not a premium app, so the free plan works: 100 tasks a month, two-step Zaps, and a check every 15 minutes. Paid plans check more often. A filter or a second action makes the Zap multi-step, which needs a paid plan.
Connect your LanderLab account
- 01
Open the Apps page
In your Zapier account, open the Apps page and click + Add connection. You need a LanderLab account that already holds at least one landing page with a form on it.
- 02
Find LanderLab and start the link
Type LanderLab in the search box of the dialog, pick it from the results, then click Add connection. A new browser tab opens on the LanderLab side to finish.
- 03
Sign in and grant access
Log in to LanderLab in that tab and allow Zapier to reach the account. The connection is saved once under Apps, and every Zap built on LanderLab reuses it afterwards.
Your first LanderLab Zap, step by step
GoalAdd every lead from a campaign page to your mailing list, skipping test submissions.
- 01
Build: pick the trigger and the page
Create a Zap, choose LanderLab and New Lead, then select the lander whose form you want to watch. One Zap watches one page.
- 02
Test with a real entry
Submit the form once yourself, 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, then set field, rule and value with a text rule on the email. This keeps tests out and makes the Zap multi-step, so paid.
- 04
Add the list action
Pick your email tool and its subscriber action, choose the list, then map the form fields to the matching ones and type the page name as a fixed value.
- 05
Test, then publish
Test the action and check the new subscriber. When it is right, click Publish to switch the Zap on. Leads collected before that point stay where they are.
The LanderLab trigger
1 event starts a Zap when something happens in LanderLab. Zapier checks for them at the interval your plan allows.
New Lead
Polling triggerIn Zapier“Triggers when a user submits/enters data from your form.”
Starts your Zap whenever someone fills in and sends the form on the landing page you selected, and hands over each value they typed. It covers a single page, picked when you set the trigger up, not your whole LanderLab account.
When a LanderLab Zap breaks
Zapier publishes no help article and no specific limit for LanderLab. What goes wrong comes from how Zaps behave in general.
Most surprises come from timing, from leads collected before the Zap existed, or from the page that was picked. When you are stuck, see our Zapier troubleshooting guide.
Old leads never come through
A Zap only reacts to what happens after it is published. Submissions from before that stay in LanderLab; moving them is a separate job.The lead arrives later than expected
New Lead is a polling trigger. On the free plan Zapier checks every 15 minutes, so a lead can wait that long before your Zap runs.A launch spike gets held back
If a campaign brings a huge batch of submissions at once, Zapier's flood protection can hold the trigger back before the next app receives anything.Duplicates come from a second Zap
Zapier remembers which leads a polling trigger has already seen, so one entry does not run twice. Two Zaps on the same page would, though.
Need help automating LanderLab with Zapier?
A person reads every message.



