Name the workflow
Start blank when the task is genuinely new, or choose a relevant template when its decision and field logic match.
Build a focused form from a blank canvas or a workflow template, test it at phone width, publish one clean link, and export responses when your team is ready.
Build, test, publish, and review. The steps stay visible and reversible.
Start blank when the task is genuinely new, or choose a relevant template when its decision and field logic match.
Rewrite labels, remove unused fields, and add instructions where a format could be unclear.
Try errors, keyboard use, a narrow screen, and the response export with sample data. Use a confirmation message that names the next step before sharing the form.
Choose from short text, email, phone, longer answers, choices, dates, and rating fields. Required status and choice options remain explicit, so the published form has visible labels and predictable controls.
After publishing, the builder creates one hosted form link. Responses enter the owner's workspace, where they can be reviewed and exported as CSV. Spreadsheet export values are protected against common formula-injection prefixes. Follow the CSV export safety checks before opening response files in spreadsheet software.
Begin with the action that follows submission. A contact request needs a reply owner. An event form needs a capacity and confirmation process. A survey needs an analysis plan. Remove any question that does not change routing, a decision, or the next action.
Define assignment, status, escalation, and retention with a form response workflow before inviting real submissions.
The fastest useful starting point is a workflow-specific template with fields and review guidance already connected.
Open the template page to see every proposed question and why it matters to that workflow.
Use the template, change the title and questions, and remove anything the response owner will not use.
Submit realistic sample answers, correct errors, inspect the response inbox, and test the CSV before sharing the form.
Answers about the current field tools, preview, response export, and product limits.
Yes. A blank start creates one editable placeholder question so you can define the form title, description, and field set yourself. Use a purpose-specific template instead when its workflow already matches the task.
Yes. The builder preview can switch to a narrow layout so long labels, controls, and actions can be checked before publication.
Yes. Form owners can review submissions in the response workspace and export the collected values as a CSV file.
No. Use an appropriate payment or commerce platform when a workflow needs card processing, tax calculations, refunds, or payment records.
Start with a blank form or adapt a relevant template, then verify the response process before publishing.