How do I connect a form, funnel or website I built somewhere else?
Create a form URL, paste one block into whatever built the page — Claude, Manus, Lovable, Webflow, WordPress — and submissions land here as leads.
Who this is for
Whoever owns the website or funnel — often the agency owner or their marketer. It's a copy-paste job; you do not need a developer and you do not need to understand webhooks.
Before you begin
- Know which page or form you want to connect.
- Have access to whatever built it (your AI tool, site builder, or form tool).
- Admin or manager access here, to create the form URL.
Steps
- Go to Agency Admin → Setup → Inbound Forms and click "New form URL".
- Name it something you'll recognise ("Mortgage quote — Facebook funnel"), optionally set a lead source, product, tags and who new leads get assigned to, then save.
- In the panel that appears under it, pick what you built the page with.
- Copy the block and paste it into that tool. For AI builders it's a written brief, not code — it survives being pasted into a tool that writes React, Vue or plain HTML.
- Submit your own form once. The status line on the panel turns green when it arrives.
You keep your funnel, your domain and your designer or AI. We only own the part that matters to us: the submission arriving as a real lead, matched to the right person, and able to start an automation.
Why we don't have a page builder
It's a deliberate product decision, not a gap. Almost everyone now has an AI build their pages, and a worse clone of somebody else's drag-and-drop builder would leave you married to our version of it. Building anywhere and connecting in one paste is a better answer to the same job — and it means your pages don't break if you ever leave.
What the AI brief actually says
It carries your form's exact field names, tells the AI explicitly NOT to build a backend or API route (these tools invent one otherwise), spells out the SMS consent checkbox, and describes what a good response looks like. That's the difference between a page that posts `fullName` with no consent flag — which quietly can't be texted — and one that works.
Nothing you send is thrown away
Fields we recognise (name, email, phone, city, state, zip, date of birth, notes and their common variants) map automatically. Anything else is kept on the contact as a custom field under whatever label you send — so use readable labels like "Mortgage Balance" rather than "mb2", and send everything the form collects.
Someone who's already in your CRM
The endpoint matches on phone first, then email. An existing contact is UPDATED rather than duplicated, and blank fields get filled in from what you sent. That's what makes re-quote forms, "send me info" boxes and surveys work properly instead of littering your database with copies of the same person.
How to check it worked
- Submit your own form once with your real phone number.
- The connector panel's status line turns green with the submission time — no reload needed.
- Find yourself in Leads and confirm the fields you sent are on the record.
Common mistakes
- Letting the AI build a backend or form service. The brief tells it not to; if you shortened the brief, it will. Post straight from the browser — the endpoint is CORS-enabled for exactly this.
- Hardcoding the consent checkbox to true. An unticked box that arrives as true is an illegal text message, not something you fix later. The generated code always reads the real checkbox.
- Sending consent as the string "on" from a no-code form tool. It has to be a true/false boolean, or nobody ends up textable.
- Sending neither a phone nor an email. The submission is rejected with a 400 — there'd be no way to know who it is or reach them.
- Copying the URL out of the iOS app by hand. Use the copy button; a hand-typed one from the app can carry the wrong origin.
Troubleshooting
| Form submits but nothing appears in the CRM. | The page is posting to a backend the AI invented rather than to the form URL. Search your generated code for the form URL. If it isn't there, re-paste the brief and tell the tool explicitly not to create an API route. |
|---|---|
| Leads arrive but never get texted. | sms_consent is arriving false, or as the string "on". Open the lead and check the consent field. Make sure the checkbox value is sent as a real boolean. |
| 400 error on submit. | No phone and no email in the payload. Make one of them required on the form. |
| The same person keeps appearing twice. | The phone is being sent in a format that doesn't match, or only email is sent and they're stored under a different one. Send both phone and email where you can — phone is matched first. |
Related
Where this lives in the app
This is documentation for Virtual Closer. Book a walkthrough or sign in.