Intake forms

Collect structured answers at a public link, and route every submission with a flow.

What you see

Flows → Forms lists every form in the workspace with its public link, field count and submission count. Open one and you get the builder:

  • Fields — add, reorder and remove questions. Each has a label, a type (text, long text, email, number, dropdown, checkbox), an optional required flag, and an answer key — the name the answer is stored under, derived from the label unless you set it.
  • A dropdown's choices are edited inline; they are kept only for that type, so switching a field to text does not leave a stray list behind.
  • Live / paused — a paused form returns 404 at its public link while keeping everything it already collected.
  • Slug — the last part of the public link. It is unique across all of CoreX (the URL is /forms/{slug} with no workspace segment), so a name already taken gets a short suffix rather than failing the save.
  • Submissions — the answers so far, one column per field, below the builder.

Use it

  • Share the link from an email, your docs, or inside your product. No login is required to fill it in.
  • Every submission fires the form.submitted trigger, so a flow can act on it — email the submitter, notify a channel, create a task, or enrol them in a sequence. The submitted email is surfaced to the flow directly, so those actions resolve a recipient even for someone with no contact record yet.
  • If the email matches a known contact, the submission is linked to that customer automatically.

Why it matters

Structured intake beats free-text email for onboarding and requests — the answers land on the customer record and in an automation, instead of in an inbox.