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>

activepieces-fork/docs/install/troubleshooting/bullboard.mdx

@@ -0,0 +1,71 @@
+---
+title: "Queues Dashboard"
+icon: "gauge-high"
+---
+
+The Bull Board is a tool that allows you to check issues with scheduling and internal flow runs issues.
+
+![BullBoard Overview](https://raw.githubusercontent.com/felixmosh/bull-board/master/screenshots/overview.png)
+
+## Setup BullBoard
+
+To enable the Bull Board UI in your self-hosted installation:
+
+1. Define these environment variables:
+   - `AP_QUEUE_UI_ENABLED`: Set to `true`
+   - `AP_QUEUE_UI_USERNAME`: Set your desired username
+   - `AP_QUEUE_UI_PASSWORD`: Set your desired password
+
+2. Access the UI at `/api/ui`
+
+
+<Tip>
+For cloud installations, please ask your team for access to the internal documentation that explains how to access BullBoard.
+</Tip>
+
+## Queue Overview
+
+We have one main queue called `workerJobs` that handles all job types. Each job has a `jobType` field that tells us what it does:
+
+### Low Priority Jobs
+
+#### RENEW_WEBHOOK
+Renews webhooks for pieces that have webhooks channel with expiration like Google Sheets.
+
+#### EXECUTE_POLLING
+Checks external services for new data at regular intervals.
+
+### Medium Priority Jobs
+
+#### EXECUTE_FLOW
+Runs flows when they're triggered.
+
+#### EXECUTE_WEBHOOK
+Processes incoming webhook requests that start flow runs.
+
+#### DELAYED_FLOW
+Runs flows that were scheduled for later, like paused flows or delayed executions.
+
+### High Priority Jobs
+
+#### EXECUTE_PROPERTY
+Loads dynamic properties for pieces that need them at runtime.
+
+#### EXECUTE_EXTRACT_PIECE_INFORMATION
+Gets information about pieces when they're being installed or set up.
+
+#### EXECUTE_VALIDATION
+Checks that flow settings, inputs, or data are correct before running.
+
+#### EXECUTE_TRIGGER_HOOK
+Runs special logic before or after triggers fire.
+
+
+<Info>
+Failed jobs are not normal and need to be checked right away to find and fix what's causing them. 
+They require immediate investigation as they represent executions that failed for unknown reasons that could indicate system issues.
+</Info>
+
+<Tip>
+Delayed jobs represent either paused flows scheduled for future execution, upcoming polling job iterations, or jobs being retried due to temporary failures. They indicate an internal system error occurred and the job will be retried automatically according to the backoff policy.
+</Tip>

activepieces-fork/docs/install/troubleshooting/reset-password.mdx

@@ -0,0 +1,37 @@
+---
+title: "Reset Password"
+description: "How to reset your password on a self-hosted instance"
+icon: "key"
+---
+
+If you forgot your password on a self-hosted instance, you can reset it using the following steps:
+
+1. **Locate PostgreSQL Docker Container**:
+   - Use a command like `docker ps` to find the PostgreSQL container.
+
+2. **Access the Container**:
+   - Use SSH to access the PostgreSQL Docker container.
+   ```bash
+   docker exec -it POSTGRES_CONTAINER_ID /bin/bash
+   ```
+
+3. **Open the PostgreSQL Console**:
+   - Inside the container, open the PostgreSQL console with the `psql` command.
+   ```bash
+   psql -U postgres
+   ```
+
+4. **Connect to the ActivePieces Database**:
+   - Connect to the ActivePieces database.
+   ```sql
+   \c activepieces
+   ```
+
+5. **Create a Secure Password**:
+   - Use a tool like [bcrypt-generator.com](https://bcrypt-generator.com/) to generate a new secure password, number of rounds is 10.
+
+6. **Update Your Password**:
+   - Run the following SQL query within the PostgreSQL console, replacing `HASH_PASSWORD` with your new password and `YOUR_EMAIL_ADDRESS` with your email.
+   ```sql
+   UPDATE public.user_identity SET password='HASH_PASSWORD' WHERE email='YOUR_EMAIL_ADDRESS';
+   ```

activepieces-fork/docs/install/troubleshooting/truncated-logs.mdx

@@ -0,0 +1,35 @@
+---
+title: "Truncated Logs"
+description: "Understanding and resolving truncated flow run logs"
+icon: "file-lines"
+---
+
+## Overview
+
+If you see `(truncated)` in the flow run logs, it means the logs have exceeded the maximum allowed file size.
+
+## How It Works
+
+There is a current limitation where the log file of a run cannot grow past a certain size. When this limit is reached, the engine automatically removes the largest keys in the JSON output until it fits within the allowed size.
+
+<Note>
+**This does not affect flow execution.** Your flow will continue to run normally even when logs are truncated.
+</Note>
+
+## Known Limitation
+
+There is one known issue with truncated logs:
+
+If you **pause** a flow, then **resume** it, and the resumed step references data from a truncated step, the flow will fail because the referenced data is no longer available in the logs.
+
+## Solution
+
+You can increase the `AP_MAX_FILE_SIZE_MB` environment variable to a higher value to allow larger log files:
+
+```bash
+AP_MAX_FILE_SIZE_MB=50
+```
+
+<Info>
+**Future Improvement:** There is a planned enhancement to change this limit from per-log-file to per-step, which will provide more granular control over log sizes. This feature is currently in the planning phase.
+</Info>

activepieces-fork/docs/install/troubleshooting/websocket-issues.mdx

@@ -0,0 +1,17 @@
+---
+title: "Websocket Issues"
+description: "Troubleshoot websocket connection problems"
+icon: "plug"
+---
+
+If you're experiencing issues with websocket connections, it's likely due to incorrect proxy configuration. Common symptoms include:
+
+- Test Flow button not working
+- Test step in flows not working
+- Real-time updates not showing
+
+To resolve these issues:
+
+1. Ensure your reverse proxy is properly configured for websocket connections
+2. Check our [Setup HTTPS](/install/guides/setup-ssl) guide for correct configuration examples
+3. Some browsers block http websocket connections, please setup SSL to resolve this issue.