Forms collect structured information with a fixed set of fields (and optional show/hide rules). They are usually better than asking for each field in separate chat messages.Forms are part of the app blueprint. People can open them from chat, the portal, Preview, or navigation. Submissions can save data through tools and can kick off automations.Field types such as email, phone, URL, date, datetime, and UUID are checked for a valid format before submit (not only whether the field is filled in). Required fields and number min/max still apply as usual. When a form submits straight to a tool, GenieForge can infer required flags and those format field types from the tool’s parameters.
For guests who should fill a form without signing in (in-store QR, kiosk, landing page), open the form under App Blueprint → Forms, then use Public intake to publish it to a project. You get a shareable link and a downloadable QR code. Brand colors live under App Settings (logo + public brand colors).Opening the link starts a short-lived form session (claim, then fill and submit once). Guests who go back in the browser need to open the link or scan the QR again.To show that QR on a portal or Preview page (for example a front-desk screen), ask the builder agent to add an intake QR block bound to the form. The page loads the live published link for the current project, so rotating the token updates the QR without editing hardcoded URLs.To attribute walk-ins to whoever is signed in (each sales associate’s own QR), ask for an intake QR block with context bound to the current user (for example associate id). Publish the form once; each associate who opens that portal page gets a QR that tags submissions as theirs. You do not create a separate public link per person.Public intake is not available on HIPAA-enabled apps. The form must submit to a dedicated code tool that owns safe ingestion for that app (for example duplicate checks before creating a client), not directly to a data model. File uploads, SQL-powered dropdowns, and background jobs are not supported on public intake. Do not host interactive registration HTML as a public app file: that path is for static assets only.Find them under App Blueprint → Forms.
