Understanding Blocks in Scout Workflows
Building effective workflows with modular units
Blocks are the foundational elements of any workflow in the Scout platform, acting as modular units that carry out specific tasks within a process. Each workflow begins with an input block, which receives initial data or a trigger, setting the stage for the series of actions that follow. The versatility of blocks allows users to construct complex logical flows and achieve a wide range of automation objectives.
Blocks are designed to be both composable and customizable, enabling the creation of intricate processes by linking various types of blocks in a sequence. Each block performs a unique function, such as querying a database, sending an HTTP request, or processing text with an LLM. This modularity ensures that workflows can be tailored to specific use cases, whether for data processing, API integration, or automated reporting.
Each block type has its own detailed sub-section, providing specific insights and configuration guidelines:
Interface with large language models (LLMs) using the LLM block.
Query collection data using the collection block.
Work with JSON data using the JSON block.
Save data to various locations using the save block.
Manage and manipulate text using the text block.
Make HTTP requests using the HTTP block.
Extract hyperlinks from text or web pages using the extract links block.
Set conditions and branching logic using the conditional block.
Interface with Postgres databases using the Postgres block.
Send messages to Discord channels using the Discord message block.