Forms

The Human Interaction app's form actions and triggers collect input from people. Used for approvals, data correction, intake, file collection, and full multi-screen form apps.

Claude designs the form — fields, validation, theming, dynamic content, conditional flow — and adds it to your automation as either a trigger or a mid-flow action.

Two modes

• Form trigger — the automation starts when a form is submitted. The form is the trigger; submitted values are the trigger's output fields. Use when the form is the entry point: customer intake, contact requests, internal request forms.
• Form action (mid-flow) — paired "Create a Form" + "Await Form Submission" actions pause the automation, present the form, and resume with the submitted values once the user submits. Use when the form sits inside a larger flow: approvals, data correction, follow-up questions.

Capabilities

• Field types — single-line text, multi-line text, checkbox, check-all, radio group, dropdown, multi-select, file upload, multi-line repeating groups (arrays), hidden inputs, text labels, JavaScript blocks.
• Validation — per-field required flags enforced before submit.
• Theming — light and dark mode hex colors, highlight color, corner radius, custom button text.
• Dynamic content — dropdown and multi-select items populated at runtime from prior automation output (not just hard-coded choices).
• Pre-population and hidden fields — any field can be pre-filled or hidden via URL query parameters, no special element type needed.
• Embedding — render standalone at the form's URL, or inline inside another page.
• Submit behaviors — show a confirmation message, close the dialog, redirect to a URL, or display the next form in a sequence.

Form apps

A form app is a sophisticated multi-screen flow built from chained forms — not a one-shot data grab. Each screen is its own form, branched based on prior answers, with shared state carried between screens.

• Each screen flows directly into the next without a page reload.
• The next screen is chosen based on what the user just answered, so different users can see different paths.
• A progress or "working on it" message keeps the user oriented while the next screen prepares.
• Earlier answers — plus anything the automation looks up or calculates — stay available on later screens.
• The last screen ends with a confirmation message, a thank-you screen, or a redirect to your own URL.

Combining patterns

• Moderation with a form — pair with Human Moderation for rich approval flows: a moderation queue link opens a form for the reviewer to fill out before approve/deny.
• File collection — a fileupload element captures attachments alongside field data; downstream actions process the uploaded file.