Skip to content

Flow Steps Overview

Steps are the building blocks of Flows in Cognipeer. Each step performs a specific function, from asking a language model to searching a datasource, collecting approval, or preparing a final response. This guide provides an overview of the step types available for building workflows.

Understanding Steps

Each step in a Flow:

  • Accepts inputs either from Flow inputs or previous steps
  • Performs a specific operation
  • Produces outputs that can be used by subsequent steps

Steps are executed in sequence, creating a flow of operations that process data and produce results.


Available Step Types

Cognipeer offers a diverse range of step types to build powerful workflows:

AI and Language Model Steps

Studio Flow Agent step showing model, chat-history option, system prompt, and user message configuration

Connected Client Actions

  • Client Tool - Pause a Flow while a connected client action completes

Data and Search Steps

Studio Flow Search in Knowledgebase step showing datasource selection, prompt input, result count, and source saving option

Web and Internet Steps

Workflow Control

Studio Flow Each step showing array variable selection, max item limit, and loop branch outputs

Interaction and UI Steps

Utilities

Variable Manipulation

Memory Management


Combining Steps

The power of Flows comes from combining multiple steps into cohesive workflows. Here are some common patterns:

Sequential Processing

The simplest pattern is sequential processing, where steps are executed one after another, with each step using the output of the previous step.

Example:

  1. A trigger starts the Flow with user-provided inputs.
  2. A data or tool step gathers supporting information.
  3. An AI step summarizes the result.
  4. A Final step returns the outcome.

Conditional Branching

Use the Condition step to branch Flows based on earlier outputs.

Data Enrichment

Combine search and AI steps to enrich data:

  1. Search Knowledgebase step retrieves relevant information
  2. Optional tool or web steps add supporting context
  3. Ask LLM step combines and synthesizes the information

Best Practices for Using Steps

  • Start Simple: Begin with a few steps and test thoroughly before adding complexity
  • Use Descriptive Names: Give each step a clear, descriptive name that indicates its purpose
  • Plan Your Data Flow: Consider how data will flow between steps and what transformations are needed
  • Handle Errors: Use Node.js steps to implement error handling where appropriate
  • Test Incrementally: Test your workflow after adding each new step to identify issues early

Next Steps

Explore the detailed documentation for each step type to learn about their specific configurations, inputs, and outputs:

  • See the step reference links above for detailed pages.

By understanding the capabilities of each step type, you can design effective workflows that automate tasks, integrate systems, and leverage AI to solve business problems.

Studio · Pulse — Cognipeer product documentation