zapier nails the workflows that never change, the ones that mutate every run are where i want an agent
Summary
The author observes that Zapier handles fixed workflows well, but variable workflows are where they want to use an AI agent.
Similar Articles
Are we calling too many workflows “agents”?
The author questions whether many so-called AI agents are better described as workflows, arguing that for repeatable browser tasks, defined workflows may be more reliable than agents that reinterpret steps each time.
AI agents are starting to expose how broken most workflows already were
The article argues that AI agents are revealing how unstructured and chaotic many corporate workflows actually are, suggesting that successful automation depends more on clean systems and documentation than on advanced models.
I stopped building single agents. Here's why I switched to workflows instead.
The author explains why they switched from single agents to chained workflows for AI tasks, citing improved reliability and easier debugging despite higher upfront complexity.
@AdamRLucek: I'm bullish on agent swarms (aka workflows). Agents are increasingly being used to analyze and collate massive amounts …
The author discusses the growing use of agent swarms/workflows for processing unstructured data at scale, noting that reliable execution drops significantly when deploying more than 30+ sub-agents in parallel, and teases a solution for combining intelligent decision-making with reliable task execution.
Everyone is selling AI agents, but almost nobody is selling the workflows to make them useful.
The article argues that while many are building and selling AI agents, the real value lies in the workflows and training that make them useful, not the underlying technology.