Web forms
Build a form once, drop it on any page, watch contacts land in your pipeline. No Zapier. No middleware. No monthly fee.
Before you start
- Decide what data you actually need. Ask for the minimum. Every extra field halves your conversion.
- Know where the form will live. Your own site, a landing page, an email footer.
- Know who should get the notification email when someone submits.
Step 1: Create the form
- Go to Web Forms in the left sidebar.
- Click New form. You will land in the editor on the Build tab.
- Give the form a name at the top - this is only for you, not visible to visitors.
- Add fields from the left panel. Short text, long text, email, phone, dropdown, radio, checkbox, consent tick, hidden fields and section headers are all available.
- Click any field to change its label, placeholder, help text, required flag, and how it maps onto a contact record.
- Drag the handles to reorder. Delete any field with the little cross on the right.
Step 2: Wire the settings
- Open the Settings tab.
- Set the Thank-you message visitors see after submitting. Or set a Redirect URL if you would rather send them to a specific page.
- Add a Notification email address (or a comma-separated list) so you find out the moment someone submits.
- Add any Tags to apply - useful for pipeline automation and reporting later.
- Choose the Pipeline stage new leads should drop into. Default is New lead.
- Leave the honeypot on. Add a Cloudflare Turnstile key if you are being hammered by spam.
Step 3: Publish
Click the Publish button in the top right. Only published forms accept submissions. Drafts return a friendly "form not available" page.
Step 4: Share the form
Open the Share tab. Three ways to use the form:
- Hosted URL - the form on its own centred page. Best for email footers and quick shares.
- Iframe embed - drop the snippet into any page's HTML. The form appears in a frame at whatever height you set.
- JavaScript embed - the best option. The form renders directly in the host page using an isolated shadow root, so nothing on the parent page can style it accidentally.
Step 5: Verify with a test submission
- Click Preview at the top of the editor. This opens the hosted URL in a new tab.
- Fill the form as a real visitor would.
- Return to the CRM and open Submissions on the form's card.
- You should see your test entry at the top, with the contact linked.
- Delete the test entry to keep your data clean.
GDPR and consent
Every form ships with a Consent tick field pre-configured. Edit its label to spell out what the visitor is consenting to. If you need double opt-in, tick Send verification email in the form settings (available in a future release). All submissions store the IP address for spam analysis and are automatically hashed after 30 days.
Troubleshooting
- Submissions never arrive - check the form is Published. Drafts silently refuse submissions.
- Notification emails missing - check the address is set in Settings, and that your SMTP is configured under Settings > Integrations.
- Duplicate contacts - shouldn't happen. The form uses email OR phone-tail deduplication. If you see duplicates, check the form actually collects one of those fields.
- Spam through the honeypot - turn on Cloudflare Turnstile. It is free and works in seconds.