A self-serve intake control room inside Integrations. Connected accounts list every page with its lead-sync state and its lead forms. Each lead source carries its endpoint URL, its secret, a field-mapping editor translating provider fields to card fields or custom answers, a test-fire button, and a log of recent deliveries with verdicts — created, merged, duplicate, test, rejected or error.
Also called: website form leads · facebook lead ads · zapier · webhook · where do my leads come from
- 1Facebook and Google connect through OAuth in a popup over the page, so closing it aborts cleanly.
- 2Field mapping offers explicit targets — full name, first, last, email, phone, street, city, state, ZIP, county, budget, project value, custom answer, or ignore.
- 3Every delivery, including failures, is recorded and rendered with a coloured verdict.
- 4Setup guides sit behind an ⓘ on each provider card.
The design intent is stated as 'a builder must be able to do ALL of this alone — copy a URL into their form tool, map the fields by the names they recognize, fire a test, watch it land.' The reason the delivery log exists is in the same comment: 'a silently dropped lead is a $30k–$250k hole.' The guides are too, so a builder can follow a picture rather than a support call.
- Lead intake required developer setup.
- Dropped or rejected leads were invisible.
- Provider field names did not match the platform's fields.
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →