Workflow Automation
Lindy
Email-and-calendar agents with a leash
Lindy is an agent that lives in email and calendar. Start with drafts. Do not give send authority on day one.
List price: Free/low tier then paid from tens of dollars. Confirm current packing.
Review status
Email-and-calendar agents with a leash
An agent in the inbox. Easy to start, spend is the risk.
No four-job lab on this one yet. Placement is editorial. Confirm the price with the vendor.
Where it earns the seat
- • Agent UX non-technical people will try
- • Email/calendar are the right surfaces
- • Faster than drawing a 12-step Make scenario
Where it fails
- • Autonomy is the risk
- • Not an iPaaS replacement
- • Eval the send permissions like an identity review
Best for
AI agents
Inbox and calendar agents that should start as drafts-in-a-queue.
Operator review · evidence before adjectives
Lindy evaluation plan
The real product is failure handling: idempotency, retries, credentials, audit, and the person paged when a payload changes.
Know which job you are buying
No-code integration
Connect common SaaS events and actions
Boundary: Best for simple, observable business flows
Visual process builder
Branching, data changes, queues, and multi-step processes
Boundary: Complexity requires version history and an operating owner
Self-hosted automation
Custom nodes, private networking, and controlled execution
Boundary: Infrastructure and security become your job
AI agents
Interpret unstructured input and choose among tools
Boundary: Nondeterminism requires narrower permissions and stronger review
The four-run test
Make the demo survive real work
Use the same inputs with every finalist. Score the artifact, the audit trail, and the failure—not the presenter.
01
The duplicate event
Feed it: The same paid-order event delivered three times after a timeout.
PassCreates one downstream record and logs deduplication with a stable key.
Where it faceplantsCharges, emails, or provisions three times.
02
The schema drift
Feed it: A source field changes type and one optional field disappears.
PassStops or routes the record with a visible error and recoverable payload.
Where it faceplantsSilently writes nulls or maps the wrong value into production.
03
The partial failure
Feed it: Step four of six fails after the CRM write but before the customer notification.
PassResumes safely or compensates without duplicating completed actions.
Where it faceplantsRetries the entire flow and corrupts state.
04
The agent boundary
Feed it: An ambiguous request with access to email, CRM, and a refund action.
PassUses least privilege, proposes consequential actions, and records approval.
Where it faceplantsTreats tool availability as authorization.
Score the operating result
| Metric | Measure | Red flag |
|---|---|---|
| Successful business outcomes | Complete, correct end states—not green step executions | Platform task count is reported as value |
| Duplicate and replay safety | Idempotent behavior under retries and late events | Happy-path demos only |
| Mean time to detect/recover | Minutes from bad event to owner and repaired state | Failures live in a builder nobody monitors |
| Credential blast radius | Actions available to each connection and agent | One owner token powers every workflow |
AAT · Editorial reading
The Dials
Four readings. Not a score. Not a room.
An agent in the inbox. Start as drafts. The danger is send authority.
Company size
How automatic
Style
Collaboration
Four independent meters for this product. They do not cross. Company size, how automatic, whether it invents a voice or follows yours, and how much of the team can work in it.
More Workflow Automation tools
More tools in this category. Confirm list prices on the vendor page.
Visual automation for branching logic
Make is the canvas for loops, routers, and cheaper operations. It is the live affiliate on this site because the product actually matches the ops job.
The default no-code glue
Zapier is the first automation seat: 6,000+ apps and a builder a marketer can finish. Switch when branching or task cost hurts.
Enterprise iPaaS with an AI story
Workato is what RevOps buys when Zapier is a toy and IT wants an iPaaS with RBAC. Not a founder weekend project.
Self-host when you want the workflow file
n8n is for teams that want the workflow as code/self-host, not a metered SaaS. Cloud exists; the point is control.
Canvas for AI-heavy flows
Gumloop is a canvas aimed at AI pipelines: scrape, extract, generate. Treat outputs as drafts.
Low-code iPaaS for product and ops
Tray is the Merlin/low-code middle: more power than Zapier, less “hire an integration team” than MuleSoft.
Workforce of agents with tools
Relevance AI is an agent workbench: tools, knowledge, and workforce views. Start with one job and logs.
Human-in-the-loop automations
Relay is automation that waits on a human. Use it when the step is “approve this draft,” not “fire and forget.”
Browser-native automations for the tab you are in
Bardeen runs on the page: scrape, enrich, push to CRM from the tab. Good for SDRs. Not your system of record.
Microsoft’s automation seat you may already pay for
Power Automate is the correct first automation if the org is already in Microsoft 365. Do not buy Zapier first out of habit.