A form that turns itself into a lead

Build a form once with order tables and computed fields, publish it as a link or an embed, and every response lands in your CRM. The same engine runs NPS and CSAT surveys with branching logic.

Included on every plan, free included

Start free See pricing

Why this exists

A public form is easy to build and hard to turn into a real lead without somebody retyping it.
An order form that trusts whatever price the browser sends is an order form waiting to be edited in the browser’s dev tools.
A survey with no branching asks a detractor the same follow-up question it asks a promoter.

What it does

Build with real field types

Short text, paragraph, email, phone, number, URL, name, dropdown, radio, checkboxes, a single checkbox, line items with an order table, and read-only calculation fields.

Publish anywhere

A published form gets its own public page and a copy-paste iframe embed. Drafts stay private. No login is needed to respond.

Fill your pipeline by itself

Every response is stored under the form and automatically creates a Lead (source "form:<name>"). A submission also fires a "form.submitted" event for Automations.

Trust the totals

Line-item and calculation fields update live as someone types, and prices for preset or catalogue items are re-checked on the server at submit, so a tampered price is ignored.

Ask CSAT and NPS with a hosted page

Surveys share the same engine: NPS, CSAT, star rating, choice and text questions, with logic rules that jump respondents forward based on their answer, and a live rollup of scores and distributions.

See where a response actually came from

Every submission carries a "Came from" column, and if your site posts channel, campaign, source or device details alongside the answers, those show up in the table and the analytics tab too.

What it does not do

The part you would otherwise find out in week three. If one of these is central to how you work, raise it before you buy rather than after.

Survey logic rules only jump forward. There is no branching backward and no loop.
A survey response becomes a CRM lead only if you switch that setting on and the survey collects an email; a form response always becomes a lead.
The repeating grid’s duplicate check applies to one column you choose, and only while you leave it switched on.
The public page and the submit path are rate-limited per visitor, per form and across the whole platform, so an unusually high burst of legitimate traffic can be throttled along with abuse.

Questions, answered

Do I need to write code to put a form on my site?+

No. A published form gives you a copy-paste iframe embed, or a public link you can send directly. Either way nobody needs to sign in to respond.

Can someone fake a lower price in an order field?+

No. Prices for preset items or your live product catalogue are re-checked on the server the moment someone submits, so a value edited in the browser is ignored rather than trusted.

Do surveys create leads the same way forms do?+

Only if you turn that on and the survey actually collects an email. A form always creates a lead from its response; a survey does not, by default.

What happens to answers for a question I later removed?+

They stay visible on the responses that were already submitted. Removing a question from the form only affects submissions from that point on.

The full product documentation for this module is at /docs/forms.

Try it on your own data

Free for up to 5 seats, no card required. Every module is in the same workspace, so nothing needs connecting to anything.

Start free Compare with others