Input Block
Discover how to effectively set up and utilize the Input Block in Scout workflows, the essential starting point for defining and managing input fields.
Learning Objectives:
- Add and configure an Input Block as the workflow’s trigger
- Define input fields with proper data types and settings
- Reference input values dynamically in downstream blocks
1. Choose a Trigger Block:
When starting a new workflow, your first action should be to define the trigger—this sets how your workflow receives data. Scout supports three trigger options:
- Input Block – for manual or API-based input (recommended for most cases)
- Copilot Block – when input comes from a chat interface
- Slack Message Block – for workflows initiated by Slack commands or messages

- Choose the block that matches your intended source of input.
- When setting up a copilot and chat interface use the Copilot Block in place of the input block.
2. Add and Configure the Input Block:
- To use the Input Block as your trigger:
- Open Your Workflow Canvas
- Create a new workflow or open an existing one in edit mode.
- Add the Input Block
- Click the “Set a trigger” button.
- Define Input Fields
- Each field you add will accept a value when the workflow runs. For each field:

- Display Name: Human-readable label (e.g., User Message)
- ID: Unique key to reference the field (e.g.,
user_message
) - Type: Choose one:
short_text
– brief user messages or titleslong_text
– longer input like article contentnumber
– numerical valuescheckbox
– true/false valuesjson_object
– structured JSON input
- Optional Toggle: If checked, this input can be left empty when the workflow is triggered.
3. Add and Configure Slack Message Block:
- Slack Message block lets you start a workflow automatically when specific events happen in Slack—like when a message is posted, a user mentions the bot, or a thread is started.
- Open the “Slack Message” block and connect to your Slack, once connected, your Slack Message block should look like this:

- With Scout added to your workspace, select the channel where it will be deployed to.
- Finally select one of the 3 modes:
- Active Listener Mode: Engages with all messages
- Mention Listener Mode: Responds only when mentioned
- Thread Initiator Mode: Replies only to the first message in a thread
4. How Input Data Flows Through the Workflow:
- Once the workflow is triggered (by a form, API call, Copilot, or Slack), Scout captures the input field values and makes them available to all downstream blocks.
- This allows blocks like LLM, JSON, or API blocks to act on dynamic user-provided data.