Skip to main content
toolsSource-backed
Activepieces logo

Activepieces

Open-source, self-hostable workflow automation platform with AI workflows, TypeScript pieces, human-in-the-loop steps, and a built-in MCP server.

by Activepieces · submitted by oktofeesh1·added 2026-06-03·22,776 source repo stars·
HarnessCLI
Review first review before installing

Open the source and read safety notes before installing.

Citation facts

Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.

Source URLs
https://www.activepieces.com/docs/overview/welcome, https://github.com/activepieces/activepieces, https://www.activepieces.com
Brand
Activepieces
Brand domain
activepieces.com
Brand asset source
brandfetch
Safety notes
Activepieces flows can send messages, call APIs, write records, publish webhooks, run code, and trigger cross-system side effects, so production flows need tests, approvals, rollback paths, and rate-limit controls., The built-in MCP server can let AI assistants build flows, manage tables, inspect runs, test automations, and publish changes; enable only the needed tool categories and keep project scope tight., Custom TypeScript pieces and code steps should be reviewed like application code, especially when they handle secrets, filesystem access, network calls, or business-critical integrations.
Privacy notes
Workflows can process prompts, customer records, emails, documents, form responses, table data, app payloads, webhooks, run logs, error traces, and AI-generated outputs., Activepieces connections may store OAuth tokens, API keys, account identifiers, webhook URLs, and service credentials; avoid exposing them in prompts, logs, MCP tool output, screenshots, or exported flows., Self-hosted deployments still need retention, backup, database, Redis, worker isolation, outbound network, telemetry, and access-control policies for all flow and run data.
Author
Activepieces
Submitted by
oktofeesh1
Claim status
unclaimed
Last verified
2026-06-03

Decision playbook

Review trust signals before you adopt

Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.

Compare context
Selected

0

Current score

78

Baseline

Delta

No baseline selected

No major trust-signal divergence detected in the current selection.

Source and provenance checks

Complete

Confirm ownership and provenance before trusting install instructions.

  • Source link availableRequired

    Open the canonical repository and verify ownership.

    Done
  • Source provenance statusRequired

    Marked as source-backed.

    Done
  • Metadata reviewed

    Registry metadata indicates a reviewed listing.

    Done

Safety and privacy checks

Complete

Validate risk disclosures before installation or API wiring.

  • Safety notes presentRequired

    Review the listed safety guidance before running commands.

    Done
  • Privacy notes presentRequired

    Review data handling notes before connecting accounts or secrets.

    Done
  • Trust level risk gateRequired

    Trust level does not block evaluation.

    Done

Package and install checks

Needs review

Check package metadata and artifact integrity signals.

  • Install payload available

    Install or copy payload is available for review.

    Done
  • Package verification flag

    No package verification flag provided.

    Pending
  • Checksum metadata

    No checksum provided for downloaded artifact.

    Pending

Compare-driven decision checks

Needs review

Use compare context to validate trade-offs before adoption.

  • Compare tray has multiple entries

    Add at least one more entry to compare trust differences.

    Pending
  • Baseline comparison available

    No baseline peer selected yet.

    Pending
  • Diverging trust signals identified

    No major trust-signal divergence found.

    Pending

Setup at a glance

Copy & paste

Copy-ready — paste the snippet to get started.

Adoption plan

Balanced adoption plan

Current risk score 16/100. Use staged verification before broader rollout.

Risk 16

Pre-adoption checks

Validate source and review signals before any execution.

  • Confirm source provenanceRequired

    Source URL/provenance metadata is present.

    Done
  • Confirm metadata review state

    Listing has review metadata.

    Done
  • Verify install payload

    Install/config payload exists and can be inspected.

    Done

Security checks

Confirm safety, privacy, and package integrity signals.

  • Review safety notesRequired

    Safety notes are present.

    Done
  • Review privacy notesRequired

    Privacy notes are present.

    Done
  • Verify package integrity metadata

    No package verification/checksum metadata.

    Pending

Rollout

Adopt in controlled steps based on the selected plan.

  • Run in isolated sandbox firstRequired

    Use a constrained sandbox and observe behavior across multiple tasks.

    Pending
  • Roll out graduallyRequired

    Roll out to a small cohort before wider usage.

    Pending
  • Set monitoring and fallback

    Define rollback path and monitor errors after adoption.

    Pending

Evidence readiness

Evidence readiness matrix · balanced

Required evidence gates are covered (5/6 signals complete).

Risk 15

Source provenance

Present

Source repository/provenance is listed.

Required in this preset

Metadata review

Present

Review metadata is present.

Required in this preset

Safety notes

Present

Safety notes are present.

Required in this preset

Privacy notes

Present

Privacy notes are present.

Optional in this preset

Package integrity

Missing

Package integrity metadata is missing.

Optional in this preset

Install payload

Present

Install payload is available.

Required in this preset

Required evidence gates are covered for this preset.

Decision timeline

Decision timeline · balanced

5/6 steps complete with no blocking gaps for this preset.

Risk 14

triage

Confirm source provenanceRequired

Source/provenance metadata is available.

Done

triage

Check metadata review statusRequired

Review metadata is available.

Done

verify

Review safety notesRequired

Safety notes are available.

Done

verify

Review privacy notes

Privacy notes are available.

Done

verify

Validate package integrity metadata

Package integrity metadata is missing.

Pending

rollout

Verify install payload and commandsRequired

Install payload is available.

Done

No required blockers for this timeline preset.

Prerequisite readiness

Prerequisite readiness

3 prerequisites to line up before setup. Have accounts and credentials ready first. Includes a review or approval gate.

0/3 ready
Account & credentials2Review & approval1

Safety & privacy surface

Safety & privacy surface

3 safety and 3 privacy notes across 3 risk areas. Review closely: credentials & tokens, permissions & scopes, network access.

3 areas
  • SafetyNetwork accessActivepieces flows can send messages, call APIs, write records, publish webhooks, run code, and trigger cross-system side effects, so production flows need tests, approvals, rollback paths, and rate-limit controls.
  • SafetyPermissions & scopesThe built-in MCP server can let AI assistants build flows, manage tables, inspect runs, test automations, and publish changes; enable only the needed tool categories and keep project scope tight.
  • SafetyCredentials & tokensCustom TypeScript pieces and code steps should be reviewed like application code, especially when they handle secrets, filesystem access, network calls, or business-critical integrations.
  • PrivacyNetwork accessWorkflows can process prompts, customer records, emails, documents, form responses, table data, app payloads, webhooks, run logs, error traces, and AI-generated outputs.
  • PrivacyCredentials & tokensActivepieces connections may store OAuth tokens, API keys, account identifiers, webhook URLs, and service credentials; avoid exposing them in prompts, logs, MCP tool output, screenshots, or exported flows.
  • PrivacyNetwork accessSelf-hosted deployments still need retention, backup, database, Redis, worker isolation, outbound network, telemetry, and access-control policies for all flow and run data.

Disclosure: editorial

Safety notes

  • Activepieces flows can send messages, call APIs, write records, publish webhooks, run code, and trigger cross-system side effects, so production flows need tests, approvals, rollback paths, and rate-limit controls.
  • The built-in MCP server can let AI assistants build flows, manage tables, inspect runs, test automations, and publish changes; enable only the needed tool categories and keep project scope tight.
  • Custom TypeScript pieces and code steps should be reviewed like application code, especially when they handle secrets, filesystem access, network calls, or business-critical integrations.

Privacy notes

  • Workflows can process prompts, customer records, emails, documents, form responses, table data, app payloads, webhooks, run logs, error traces, and AI-generated outputs.
  • Activepieces connections may store OAuth tokens, API keys, account identifiers, webhook URLs, and service credentials; avoid exposing them in prompts, logs, MCP tool output, screenshots, or exported flows.
  • Self-hosted deployments still need retention, backup, database, Redis, worker isolation, outbound network, telemetry, and access-control policies for all flow and run data.

Prerequisites

  • Activepieces Cloud account or reviewed self-hosted deployment using Docker, Docker Compose, Kubernetes, or another supported hosting path.
  • Connected app credentials, OAuth grants, webhooks, tables, and flow permissions scoped to the automations being built.
  • Review policy for which flows an AI assistant or MCP client may create, modify, publish, test, retry, or disable.

Schema details

Install type
copy
Troubleshooting
No
Source repository stats
Scope
Source repo
Stars
22,776 source repo stars
Forks
3,803
Updated
2026-06-15T22:39:36Z
Tool listing metadata
Pricing
freemium
Disclosure
editorial
Application category
BusinessApplication
Operating system
Web, Docker, Kubernetes, Self-hosted
Full copyable content
## Editorial notes

Activepieces is useful for teams that want a self-hostable automation layer between Claude-adjacent agents and business systems without routing everything through a closed automation platform. It combines a visual flow builder, open-source TypeScript pieces, AI workflow support, human-in-the-loop steps, self-hosting options, and a built-in MCP server that can expose approved automation capabilities to Claude Desktop, Cursor, Windsurf, or Claude.ai connectors.

## Source notes

- The official docs describe Activepieces as an open-source all-in-one automation tool with AI-ready flows, TypeScript pieces, enterprise customization, self-hosted/network-gapped deployment, and human-in-the-loop steps.
- The installation overview says Activepieces Community Edition can be deployed with Docker, Docker Compose, and Kubernetes, and that Community Edition is free and open source.
- The MCP Server docs describe a built-in MCP server that lets AI assistants build flows, manage tables, test automations, inspect runs, and use OAuth-authenticated project-scoped tools.
- The GitHub repository describes Activepieces as an open-source replacement for Zapier, an AI automation platform with TypeScript pieces, MCP support for pieces, AI-first workflow features, and MIT-licensed Community Edition code with commercial enterprise features.

## Duplicate check

Checked current `content/tools/`, `content/mcp/`, guides, skills, agents, open pull requests, live HeyClaude `llms-full.txt`, and repository-wide content for `Activepieces`, `activepieces.com`, `github.com/activepieces/activepieces`, `workflow automation`, `Zapier`, `Make`, `n8n`, `Pipedream`, `Workato`, and `Windmill`. Existing n8n, Make, Pipedream, Workato, Zapier AI, Zapier MCP, and Workato MCP entries cover adjacent automation platforms or MCP connectors, but no Activepieces tools entry, Activepieces source URL duplicate, or open duplicate PR was found.

## Disclosure

Editorial listing. No paid placement or affiliate link is used.

About this resource

Editorial notes

Activepieces is useful for teams that want a self-hostable automation layer between Claude-adjacent agents and business systems without routing everything through a closed automation platform. It combines a visual flow builder, open-source TypeScript pieces, AI workflow support, human-in-the-loop steps, self-hosting options, and a built-in MCP server that can expose approved automation capabilities to Claude Desktop, Cursor, Windsurf, or Claude.ai connectors.

Source notes

  • The official docs describe Activepieces as an open-source all-in-one automation tool with AI-ready flows, TypeScript pieces, enterprise customization, self-hosted/network-gapped deployment, and human-in-the-loop steps.
  • The installation overview says Activepieces Community Edition can be deployed with Docker, Docker Compose, and Kubernetes, and that Community Edition is free and open source.
  • The MCP Server docs describe a built-in MCP server that lets AI assistants build flows, manage tables, test automations, inspect runs, and use OAuth-authenticated project-scoped tools.
  • The GitHub repository describes Activepieces as an open-source replacement for Zapier, an AI automation platform with TypeScript pieces, MCP support for pieces, AI-first workflow features, and MIT-licensed Community Edition code with commercial enterprise features.

Duplicate check

Checked current content/tools/, content/mcp/, guides, skills, agents, open pull requests, live HeyClaude llms-full.txt, and repository-wide content for Activepieces, activepieces.com, github.com/activepieces/activepieces, workflow automation, Zapier, Make, n8n, Pipedream, Workato, and Windmill. Existing n8n, Make, Pipedream, Workato, Zapier AI, Zapier MCP, and Workato MCP entries cover adjacent automation platforms or MCP connectors, but no Activepieces tools entry, Activepieces source URL duplicate, or open duplicate PR was found.

Disclosure

Editorial listing. No paid placement or affiliate link is used.

Source citations

Add this badge to your README

Show that Activepieces is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/tools/activepieces.svg)](https://heyclau.de/entry/tools/activepieces)

How it compares

Activepieces side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

1 trust signal differ across this comparison (Submitter).

Field

Open-source, self-hostable workflow automation platform with AI workflows, TypeScript pieces, human-in-the-loop steps, and a built-in MCP server.

Open dossier

Visual automation platform for building integrations, scenarios, API workflows, and AI-connected business processes.

Open dossier

Source-available workflow automation platform for self-hosted integrations, AI workflows, triggers, and data pipelines.

Open dossier

Open-source SDK and runtime for building, running, and managing agent platforms with agents, teams, workflows, memory, knowledge, tools, MCP, and AgentOS.

Open dossier
Next steps
Trust
Review statusReviewedMaintainer reviewedReviewedMaintainer reviewedReviewedMaintainer reviewedReviewedMaintainer reviewed
Package trustPackage not verifiedPackage not verifiedPackage not verifiedPackage not verified
Source provenanceSource-backedSource-backedSource-backedSource-backed
SubmitterDiffersoktofeesh1oktofeesh1
Install riskReview firstReview firstReview firstReview first
Notes Safety ✓ Privacy ✓ Safety · Privacy · Safety · Privacy · Safety ✓ Privacy ✓
BrandActivepieces logoActivepiecesMake logoMaken8n logon8nAgno logoAgno
Categorytoolstoolstoolstools
SourceSource-backedSource-backedSource-backedSource-backed
AuthorActivepiecesMaken8nAgno
Added2026-06-032026-04-272026-04-272026-06-03
Platforms
Harness
Source repo22.8k repo stars
Safety notesActivepieces flows can send messages, call APIs, write records, publish webhooks, run code, and trigger cross-system side effects, so production flows need tests, approvals, rollback paths, and rate-limit controls. The built-in MCP server can let AI assistants build flows, manage tables, inspect runs, test automations, and publish changes; enable only the needed tool categories and keep project scope tight. Custom TypeScript pieces and code steps should be reviewed like application code, especially when they handle secrets, filesystem access, network calls, or business-critical integrations.— missing— missingAgno agents are stateful control loops around stateless models, so model reasoning, tool calls, memory, knowledge retrieval, and workflow steps still require review before production use. Agents, teams, workflows, MCP tools, schedulers, and AgentOS APIs can call external systems, update databases, create memory, trigger background work, and expose capabilities to users or other agents. Agent memory and knowledge can make behavior more useful, but they can also preserve stale, incorrect, over-broad, or sensitive facts that influence future responses and actions. Human-in-the-loop approval, guardrails, tracing, RBAC, audit logs, and rollback paths should be configured before connecting Agno to billing, support, production data, infrastructure, or customer operations. MCP integrations discover tool schemas and let agents call third-party or internal services; review tool names, descriptions, arguments, auth headers, and permission scope before enabling them. Telemetry, tracing, evals, and AgentOS dashboards are operational signals, not proof that an agent platform is safe, compliant, accurate, or production-ready.
Privacy notesWorkflows can process prompts, customer records, emails, documents, form responses, table data, app payloads, webhooks, run logs, error traces, and AI-generated outputs. Activepieces connections may store OAuth tokens, API keys, account identifiers, webhook URLs, and service credentials; avoid exposing them in prompts, logs, MCP tool output, screenshots, or exported flows. Self-hosted deployments still need retention, backup, database, Redis, worker isolation, outbound network, telemetry, and access-control policies for all flow and run data.— missing— missingAgno agents can process prompts, messages, tool arguments, tool results, retrieved knowledge, memory content, session history, user identifiers, traces, metrics, schedules, and audit events. Memory features can automatically store user facts, preferences, inputs, topics, agent IDs, team IDs, and update timestamps in connected databases; define consent, retention, correction, and deletion workflows. AgentOS and agent APIs can centralize sessions, memory, traces, schedules, RBAC, and audit logs in infrastructure the operator controls, so database credentials, backups, access controls, and exports need normal review. Model providers, vector stores, embedder providers, MCP servers, and tools may receive user data or internal context depending on the agent configuration. Agno's telemetry documentation says anonymous usage data is collected about agents, teams, workflows, and AgentOS configurations, and documents `AGNO_TELEMETRY=false` plus per-instance telemetry disabling.
Prerequisites
  • Activepieces Cloud account or reviewed self-hosted deployment using Docker, Docker Compose, Kubernetes, or another supported hosting path.
  • Connected app credentials, OAuth grants, webhooks, tables, and flow permissions scoped to the automations being built.
  • Review policy for which flows an AI assistant or MCP client may create, modify, publish, test, retry, or disable.
— none listed— none listed
  • Python project, package manager, or deployment environment for installing Agno and running agents, teams, workflows, AgentOS services, or MCP integrations.
  • Model provider credentials, local model configuration, database, vector store, embedder, and tool credentials for the agents or workflows being built.
  • Reviewed database and storage plan for sessions, memory, chat history, traces, audit logs, schedules, agent state, and knowledge indexes.
  • Authentication, RBAC, network exposure, API, scheduling, and audit-log requirements before exposing AgentOS, agent APIs, or MCP-connected workflows to users.
Install
Config
Citations
ClaimUnclaimedUnclaimedUnclaimedUnclaimed
Open 4 picks in the interactive comparison tool

Related guides

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.