Lookup & Related-Record Fields on Web Forms

What they're for#

A lookup field lets a visitor choose an existing record to link their submission to — for example picking their company, a product they're asking about, or a branch/location. The new record is then connected to the one they chose, with no manual matching afterwards. There are two kinds: a single Lookup and a Multi-select lookup (choose several).

Add a lookup field#

Lookup fields come from your target module. If the module has a lookup field, it appears in the builder's Available Fields panel — drag it onto the canvas or click +. (See Adding & Configuring Web Form Fields.)

What the visitor sees#

A searchable dropdown. The visitor types to search and matching records appear (the list narrows as they type, showing up to 25 at a time). They pick one from the results.
Multi-select lookup works the same way but lets them choose several records, each shown as a removable chip.
Standard prompts: "Select…", "Search…", and "No results found." when nothing matches.

The choices are pulled live from the related module's records, so the visitor always sees current data. On submit, the chosen record is linked to the new record automatically.

Good to know#

The lookup must know which module it points at — that's set on the field's definition on the module. If a lookup field isn't configured with a related module, the control appears disabled with "Options unavailable."
On the form you control the usual bits — label, placeholder, help text, and required — see Configuring a field.

💡

Lookups are perfect for tying a lead to the right context from the very first touch — let a visitor pick their company or the product they're interested in, and every downstream view, report, and workflow already has the connection.

Was this article helpful?

Ready to implement this?

OpenAI Engage and apply what you just learned to your own workspace.

Open AI Engage CRM