Make on your landing pages
Make is where lead routing gets visual: a webhook on the left, a Router in the middle, a branch per buyer, sheet or channel on the right. Connect it to LanderLab and every lead from a landing page or quiz funnel starts your scenario, with every field the visitor filled in and LanderLab's own fields beside them.
There's no Make app to install, and you don't need one: a Make custom webhook gives your scenario an address, and the page's Webhook integration posts each lead to it. That works on any Make plan, and the same address can take leads from as many pages as you like.
Start a Make scenario on every lead
Each lead arrives in your scenario as JSON. The keys are whatever you name them, so the scenario works with first_name and email rather than the form's labels, and LanderLab's own fields, such as the page URL, the visitor IP and the submission time, come along for filtering, routing and compliance records.
In Make every one of those fields is a variable the next modules can use, the answers, the UTMs and the variant included, so routing and formatting work from the lead's real data.
One Make scenario for many pages
The same Make webhook URL can go on several landing pages. Add a Router with filters on the page URL or a quiz answer, and each lead takes its own path: one page's leads to a buyer, another's to a sheet and a Slack channel.
For a lead gen operator, that's the whole offer in one picture. When a buyer caps out or a new state opens, you change a filter on the canvas, not five separate automations.
Any API, even without a Make app
When the destination has no app in Make, the HTTP module can post the lead to its API directly. If a delivery fails, Make's History tab and LanderLab's delivery logs show the request that was sent and the response that came back, which is what you need when a buyer says a lead never arrived.
Make or LanderLab Workflows (beta)?
LanderLab's Workflows (beta) covers a lot of routing on its own: a Lead trigger on one or more pages, Filter, If, Switch and Delay nodes, and actions for Google Sheets, HubSpot, Klaviyo, GoHighLevel, LeadProsper, Meta CAPI and an HTTP Request node. If your routing fits there, it's one less tool and one less bill.
Make earns its place when the scenario reaches beyond that: dozens of apps, data transformations, lookups in other systems, or a team that already runs its operations in Make.
