Skip to main content
Back to Blog
workflows forms automation configuration

Workflow-Generated Forms

Swifty Team Oct 20, 2025 2 min read

Multi-step workflows have a configuration overhead that grows with complexity. You design the workflow steps, then separately configure which form each step should use, which fields should appear, and what the user should see when they're working that step.

Workflow-generated forms remove that overhead.

Forms Derived from Workflow Context

When a workflow reaches a step that requires user input, the platform now automatically generates an appropriate form based on:

  • What information is needed to proceed: The workflow definition specifies which fields must be filled or confirmed to advance to the next step. Those fields appear on the form.
  • What's already known: Fields that have values from previous steps or from the record itself are pre-populated. Users only fill in what's genuinely new.
  • What the step is for: A review step generates a form with readable field values and an approve/reject action. A data-entry step generates an editable form. The form type matches the step type.

Fewer Things to Configure

Traditional workflow configuration requires: define the steps, define the transitions, define the form for each step, define which fields each form shows, define the layout of each form. That's five separate concerns.

Workflow-generated forms collapse the last three into a single concern: define what information each step needs. The form generation handles the rest.

Customization Where It Matters

Auto-generated forms are the default, not a constraint. For steps where the generated form isn't quite right — custom layout needed, specific field grouping, special instructions for the user — you can override the generated form with a custom one.

The automatic path works for the common case; the override path handles the exceptions.

The Result

Workflows get built faster because there's less to configure. Changes to workflow steps automatically update the generated forms — add a field to a step's requirements and it appears in the form without a separate update.

Workflows should drive the UI. Generated forms make that happen automatically.

Related posts

Composed Data Sources

Chain and relate data sources for rich dashboards — compose complex data views from simpler sources without writing code.

Computed Expressions

Transform data with template expressions and built-in functions — format, combine, and derive values from your data without code.

Cross-Source Data Joins

Combine data from multiple sources in one view — join records from your database with data from external services using a shared key.