Forms
A form that files itself
A block-based builder. A submission creates or updates a person and can trigger a workflow.
A form is a page you publish, a link you share or embed, and a submission that becomes a record. A demo request, a waitlist, a survey, a partner inquiry. The submission is a workflow trigger, so what happens next is yours to decide.
Building
- Add field blocks: text, email, phone, select, multi-select, date, file, long text.
- Map a field to a record field, built-in or custom, so the submission fills the person in.
- Arrange, style, add a headline and a thank-you.
- Publish to a link. Embed it. Unpublish any time.
Submissions
Submissions collect on the form. The submitter becomes, or updates, a person, matched by email. Their sessions from website tracking attach. The submission itself is on their record, so the answers are there when you call.
What a submission can do
- Notify
- Email someone, post to Slack, or both, from Forms settings.
- Create a deal
- A demo request opens a deal in Discovery with the person on it.
- Enroll
- A waitlist signup goes into the nurture sequence.
- Route
- Assign an owner by territory, tag by source, set a status.
Around forms
The parts of the workspace this one works with.
Forms settings
Where a submission is announced, and the defaults a new form starts with.
A submission can email someone, post to a Slack channel, or both. Set it once here and every new form inherits it. A form can still override it for itself.
Workflows
Something happens, a condition decides, the workspace acts. Build it on a canvas or ask the agent to.
A workflow starts from an event, not a schedule. A reply arrives, a deal changes stage, a form is submitted, a meeting ends. Then a condition decides, and the workspace does the thing you would have done by hand.
Website tracking
One snippet on your site. Then sessions, pages, identified visitors and intent, on the records they belong to.
Install the snippet and the Website visitors page fills with who is on your site and what they looked at. Identify a visitor once and every past session attaches to their record.
Questions
Can I embed it on my site?+
Yes. A script embed, or an iframe, or just the link.
Spam?+
Submissions are rate-limited and checked. A suspicious one is held rather than made into a person.
Can one form notify a different channel?+
Yes. Each form can override the workspace default in its own settings.
Can I test a workflow?+
Run it against a record by hand from the builder and read the run.
What if an action fails?+
The run shows the error. Fix the node and retry the run.
Is there a limit on runs?+
No. Runs are logged and kept.
Does it slow the site down?+
The script is small and loads after the page. Events are batched.
Is this a cookie banner problem?+
It sets a first-party identifier. Whether your site needs consent for that depends on where your visitors are; the snippet can be loaded after consent.
Try forms on your own data
Connect your email, then open a person. Most of the product shows up on that one page once the mail is in.
More in Automate
Sequences, workflows, forms and an assistant that does the repetitive parts.
A reply arrives, a deal changes stage, a form is submitted. A condition decides, and the workspace does what you would have done by hand.
It reads what you can read and does what you can do. With your permissions, in your workspace, and nowhere else.
Describe the recurring ask once, then it is one click.
Every Monday at eight, summarise last week’s pipeline and post it.