A workflow is a visual, node-based automation that connects triggers, logic, and actions into a directed graph. Workflows are how Anyreach extends agent capabilities, i.e calling your APIs, transforming data, branching on conditions, and handling events.Documentation Index
Fetch the complete documentation index at: https://docs.anyreach.ai/llms.txt
Use this file to discover all available pages before exploring further.
When to use a workflow
| Situation | Use a workflow when… |
|---|---|
| Post-call processing | After a call ends, summarize the conversation, write to your CRM, or alert Slack |
| Pre-call setup | Before a campaign call, fetch the contact’s history and prepare the agent |
| Agent tools | Give your agent the ability to look up orders, book meetings, or update records |
| Ongoing conversations | Run logic mid-conversation as the agent speaks with a contact |
| Scheduled jobs | Nightly reconciliation, daily reports, recurring follow-ups |
| External events | Respond to a Slack message, Google Sheet row, or any Pipedream-connected app |
How a workflow runs
Every workflow starts with a Trigger — the event that kicks it off. From there, execution flows step by step through the canvas until it reaches the end or an Output step. Steps connect by directional edges. Condition steps create branches. Every path eventually terminates.Step types
Seven step types are available in the builder:| Step | Purpose |
|---|---|
| Trigger | The entry point — defines what starts the workflow to run |
| Input | Define named input fields when running the workflow manually |
| Action | Call Anyreach-native apps or 2,000+ external apps |
| Condition | Branch the workflow’s path depending on data-driven conditions |
| Code | Run sandboxed Python code with access to workflow context |
| HTTP API | Call any HTTP endpoint directly |
| Wait | Pause execution for a set duration before continuing |
| Output | Return a structured result and terminate the path |
Trigger types
Triggers determine what starts your workflow. Anyreach supports two categories: AnyReach triggers - Triggers native to the platform:- Pre Call — runs before a call begins
- Post Call — runs after a call ends
- Ongoing Conversation — runs while a conversation is active
- Timer — runs on a recurring schedule
Versioning
Each workflow has a Draft, a Published version, and any number of Live versions. Edit the draft, publish it to create a new version, and mark a version as live to activate its triggers.
Execution modes
Workflows run in two modes:- Synchronous — the caller waits until the workflow finishes. Used by agent tools during a live call.
- Asynchronous — returns immediately with an execution ID; the workflow runs in the background. Used for post-call jobs, scheduled runs & runs via API’s.