The Form step pauses a workflow and presents a form to the user for manual input. You define the form fields using a field set, and the workflow resumes once the user submits. Form steps are bidirectional, meaning every field set can both receive data from upstream steps and produce data for downstream steps.

• Collect initial data to kick off a workflow (e.g., a lead intake form)
• Add a human review or approval gate mid-workflow
• Let users edit or correct data before it moves to the next step
• Build multi-step wizards by chaining multiple Form steps

When execution reaches a Form step, the workflow run enters a blocked state and waits for user input. The form renders based on the field set you define, and each field becomes a form control. If the form has field mappings from upstream steps, those fields are pre-populated. Once the user submits, the form data becomes the step's output and the workflow advances. Form steps can have multiple field sets, each acting as both input and output. A "Review All Data" form, for example, can receive field mappings targeting any of its field sets from different upstream steps.