Skip to content

Start Node

Definition

The Start node is a required preset node in every Workflow application. It provides the initial information needed for the workflow to run — such as user input and uploaded files — and makes that information available to all downstream nodes.

Configuring the Node

The Start node settings panel has two sections: Input Fields and System Variables.

Start Node

Input Fields

Input fields are configured by the application developer to collect additional information from the user before the workflow runs. For example, a weekly report application might ask the user to provide their name, work date range, and task details upfront. This pre-collected information helps the LLM generate higher-quality output.

Six variable types are supported, all of which can be marked as required:

  • Text — Short text, user-entered, max 256 characters.
  • Paragraph — Long text, allows longer user input.
  • Dropdown — Fixed options set by the developer; users can only select from the preset choices.
  • Number — Numeric input only.
  • Single File — Allows the user to upload one file. Supports documents, images, audio, video, and other file types. Supports local upload or pasting a file URL.
  • File List — Allows the user to upload multiple files. Same format support as Single File.

Note: The file list upload limit is a maximum of 100 files.

System Variables

Workflow applicationtically inject the following system variables into the Start node. They can be referenced directly in any downstream node without manual configuration:

VariableData TypeDescription
sys.filesArray[File]List of files uploaded by the user
sys.user_idStringUnique identifier of the current user
sys.app_idStringUnique identifier of the current application
sys.workflow_idStringUnique identifier of the current workflow
sys.workflow_run_idStringUnique identifier of the current workflow execution instance

System variables are itomatically by the platform. They can be referenced anywhere — in model node prompts, condition nodes, HTTP request nodes, etc.

Note: Workflow applications are single-run processes with no multi-turn conversation, so conversation-related variables like sys.query, sys.conversation_id, and sys.message_id are not available.