Activepieces

What it is and why

Activepieces is an open-source Zapier alternative with an MIT license (freer than n8n's fair-code) and a simpler, Zapier-like UX. You can host it yourself — your data stays under your control and there's no per-operation fee. It has AI steps and custom "pieces" written in TypeScript. Take it when you want Zapier's simplicity + the privacy of self-hosting + a genuinely permissive license (including for embedding it in your own product).

How to do it (step by step)

1. Where to run it. Activepieces cloud (paid, fast) or self-hosted via Docker/docker-compose (free, private). A ready compose file is in their repository.
2. Create a Flow. Pick a Trigger: a schedule, a webhook (Catch Webhook) or a service event.
3. Webhook. The "Catch Webhook" trigger gives you a URL → paste it into the source (a form/payment provider).
4. Add steps (pieces). Chain actions together: HTTP, Google Sheets, Telegram, SMTP, and AI steps (call an LLM to process text right inside the flow).
5. Map the data by picking fields from previous steps (drag-and-drop, like in Zapier).
6. Branching and loops. Branch (if/else) and Loop (iterating an array) for logic.
7. A custom piece (if there's no ready connector): written in TypeScript against their SDK — it plugs the gaps in the catalog.
8. Test and publish. Run it → Publish → the Flow is live. Run logs are in the Runs tab.

A ready-made recipe/combo

"Lead → AI qualification → CRM": a webhook from the form → an AI step takes the request text and classifies it ("hot/cold lead", extracts the budget) → Branch: hot ones → create a deal in the CRM + a Telegram message to the manager; cold ones → into Google Sheets for nurturing. AI processing right inside the flow with no separate service, all on your own server (MIT license, your data stays with you).

What it costs (honestly)

The logic: self-hosting is free (MIT) with no operation limit — you only pay for your own server. The cloud is a subscription by number of tasks/seats. The MIT license even lets you embed it in your own commercial product. Exact cloud amounts are on Activepieces' side and change.

When it fits / doesn't fit

• Fits: you want Zapier's simplicity + self-hosting; you need the most permissive license possible (MIT, embedding); you need AI steps in the flow; you have Docker skills.
• Doesn't fit: you need the widest catalog of ready integrations (Zapier/Make); you don't want to maintain a server; you need a mature product with a huge ecosystem (the project is young).

Risks and responsibility

Self-hosting = server, key and backup security is on you. Processing customers' personal data falls under Russia's 152-FZ (consent required). AI steps send data to an external LLM — don't pass sensitive personal data there without an assessment (or use a local model). Automated mailings require consent. See the section disclaimer.

🤖 Prompt helper

You're an Activepieces engineer (self-hosted, MIT). Design a Flow for: "{task, which services}". Give me: (1) the trigger and the steps in order; (2) where to insert an AI step and what prompt to give it for processing the data; (3) the Branch/Loop logic; (4) whether a custom piece is needed and what for. Step by step, assume I'm on Docker.