Capture leads with Forms

A form lives in Forms in the sidebar. You build it by dragging elements onto a canvas, then you put it in front of customers by embedding it on your website. When someone fills it in, Exabloom turns that submission into a contact and stores the answers - so nothing lands in an inbox you forget to check.

Here’s the key idea: a useful form is tiny. A brand-new form already comes with a heading, a name, an email, a phone number and a Submit button. Rename it, save it, embed it - that is a working lead capture. Everything past that - your own questions, styling, logic, automation - is opt-in.

The palette isn’t always on screen. Click Add element, top left of the canvas, and the Add Element panel slides out. Its six groups start collapsed - click a group to open it, then drag an item onto the form.

When you drop an element, the edit panel opens on the right at once so you can name it. Every group, as the panel lists it:

• Input fields - Text Input, Text Area, Number Input, Single Select, Multi Select and the Consent Checkbox (a tick-box with your own wording, such as “I agree to the terms and conditions”; it’s required by default).
• Date & time - Date Picker, Time Picker, or a combined Date & Time Picker.
• Content - a Text Block, an Image and a Divider. Layout holds the Collapsible Section. Actions holds the Submit Button.

This is the part that makes a form a lead capture tool, not just a survey. The first group in the panel is Contact Fields: Standard Fields (Full Name, First Name, Last Name, Email, Phone) and your contact Custom Fields, shown with a count. Answers to these are written onto the contact Exabloom creates.

The canvas is a single column: every element sits in its own row, stacked top to bottom. Full Name is the one element that puts two boxes side by side (First Name and Last Name).

• Reorder by dragging a row up or down the form.
• Delete an element by selecting its row and clicking the bin in the little toolbar beside it. There’s no delete button inside the edit panel.
• Group with a Collapsible Section (Layout group). Drop one in, then drag fields into it: an empty one reads “Drag elements to this container”. Select it to give it a heading; it has its own gear and bin too.

Click any element on the canvas to open its edit panel on the right. The header names the element type, and the panel is organised in collapsible groups - General is open, the rest start closed.

• General - Is required, plus Is initially hidden and Is initially disabled (start a field tucked away or greyed out, then reveal or enable it with conditional logic). A Single Select also has Display as - Dropdown or Radio buttons.
• Label & Content - Show label, the Display text (the question) and the Placeholder. Single and Multi Select fields add an Options group where you add, rename, reorder and delete each choice; date fields add range options.
• Advanced - the field’s Query key.

Click Styling, top right of the canvas, to open the Form Styling drawer. Styling here is form-wide - set it once and every field follows. It has four groups, all closed until you click them.

• Background - the colour and opacity behind the form.
• Form Container - the form’s Width and its border shadow (colour, opacity, blur radius).
• Input Fields - label text, input text, outline and background colours, applied to every input at once.
• Custom CSS - your own rules when you need pixel control the groups don’t cover.

Press Save, top right. A “Successfully saved form” toast confirms it. Saving does two things: it stores your edits and it publishes the form’s public config, so the form at its public link (and anywhere you’ve embedded it) updates straight away.

Before it saves, the editor checks the form has the basics to reach a person. If it doesn’t, you’ll see a Complete Your Form prompt and nothing is saved:

When someone hits Submit, Exabloom reads the contact fields off the form and decides whether this is a new person or one you already know - by phone number:

Every saved form has a public link (Preview in the ⋮ menu on the Forms list opens it). To show it on your own site, embed it.

Every submission shows up under the Submissions tab as a row - submitted time, then a column for each input field (headed with the field’s label). A Full Name shows as first and last name together, and a Consent Checkbox shows Yes or No. The Submissions count on the Forms list is the same number.

Pages hold 20, 50 or 100 rows (Rows per page, bottom right). The CSV has all submitted fields and timestamps.

Want a copy of each submission in someone’s inbox? Open the Settings tab, find Email Notifications and pick Recipients - workspace teammates, up to 20. Each submission then emails them a “New submission: your form’s title” message.

Everything so far is the common case. From here on is the advanced tier - skip it unless a plain form isn’t enough. In the Settings tab, Conditional Actions let the form react to what people type. Each rule is when this condition is true, do these actions.

The actions you can take on a field or section are:

Conditions combine with and / or, and each field type brings its own operators (text contains, number greater than, date before, single select is any of…). Drag the grip at a card’s left to reorder rules. Pair Is initially hidden on a field with a Show Element rule to reveal it on demand.

A form on its own just stores submissions. To act on a lead the instant they submit - auto-reply, tag, route, start a nurture - pair it with a workflow. Add a Form Submitted trigger, choose this form in its Form list, and the workflow runs on every submission. Building the workflow itself is covered in Automate with workflows.

Inside the workflow, the submission is available as a Form Submission - each answer under its Query key (e.g. form_submission.data.programme) to drop into messages or If/Else branches. The new or matched contact is available too. Phone and Full Name answers arrive as small groups (country code and number; first and last name) rather than one string.

Four common forms, each built from the pieces above. Adapt, don’t copy exactly.

• A form makes a contact, not a lead. Use a workflow on submit if you want it tracked in a pipeline.
• Only contact fields touch the contact. Plain inputs live in the submission (and are visible to workflows) but don’t change the contact record by themselves.
• De-duplication is by phone. A form with no phone field creates a fresh contact every time - keep the phone field if you care about merging.
• A matched contact isn’t updated. Answers are only written onto a contact when it’s first created; a phone-matched repeat only adds a submission.
• Save publishes. Saving updates the public form straight away; embedding puts it on your site. Preview shows the saved version, so save before you check.
• Nothing autosaves. Press Save often - Back returns to the list without asking, and unsaved edits are lost.
• Query keys are the contract. Keep them unique and stable - renaming a key after a form is live breaks workflows that point at the old name.
• Hidden means initially hidden. A field marked Is initially hidden stays hidden unless a Conditional Action shows it - don’t hide a field you want answered.