| Tool | Self-host | Pricing model | Custom code | Best for |
|---|---|---|---|---|
| n8n | Yes (fair-code license) | Cloud plans by executions; self-host community edition | JavaScript, Python | Self-hosted workflows, AI agent nodes, Telegram triggers |
| Zapier | No | By tasks per month | Code steps (JS, Python) | Largest app catalog, non-technical teams |
| Make | No | By operations/credits | Limited | Visual multi-step scenarios with branching |
| Pipedream | No | By credits (compute time) | Full Node.js, Python, Go, Bash | Developers who want webhooks plus real code |
| Node-RED | Yes (Apache 2.0) | Free, you host it | JavaScript | IoT, home automation, small servers |
| Activepieces | Yes (MIT core) | Cloud plans; free self-host | TypeScript | Open-source alternative to Zapier |
Licenses and hosting options checked on 2026-10-19. Pricing pages linked; limits not copied because they change frequently.
When to use no-code, and when not
- Good fit: a form posts to Slack, a new order sends a Telegram message to staff, a nightly report, connecting two SaaS tools.
- Poor fit: a public bot with many users, conversations with state, strict latency, or anything where per-task pricing grows with every message.
- Middle ground: keep the bot in code and let a workflow tool handle back-office tasks through a webhook.
Self-hosting n8n or Node-RED on a small VPS works well; see the VPS tutorial and the automation guide. Design flows first with the flow designer.