Skip to main content
A workflow form is a public web page that collects a workflow’s inputs and starts a run when someone submits it. Use one when you want humans outside your team (or without CLI/API access) to kick off a deployed workflow from a link. Forms are a platform feature: they are published against a deployed workflow, not defined in project code. Field shape comes from the workflow’s input schema. Presentation (labels, help text, controls) is configured when you publish.

​
When to use a form

Forms appear on the workflow canvas as a Form trigger once published. Submissions create normal workflow runs you can inspect like any other surface.

​
Requirements

  • The workflow must be deployed and accept inputs (input schema with at least one field).
  • Supported field types are scalars (string, number, boolean, enum) and arrays of scalars. File, object, and nested array fields are not supported yet.
  • You need permission to manage the project (publish / unpublish / rotate).

​
Publish from the dashboard

  1. Open the workflow in the web app.
  2. Use Share → Publish a form.
  3. Optionally set a title, description, and per-field presentation (label, help text, placeholder, control).
  4. Copy the public URL and share it.
You can customize presentation later from the same Share menu, unpublish to stop accepting submissions, or rotate the link to invalidate the old URL.

​
Manage forms from the CLI

Forms are org/project-scoped like other platform commands. Link a project (or pass --project) so workflow slugs resolve unambiguously.
list includes disabled (unpublished) forms; use the enabled field to see which still accept submissions. Full flag reference: CLI — workflows.

​
Field presentation

--field-config (or the dashboard editor) is a JSON map of input field key → presentation options: Allowed controls by field type: Unknown field keys or unsupported controls are rejected on publish. If the deployed schema later drops a field, stale config for that key is ignored on the public page so the form keeps working.

​
Branding

Public forms show your organization and project name, plus optional org logos from workspace settings. Branding is not set on the form publish payload.

​
Next steps

Run workflows

Triggers, CLI, API, and agent tools for starting runs.

Build workflows

Define typed input schemas that drive the form fields.

CLI reference

Full workflows forms command table.

Workflow runs

Inspect submissions in run history.