Reecall
Workflows

Overview

Workflows combine API calls, AI processing, messages, and conditional logic in a sequence of steps. Send the steps and their input data to the execution endpoint to run them.

What is a workflow?

Each step has a type that selects its action and a config object that supplies its settings. An optional output name stores the step's result in context so later steps can use it.

Anatomy of a workflow

  • Steps run in order within each sequence. Use Batch for independent operations that can run in parallel.
  • Context contains the input data and named step results. Nested steps have their own scope.
  • Morpher templates read context values in step configuration, for example {{ user.email }}.

Available step types

StepUse it to
RequestCall an HTTP API
AgentGenerate structured data with an LLM
SMS and EmailSend messages through the configured providers
RuleRun the first branch whose conditions match
BatchRun independent steps in parallel
MapRun a sequence for each item in an array
RespondReturn a custom HTTP response and stop execution

Use cases

  • Send email and SMS notifications after an order or booking.
  • Extract structured fields from text with an Agent, then send the result to an API.
  • Fetch data from several services and return a combined response.
  • Route onboarding or alerts based on user data and conditions.

Benefits

Steps share a configuration format and pass data through context, so you can combine them without writing a separate integration for each sequence. Start with the execution guide, then use the step references to configure each action.

Last modified on