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. Ask for a name, a way to reach them, add a Submit button, and embed it. Everything past that — logic, styling, automation — is opt-in.

Open Forms and click New form. You land straight in the editor with three tabs along the top — Editor, Submissions, and Settings. A new form opens blank with an editable title in the toolbar — click it to name your form (this is the name you’ll see in the Forms list and pick from a workflow trigger).

Flip the Preview toggle any time to see the form exactly as a customer would — it drops you onto the Editor tab and shows the live result. Editing resumes the moment you toggle it back off.

Open Add Element and drag pieces onto the canvas. They’re grouped exactly as the panel groups them:

• Input fields — Text, Text Area, Number, Single Select, Multi Select. Each can be marked required.
• Date & time — Date, Time, or a combined Date & Time picker.
• Content & layout — a Text block, Image, Divider, a Collapsible Section to group questions, and the Button.

This is the part that makes a form a lead capture tool, not just a survey. The top group in the palette is Contact Fields: standard fields (Full Name, First Name, Last Name, Email, Phone) and your contact Custom Fields. Answers to these are written straight onto the contact Exabloom creates.

The canvas is built from rows. Every element you add sits in its own row by default, stacked top to bottom. Drop a second element beside an existing one and they share a row as columns, splitting the width evenly — that’s how you put First Name and Last Name side by side.

• Reorder by dragging — grab a row’s handle and move it up or down the form.
• Delete an element by hovering its row and clicking the trash — there’s no delete button inside the edit panel, so removal lives on the row itself.
• Group with a Collapsible Section — drag fields into one to fold a chunk of the form (say, optional extra questions) behind a heading. The section has its own heading and its own Delete.

Click any element on the canvas to open its edit panel on the right. Whatever the field type, the panel is organised the same way, in three collapsible groups:

• 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 — see below).
• Label & Content — toggle Show label, set the Display text (the question), and the Placeholder. Single and Multi Select fields add an Options list where you add, rename, reorder, and delete each choice; date fields add range options like disabling past dates.
• Advanced — the field’s Query key (covered next).

Hit Styling at the bottom of the canvas to open the Form Styling drawer. Styling here is form-wide — set it once and every field follows — across four tabs:

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

Before a form will save, Exabloom checks it has the basics to actually reach a person. If something’s missing you’ll see a Complete Your Form prompt listing what to add:

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:

A form goes live by being embedded. Click Embed in the toolbar and pick a method:

• JavaScript Embed (recommended) — a small <script> that calls ExabloomForm.init. It inherits your site’s responsive layout and styling for the most seamless fit.
• iFrame Embed — drops the form in an isolated frame. Fully shielded from your page’s CSS and dead simple to paste anywhere.

Every submission shows up under the Submissions tab as a row — submitted time plus a column for each input field. Page through them and Export the lot for a spreadsheet whenever you need it.

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 can be combined with and / or groups, and each field type brings its own operators (text contains, number greater than, date before, and so on). Add as many rules as you need.

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, and the workflow runs on every submission:

Inside the workflow, the submission shows up as a Form Submission entity — every field you collected is available as a placeholder (e.g. form_submission.data.programme) to drop into messages, use in If/Else branches, or filter the trigger on. The new or matched contact is available too.

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. Email-only forms create a fresh contact every time — add a phone field if you care about merging.
• Custom fields are set on create only. A phone-matched repeat submission won’t overwrite existing custom fields — update those in a workflow.
• Embed to go live. Saving a form doesn’t publish it — it’s live once the JavaScript or iFrame snippet is on your site.
• No contact field = no workflow. The Form Submitted trigger only fires when a contact could be identified.
• Nothing autosaves. Press Save often — leaving the editor with unsaved edits loses them, and only a saved form is the one your site serves.
• Query keys are the contract. Keep them unique and stable — renaming a key after a form is live breaks workflows and export columns that point at the old name.