ClickUp on your landing pages
When a home services shop or an agency runs on ClickUp, everything that matters is a task: it has an owner, a status and a notification on someone's phone. A paid lead that arrives as an email has none of those, and that's how good leads go cold.
LanderLab's webhook calls ClickUp's API to create a task in the List you choose on every submit. The task name tells you who and what at a glance, the description holds every answer, and Custom Fields carry the campaign, the click ID and the page. Your team picks it up like any other task, with no Zap in the middle.
A ClickUp task per lead, ready to work
A task beats an email for one reason: it has a state. Each lead arrives with a name you can scan, a description in Markdown with every answer on its own line, a priority, tags like paid-lead and an assignee. ClickUp's notifications, reminders and automations take it from there.
Because each landing page has its own webhook, each page can file its leads its own way: the emergency repair page into the dispatch List as urgent, the maintenance plan page into the sales List as normal, the careers page somewhere else entirely.
ClickUp Custom Fields for the numbers you report on
Answers you want to sort or filter by belong in Custom Fields: the campaign as short text, the landing page as a URL, the email in an Email field. Group the List by campaign and you see which ad set fills the board, and which fills it with leads nobody can reach.
Speed to lead for home services
An emergency AC or plumbing lead often goes to whichever company calls first. With the task created and assigned on submit, the dispatcher sees it without refreshing an inbox, and the job is on the schedule while the homeowner is still deciding who else to call.
Hidden fields keep the gclid and utm_campaign on each task, so at the end of the month you can tie booked jobs back to the Google Ads campaigns that produced them.
Route leads to the right List with Workflows
One page's webhook posts to one List. When leads need sorting first, LanderLab Workflows (beta) handle it: a Switch node on an answer such as team size or ZIP, an HTTP Request node per List, a Filter node to drop out-of-area jobs. The Runs view shows each lead's path and any step that failed.
