Form

Manual trigger that presents a multi-field form when you run the flow. Press Run — from the canvas or the menu bar — and a floating glass panel appears; Submit seeds the run with every field as a typed payload value, Cancel means the run never starts.

The panel is an always-on-top window: it follows you to the active Space, works over full-screen apps, and is resizable in height. It sizes itself to its content and grows when the content grows — image thumbnails, for example. Esc, the Cancel button, and the red close button all cancel it.

Like the Input trigger, a form flow has no watcher to arm, so it is always active — its status dot reflects the health of its recent runs rather than an on/off state, and the Enabled switch is shown turned on but inert.

Summon it from anywhere: pair a Keyboard Shortcut trigger with a Mid-Flow Form action and the form pops up on a global hotkey, no canvas visit required.

Fields are defined in the inspector's Fields editor: reorderable rows (drag handle) with per-type extras — placeholder, default value, help text, options, validation. The Preview Form… button presents the real panel in dry-run mode (Submit discards). Field names are auto-slugged from their labels, editable, and must be unique; the reserved names form, formTitle, timestamp, and filePath are rejected inline. The AI Flow Builder can author fields conversationally (“add title, description, and a priority dropdown”).

Validation runs live in the panel: required fields gate the Submit button until valid, numbers must parse, email and phone formats are checked, a Select value must be one of its options, and optional min/max, regex, and max-length rules apply per field.

A Destination field emits a structured object under its field name:

"destination": {
  "provider": "linear",
  "account": "acme-workspace",
  "teamId": "team_01H…",
  "teamLabel": "Watchflows",
  "projectId": "proj_01H…",
  "projectLabel": "Bug Bash"
}

(projectId/projectLabel appear only when the field's source is Linear Projects.) Downstream Linear nodes can route with {{destination.teamId}} and friends — or, easier, pick “Use the form's pick” in the Linear: Create Issue node's Destination dropdown, which writes those templates for you.

When an agent or MCP client runs the flow, each field resolves in order: the caller-supplied value, else the configured default — and if a required field has neither, the run is refused with a message naming that field. The panel never appears for agent runs, and values flow through the same payload builder, so headless payloads are identical in shape to interactive ones.