Input Form (Legacy) Block

The Input Form (Legacy) block manually triggers a workflow from the editor using a structured, typed input schema. It is a legacy starter — for new workflows, prefer the Start block.

Overview

When to Use

• Manually start a workflow from the editor during development or testing
• Define a typed JSON input schema so the workflow expects structured data
• Expose typed inputs that a parent workflow can map into when calling this workflow as a subflow
• Maintain an existing workflow that already relies on this legacy trigger (for new builds, use the Start block instead)

Configuration

Input Format

Define the JSON input schema for this workflow when run manually. This declares the typed fields the workflow accepts, allowing parent workflows to map values into them.

Tools

This block has no tool integrations (tools.access is empty). It is a trigger block that starts workflow execution; it does not call external tools.

Inputs & Outputs

• Inputs: none (the block declares no inputs keys; data is supplied through the configured input schema)
• Outputs: none declared

YAML Example

input_start:
  type: input_trigger
  name: "Input Form (Legacy)"
  inputs:
    inputFormat: '[{ "name": "query", "type": "string" }]'
  connections:
    outgoing:
      - target: next-block-id