Lindy vs Make: both are productivity tools on Scriptiii AI Tools. Lindy pricing: Freemium. Free tier with paid upgrades. (indexed from the vendor's public page, not independently verified) Make pricing: Freemium. Free tier with paid upgrades. (indexed from the vendor's public page, not independently verified) Both have 0 upvotes.
Lindy
Freemium. Free tier with paid upgrades. (indexed from the vendor's public page, not independently verified)
Make
Freemium. Free tier with paid upgrades. (indexed from the vendor's public page, not independently verified)
Pricing and pricing details come from the maker's submission. They are not independently verified.
What is Lindy?
Slack-first AI teammate that runs scheduled routines and agent workflows.
What it does Lindy is an assistant that lives in Slack threads and email, and also runs on a schedule. You describe a routine — triage an inbox, prep a meeting, chase a reply — and it executes the steps across connected tools. How it works Agents are built from triggers, skills and connected accounts, with persistent context about the workspace so a later…
What is Make?
A visual canvas that wires 3,500+ apps into scheduled, branching workflows.
What it does Make is a visual automation builder. You drop modules on a canvas, connect them into a scenario, and the scenario runs on a schedule or when something triggers it. Who it is for Operations people and small teams who need recurring plumbing between tools without writing a service. How it works Each module performs one action, like adding a row…
Questions
Do Lindy and Make list the same price?
Both listings report Freemium. Free tier with paid upgrades. Lindy: indexed from the vendor's public page, not independently verified. Make: indexed from the vendor's public page, not independently verified.
Which has more upvotes, Lindy or Make?
Both have 0 upvotes.
What does each maker say Lindy and Make are for?
Lindy: Slack-first AI teammate that runs scheduled routines and agent workflows. Make: A visual canvas that wires 3,500+ apps into scheduled, branching workflows.