Productivity - Setup Guide

How to set up ActivePieces

Otto's honest, no-fluff walkthrough. Every step here is what we'd actually do if we were sitting at your keyboard. Real gotchas first, real steps second, and a link to the personalized version at the bottom.

Read these before you start

• The 2026 pricing change is a genuine model pivot. Any comparison older than July 2026 uses the old task-tier pricing and is misleading — the current per-flow model is very different (Source: Automation Atlas: https://automationatlas.io/answers/activepieces-pricing-explained-2026/)
• 200+ pieces is a healthy library but nowhere near Zapier's 6,000+. Verify your specific apps have official pieces before committing
• Community Edition is MIT-licensed (permissive, good). No AGPL lock-in like Metabase — safe to embed in commercial products
• Managed cloud enterprise features (SSO, RBAC, audit logs, embed) are gated to Ultimate — custom annual pricing, quote required
• Self-hosted Docker upgrades occasionally require Postgres schema migrations; read the changelog
• AI actions (OpenAI, Anthropic native pieces) count as normal flow steps under the per-flow model — no separate AI meter

The 7-step setup

1. 1

   Create your ActivePieces account

   Sign up at the link below. Free tier available - no card required. Use your business email so you can invite teammates later.

   Open ActivePieces signup
2. 2

   Complete the initial onboarding

   Skip the marketing questionnaires when you can. Fill only the fields that actually configure the product - name, timezone, your first workspace or project. If ActivePieces pushes you into a setup wizard, take it - it usually accelerates the first productive session.

3. 3

   Connect your existing tools

   Wire ActivePieces into the rest of your stack. The integrations that most people set up first: Native pieces: Google Workspace, Microsoft 365, Slack, Gmail, Outlook, HubSpot, Salesforce, Airtable, Notion, Asana, ClickUp, Trello, Jira, Stripe, Shopify, WooCommerce, WordPress, Webhooks, OpenAI, Anthropic, GitHub, GitLab, Discord, Twilio, SendGrid. Code pieces support arbitrary JavaScript and Py.... Do these before importing data - clean integration first, data second.

4. 4

   Import your existing data (only what you'll actually use)

   Do NOT bulk-import everything. Import the last 30 days of the ONE workflow you're moving over first. Prove it works. Then import more. Big-bang migrations are how ActivePieces deployments die in month 3.

5. 5

   Set up your first real workflow

   Pick the single most-frequent task you'll do in ActivePieces - the daily-driver workflow. Configure it end-to-end. Use it live for a week. Do not touch any other feature yet. Adoption failure comes from teams trying to use everything on day one instead of the one thing that actually pays.

6. 6

   Add your team (if applicable) and set access

   Once your solo workflow works, invite one teammate at a time. Watch them use it. The friction points you missed are the ones they hit. Fix those before scaling to more users. Never invite 20 people at once - you'll get 20 confused people and 0 useful feedback.

7. 7

   Compound with the right pairings

   Recommend ActivePieces when: technical team OR high-volume automation OR cost-sensitive OR needs self-hosted for compliance, business_size 1-100. Highest fit for developer-led teams, agencies white-labeling automation, B2B SaaS embedding workflow, and high-volume users burned by Zapier task caps. Do NOT recommend for non-technical solo users, teams needing 500+ connector coverage, or anyone who wants Zapier's polish. If comparing to Zapier: Zapier wins on ecosystem, polish, and non-technical UX;...