Add Activepieces integration for workflow automation

- Add Activepieces fork with SmoothSchedule custom piece
- Create integrations app with Activepieces service layer
- Add embed token endpoint for iframe integration
- Create Automations page with embedded workflow builder
- Add sidebar visibility fix for embed mode
- Add list inactive customers endpoint to Public API
- Include SmoothSchedule triggers: event created/updated/cancelled
- Include SmoothSchedule actions: create/update/cancel events, list resources/services/customers

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
poduck
2025-12-18 22:59:37 -05:00
parent 9848268d34
commit 3aa7199503
16292 changed files with 1284892 additions and 4708 deletions

View File

@@ -0,0 +1,30 @@
---
title: "Overview"
icon: "cube"
---
At Activepieces, we take a unique approach to customer support. Instead of having dedicated support staff, our full-time engineers handle support requests on rotation. This ensures you get expert technical help from the people who build the product.
### Support Schedule
Our on-call engineer handles customer support as part of their rotation. For more details about how this works, check out our on-call documentation.
### Support Channels
- Community Support
- GitHub Issues: We actively monitor and respond to issues on our [GitHub repository](https://github.com/activepieces/activepieces)
- Community Forum: We engage with users on our [Community Platform](https://community.activepieces.com/) to provide help and gather feedback
- Email: only for account related issues, delete account request or billing issues.
- Enterprise Support
- Enterprise customers receive dedicated support through Slack
- We use [Pylon](https://usepylon.com) to manage support tickets and customer channels efficiently
- For detailed information on using Pylon, see our [Pylon Guide](/handbook/customer-support/pylon)
### Support Hours & SLA:
<Warning>
Work in progress—coming soon!
</Warning>