Activepieces is the project behind this setup. Local flows can work privately. Automations triggered by outside services need a stable public HTTPS address and careful secret handling.
- Recommended method
- Docker Compose
- Difficulty
- Intermediate
- Typical time
- 30–60 minutes
What you need
- Git, Docker and Docker Compose v2
- A persistent database
- A public HTTPS URL for webhooks
- Test accounts for connected services
Set it up
Clone and generate configuration
Use the official deployment helper to generate the environment file.
git clone https://github.com/activepieces/activepieces.git cd activepieces sh tools/deploy.shSet the frontend URL
Configure AP_FRONTEND_URL to the real HTTPS address before testing external triggers.
Start the stack
Launch Activepieces with Compose v2.
docker compose -p activepieces up -dBuild one harmless flow
Use a test trigger and a reversible action. Confirm authentication and inspect the run log.
Test failure behavior
Disable one credential temporarily and confirm retries, errors and alerts are understandable.
Advertisement
Reserved for launch
Verify it works
Do not call the setup finished until these small tests pass:
- The frontend uses the final URL
- A test webhook reaches the flow
- Secrets do not appear in logs
- A failed run can be retried safely
Protect the service
- Use least-privilege API keys
- Do not use temporary tunnels in production
- Back up the database and encryption secrets together
- Review connected-service charges even when Activepieces is free
Official resources
Videos are supplemental. Use the official documentation for current commands, versions and security guidance.