Webhooks, cron schedules, and app events trigger chains of nodes that fetch, transform, and route data: n8n is a workflow automation platform built around a visual, node-based editor. It ships with 400+ built-in integrations covering databases like Postgres, SaaS tools like Slack and HubSpot, and every major AI provider. When a pre-built node does not exist, the HTTP Request node calls any REST API, and the Code node runs JavaScript or Python inline, so you are never blocked by a missing connector. Workflows execute as directed graphs with branching, loops, error handling, and sub-workflows, and every run is logged for inspection and replay during debugging. It also includes LangChain-based nodes for building AI agents with tool calling and memory. Self-hosting on RepoCloud gives you unlimited workflow executions with no per-task pricing, and all data stays on your instance. Runs on Node.js with SQLite by default; add Postgres and Redis queue mode when you need to scale workers horizontally.

Zapier's job, on your own server: Activepieces is an open-source workflow automation platform built to be exactly that replacement. Flows are built in a visual no-code editor with triggers, actions, loops, conditional branches, auto-retries, raw HTTP steps, and code steps that run JavaScript or TypeScript with full npm package support. Integrations are "pieces" - type-safe TypeScript npm packages with hot reloading for local development - and the catalog spans 600+ services, with the large majority contributed by the community. The platform is AI-first in two directions: native AI pieces call OpenAI, Anthropic, Google, and Azure models inside flows, and every piece automatically doubles as an MCP server, so assistants like Claude Desktop and Cursor can invoke your integrations and workflows through natural language. A built-in MCP server also exposes 30 tools for building flows, managing tables, and running tests agentically. Flows are fully versioned with draft and locked states. The core is MIT-licensed and runs on TypeScript with PostgreSQL and Redis.

Automatisch runs your Zapier workflows on your own hardware - an open-source, self-hosted automation platform built as a direct alternative. Flows are chains of steps: one trigger (a polling or webhook event such as a new GitHub issue, a Stripe payment, or a form submission) followed by action steps that pass data downstream (post to Slack, append a Google Sheets row, update Notion). The visual builder deliberately mirrors Zapier's trigger-action model, so migrating existing Zaps requires no retraining and no programming knowledge. Roughly 60 integrations cover common business services - Slack, GitHub, Google Sheets, Notion, Stripe, Discord - and connections store credentials per service, with multiple accounts per app supported. Every execution runs on your own server: execution history, logs, and payload data never touch a third-party processor, which matters for GDPR, healthcare, and finance workloads. Error handling with retry logic, a REST API for programmatic flow management, and Docker Compose deployment round out the platform. The AGPL-3.0 Community Edition has no feature limits or per-task billing; an Enterprise Edition adds SSO, roles, and audit logs.

Drag an AI agent onto a canvas beside a Gmail trigger, a condition, and a Google Sheets step, and ByteChef runs the whole thing as one durable workflow that resumes where it stopped. Runs that fail or wait for a human pick up from the step they reached. The visual editor maps values between steps with data pills, and its 250+ connectors double as agent tools and MCP tools. An agent combines a model from twelve LLM providers, including OpenAI, Anthropic, Mistral, and Ollama, with chat memory, knowledge-base retrieval, and tools. It streams structured answers. Flow controls cover conditions, branches, loops, parallel and fork-join paths, subflows, error handling, and approval steps that pause for a person. Workflows start from webhooks, polling, schedules, forms, or app events, and code steps run JavaScript, Python, or Ruby. Workflows can be exposed through an MCP server for Claude Desktop, Cursor, or Windsurf, and ByteChef consumes external MCP servers too. Data Tables add typed relational tables with a spreadsheet-like grid and CSV import and export. The Agent Playbook opens a chat with the agent as you build it. Every run is listed with per-step input, output, and errors. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache 2.0 + EE licensed.

With over 5,000 GitHub stars since its June 2026 launch, OOMOL OpenConnector bridges the gap between AI agents and the real world by handling the authentication nightmare that stops LLMs from calling external APIs safely. The runtime connects to more than 1,000 SaaS providers — GitHub, Gmail, Notion, Slack, Microsoft, HubSpot, Google Workspace, and hundreds more — through 10,000+ prebuilt typed Actions that agents can discover and execute without ever touching raw credentials. OAuth2 flows, API key rotation, custom credentials, and no-auth providers are all managed centrally with AES-encrypted storage, scoped runtime tokens, and configurable action allowlists and blocklists that enforce least-privilege access. Agents interact through five access surfaces: the Model Context Protocol endpoint at /mcp for Claude and other MCP-capable hosts, a full REST API at /v1 for programmatic control, an auto-generated OpenAPI specification for code generation, a TypeScript SDK for application integration, and the oo CLI for local agent relay. The built-in Web Console provides browser-based administration for configuring OAuth apps, managing connections, inspecting action schemas, and reviewing execution logs with redacted inputs. Deploy via Docker Compose with SQLite for single-server setups, run from source on Node.js 22+, or push to Cloudflare Workers with D1 and R2 for edge deployment. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache 2.0 licensed.

DopplerTask is the control layer where AI agents build your automations and you decide what goes live. You describe the outcome in plain language, and your agent assembles a task from a library of eighty-one ready-made steps spanning messaging, ticketing, sales, operations, documents, databases, queues, and AI models. The proposal lands in a visual editor that people and agents share, with new and changed steps marked and the old value of each field beside the new one. Nothing goes live until you approve it, and the previously approved version keeps running untouched in the meantime. Once a task is live it can start from a webhook, a schedule, a message queue, a manual click, or the agent itself, and every run is recorded with the output of each step, the person who started it, and the person who approved the version. Failed runs resume from the step that failed, with retries and continue-on-failure where you want them. Agents reference your credentials by name only; the values stay encrypted on your server, beyond the agent's reach, and separate tokens for people and agents plus single sign-on keep access tidy. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

Connect your services once and let every AI agent use them through a single MCP endpoint, without a credential ever reaching the agent. Executor packages each integration as an app: a small TypeScript program that turns saved accounts into tools. Install one from a catalog of more than 1,800 ready-made apps, add a remote MCP server by URL, or have your agent write and deploy a new one. Agents get two tools, skills and execute, so they search for what they need and run a short program across as many apps as a task takes. Each tool decides when to ask first: always, never, or only when the input looks risky, and you approve in your agent, your MCP client, or a browser page. The dashboard shows every app with its tools, skills, workflows, schedules, webhooks, source files, and version history, and every deploy can be rolled back. Connections give each agent its own MCP URL that reaches only the apps you pick, with copy-paste setup steps for Claude, ChatGPT, Codex, and others. Organizations, groups, invitations, shared accounts, and optional single sign-on cover teams. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.