#When should I use workflows instead of a regular agent? Im trying to figure out where workflows fit

1 messages · Page 1 of 1 (latest)

rare ferryBOT
#
AI-generated Answer for flenshhh0524

Short answer: Use Workflows when you need explicit, visual control over conversation flow, routing, and guardrails beyond what a single agent’s prompt, tools, and knowledge can reliably handle.

Use Workflows when any of the following apply

  • You need branching flows (decision points) instead of a single, linear conversation path. Workflows provide a visual, graph-based editor for complex, dynamic flows. (elevenlabs.io)
  • You want to route tasks to specialized Subagents that each have their own prompt, tools, scoped knowledge, and even different LLMs or voices at different steps. (elevenlabs.io)
  • You must guarantee a specific tool call at a given step and branch on success/failure using a dedicated Dispatch Tool node. (elevenlabs.io)
  • You need first-class handoffs: transfer between AI agents, or escalate to a human/phone number as part of the flow. (elevenlabs.io)
  • You need deterministic guardrails and to gate high‑risk operations behind step-based workflows for compliance and data protection. (elevenlabs.io)
  • You want to optimize cost/latency/accuracy by selecting different LLMs per step (e.g., lightweight for routing, stronger for reasoning) and keep contexts tightly scoped. (elevenlabs.io)

Stick with a single “regular” agent when

  • A single prompt + set of tools + knowledge base can handle the task end‑to‑end without predefined branching or multi‑agent routing. In this case, let the agent handle behavior via the prompt while the platform manages conversation mechanics (turn‑taking, etc.). You can always add a Workflow later if the logic grows. (elevenlabs.io)

Pointers to the official docs

  • Workflows (visual builder, Subagents, Dispatch Tool, edges/conditions). (elevenlabs.io)
  • Agent-to-agent transfer (multi-agent handoffs). (elevenlabs.io)
  • Support page highlighting deterministic workflows for high‑risk operations. (elevenlabs.io)
  • Blog: Introducing Agent Workflows (security/policy guardrails, cost/latency optimization, example routing patterns). (elevenlabs.io)

If you share your use case (channels, tools to call, compliance needs), I can map it to a minimal Workflow or confirm a single agent is sufficient

south jolt
#

for the agents api, if we receive a message via whatsapp to our agent, is it possible to call an endpoint to load dynamic data on the conversation initiation? specifically to whatsapp