A new field type lets respondents search and pick an existing Record Type row instead of typing it in. The chosen record links the submission to that row for downstream routing, record mapping, and exports.
When a respondent needs to pick from an existing list, typing a free-text answer creates problems downstream. You get inconsistent spellings, values that don’t match your records, and manual cleanup before anything can route correctly.
Record lookup fields fix this at the source.
Add a record lookup field to any Intake Bot and point it at a Record Type. Respondents see a search box (for large datasets) or a list of selectable options (for smaller ones), sorted A to Z. Whatever they pick is stored as a reference to the actual record row, not a copied string.
That reference travels through the rest of the submission: record mapping can resolve the linked row automatically, process boards associate the card with the right entity, and exports include the resolved values rather than a raw text answer.
For Record Types with many rows, the lookup field loads matches on demand as the respondent types. No pagination, no loading the full list upfront. Builders define the field once and it scales with the record set.
Available on all plans.
A new field type lets respondents search and pick an existing Record Type row (a program, location, product, or any record) instead of typing it. Large datasets switch to a search as you type picker that loads matches on demand and sorts them A to Z; smaller sets render as selectable options. The chosen record links the submission to that row, so record mapping, process boards, and exports resolve the real entity. Available on every plan.
