Lindy spent two years as a no-code agent builder: drag together triggers, actions and an LLM step, point it at almost anything. On August 10, 2026, that product went away. What replaced it is Teammate, an AI coworker that lives inside Slack threads and mentions. If the automation you built runs outside Slack, or never touched Slack at all, Lindy no longer has a home for it.
What actually changed
The rebrand is bigger than a new landing page. Lindy's own support forum confirms the standalone builder is gone, not deprecated alongside Teammate but replaced by it. Slack is now a requirement to use the product at all, where before it was one integration among dozens.
This is Lindy's third distinct product identity in 18 months. Each pivot has re-pointed the same underlying agent engine at a different front door. For anyone who built on the no-code builder specifically, that history matters more than the new one: workflows for web research, form submission and data extraction, none of them Slack-shaped tasks, have no equivalent inside a Slack-native coworker.
Pricing moved with it
Lindy priced per seat before the pivot; it still does, but the numbers changed. Current plans, confirmed on lindy.ai as of this week:
| Plan | Monthly price | Credits per seat |
|---|---|---|
| Plus | $29.99 | 3,000 |
| Pro | $99.99 | 15,000 |
| Max | $199.99 | 35,000 |
| Enterprise | Custom | Custom |
Credits pool across a workspace with no rollover, so an idle month's unused allowance is gone at the reset. New signups get a 7-day trial; there is no permanent free tier.
What Trustpilot says
Lindy holds a 1.7 out of 5 rating on Trustpilot from 39 reviews, unchanged by the pivot. The complaints cluster in two places: billing (overage charges reviewers describe as unexpectedly steep, and continued charges after a cancellation attempt) and support response. One reviewer's specific complaint: no cancel button available in the billing settings. None of the visible reviews name the Teammate pivot itself, since most predate it, but the billing pattern they describe is the same product underneath.
What to use instead
If Teammate covers your use case, Slack threads with a persistent coworker, it may be the right tool now. If your workflow lives outside Slack, Lindy's old builder used to serve a few use cases in particular. Web research is one: pointing an agent at a set of sites and having it pull structured data on a schedule, no API required on the source, is exactly the category the no-code builder handled well and Teammate does not touch. Form submission is another: filling out supplier portals, government forms, or any site gated behind a login, needs a real browser session, not a webhook. Data extraction is the third: recurring pulls from a page or a portal into a spreadsheet or a database, run on a schedule without someone clicking through it each time.
WebRun runs all three as templates. Pick one, connect the accounts it needs, set a schedule. Each run happens in its own isolated browser session under the rules you set, and every run is recorded and priced at about a cent per task. Plans start at $20 a month for roughly 2,000 tasks, with a free trial and no credit card required.
The comparison
| Lindy (Teammate) | WebRun | |
|---|---|---|
| Where it runs | Slack threads and mentions only | Any scheduled or triggered workflow |
| Web research / scraping | Not supported | Template-based |
| Form submission | Not supported | Template-based |
| Starting price | $29.99/mo per seat | $20/mo |
| Free tier | 7-day trial only | Free to start, no card |
| Trustpilot | 1.7 / 5 (39 reviews) | N/A |
| Environment isolation | Shared workspace credits | One environment per client |
The practical read
Three repositionings in 18 months means the product underneath keeps changing shape faster than workflows built on it can keep up. If Teammate's Slack-only scope fits what you need, it may work. If it does not, and web research, form submission or data extraction were why you were on Lindy in the first place, that work now needs a different home.
