ZelaxyDocs
Core Blocks
Block

Starter Block

The entry point for every workflow — receives input and triggers execution

Starter Block

Every workflow begins with a Starter block. It receives the initial input (user message, webhook payload, or scheduled trigger) and makes it available to all downstream blocks via {{starter.input}}.

Overview

PropertyValue
Typestarter
CategoryCore Block
Color#2563EB (Blue)

When to Use

  • Every workflow must have exactly one Starter block
  • It's automatically added when you create a new workflow
  • Configure it to accept different input types and connect triggers

Configuration

SettingTypeDescription
Start LabelShort inputDisplay label for the start button
Input TypeDropdownExpected input format: text, json, file
TriggersTrigger configConnect webhooks, schedules, or generic webhooks

Input Modes

Text — Simple string input from the chat interface or API call.

JSON — Accepts structured JSON for complex input scenarios with multiple fields.

File — Accepts file uploads for document processing workflows.

Outputs

FieldTypeDescription
inputstringThe raw input text or JSON string
filefileUploaded file reference (file mode)
triggerjsonTrigger metadata (webhook headers, schedule info)

Example: Simple Chatbot Entry Point

Workflow:

[Starter] → [Agent] → [Response]

How it works:

  1. User types a message in the workflow chat
  2. Starter captures it as {{starter.input}}
  3. Agent processes the input and generates a response
  4. Response block returns the answer to the user

Example: Webhook-Triggered Automation

Workflow:

[Starter (webhook)] → [Function: Parse] → [Agent] → [Slack]

How it works:

  1. External service sends POST request to the workflow's webhook URL
  2. Starter captures the JSON body as {{starter.input}}
  3. Function block parses and extracts relevant fields
  4. Agent processes and sends results to Slack

Tips

  • Reference input everywhere{{starter.input}} is available in any downstream block
  • For JSON input, parse it in a Function block: JSON.parse(inputs.starter.input)
  • Connect triggers for automated execution (webhooks, schedules)