Filter the junk. Route the rest. See where every lead went.
Draw the logic on a canvas and every new lead runs through it: Filter, If, Switch and Delay, then out to your buyers, your CRM, a sheet or Meta. Every run is logged, down to the step that failed.
Free forever plan. No card required.
4.9
4.6
The Runs view of a published workflow, Roofing leads by state: a Lead trigger on two pages, a Filter for qualified homeowners, a Meta CAPI Lead event, then a Switch on the state field that sends Texas to LeadsPedia, Florida to LeadProsper and every other state to Google Sheets. New runs come in beside the canvas; pick one to see its path.
Runs
Today: 214 runs, 171 sent40 stopped3 failed
Newest first
After the submit
Stop moving leads by hand.
A workflow filters each lead, posts it to the right buyer and logs every run. No CSV, no copy and paste.
The old way
- “Who's pasting this morning's CSV into the portal?”
- “The buyer's paying for junk leads again.”
- “We're rebuilding the same setup on every page.”
- “The buyer says they never got it. Did they?”
The LanderLab way
- “Each lead posts to LeadProsper as it comes in.”
- “The Filter stops junk before anyone pays for it.”
- “One trigger listens to several landing pages at once.”
- “Runs shows the lead's path and the step that failed.”
Nodes
Turn your buyers' rules into nodes on a canvas.
Click a node and pick a field from your page, an operator and a value. Workflows is in beta, so the nodes may still change.
Trigger
Lead
Fires on every new lead from the pages you connect. One trigger can listen to several landing pages, and a toggle pauses a page without removing it.
Internal
Filter
Pass or stop. A lead that fails your conditions ends its run here and stays in your leads table. Eight operators, AND or OR inside a group, and groups when you need both.
Internal
If
Two outcomes. Leads that match go down the Yes branch, the rest down No, and each branch gets steps of its own.
Internal
Switch
Many outcomes. Cases are checked top to bottom, a lead takes the first one it matches, and Default catches the rest.
Internal
Delay
Holds the steps after it for seconds, minutes, hours or days. It doesn't touch the lead, so chain a few to space out a follow-up.
Action
HTTP Request
For a buyer or a tool with an API but no native action: post the lead to your own endpoint, in the same run as everything else.
Action
Native actions
Pick the account and where the lead lands, then the fields to send. In Klaviyo that's a list and a field map, LanderLab's own fields like the landing page URL and the variant ID included.
Recipes
Six workflows worth building first.
Route by state
A Switch on the state field: Texas to one buyer in LeadsPedia, Florida to another in LeadProsper, the rest to a sheet.
Homeowners to the CRM
An If node on the quiz answer sends homeowners to HubSpot and renters to a Google Sheets tab.
Only real leads to Meta
Filter out test and junk entries, then send the Lead event to Meta CAPI so the ad learns from leads worth paying for.
Follow up tomorrow
A Delay of one day, then the lead goes to your Klaviyo list for the follow-up email.
Only good leads to the tracker
A ClickFlare action after the Filter, so the tracker only hears about leads that passed.
Your own endpoint
HTTP Request posts the lead to any API, in the same run as the native actions.
Actions
Send the lead to the tool that works it.
Native actions for lead distribution, CRMs, email, Meta CAPI and ClickFlare, plus an HTTP Request node for anything with an API.
2M+
Leads collected monthly
750M+
Visits served monthly
3,500+
Marketers
4.9/5
Rated on G2
Build one
Your first workflow in three steps.
Start01 with the Lead trigger, add02 your logic and actions, then publish03 it and watch every run.
- 01
Add the Lead trigger
Create a workflow, add the Lead trigger and connect the landing pages whose leads should run through it.
- 02
Add logic and actions
Drop in Filter, If, Switch or Delay, then the actions. A yellow warning marks any node that still needs setting up.
- 03
Publish and watch Runs
Every new lead from the connected pages now runs through it. Check Runs to see where each one landed.
Before you start
Is Workflows ready for live traffic?
Yes. A published workflow runs on every new lead from its connected pages, and Runs shows each result, failed steps included. Workflows is in beta, so nodes and features may still change: build the basic trigger-to-action flow first, check Runs, then add branches.
How many destinations can I connect?
Lead and webhook integrations scale with the plan: 1 on Free, 5 on Launch, 50 on Grow, 250 on Scale and unlimited on Enterprise. Leads themselves are unlimited on every plan.
What happens when a buyer's endpoint is down?
The run is marked as failed at that step in Runs, so you can see which leads didn't arrive and fix the node. The lead itself stays in your leads table, unless you turned on Lead Compliance Delivery for that page.
Does a lead that fails a Filter disappear?
No. The Filter only stops the workflow for that lead, and the lead stays in your leads table. If you want to act on the leads that fail, use If instead, which gives them a No branch of their own.
Do I need to write code?
No. You drag nodes onto a canvas and pick fields, operators and values from dropdowns. HTTP Request is there for a tool that has an API but no native action.
Who helps me set it up?
Support is by email on Free and Launch, chat and email on Grow, Telegram and chat on Scale, and Slack and video call on Enterprise. Scale and Enterprise also come with a dedicated success manager.
Build the routing once. Let every lead run through it.
Start free, publish a page, and send its leads to the tools and buyers that pay for them.