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/build-pieces/sharing-pieces/community.mdx

@@ -0,0 +1,32 @@
+---
+title: "Community (Public NPM)"
+description: "Learn how to publish your piece to the community."
+---
+
+You can publish your pieces to the npm registry and share them with the community. Users can install your piece from Settings -> My Pieces -> Install Piece -> type in the name of your piece package.
+
+<Steps>
+  <Step title="Login to npm">
+    Make sure you are logged in to npm. If not, please run:
+    ```bash
+    npm login
+    ```
+  </Step>
+  <Step title="Rename Piece">
+    Rename the piece name in `package.json` to something unique or related to your organization's scope (e.g., `@my-org/piece-PIECE_NAME`). You can find it at `packages/pieces/PIECE_NAME/package.json`.
+    <Tip>
+    Don't forget to increase the version number in `package.json` for each new release.
+    </Tip>
+  </Step>
+  <Step title="Publish">
+    <Tip>
+    Replace `PIECE_FOLDER_NAME` with the name of the folder.
+    </Tip>
+    Run the following command:
+    ```bash
+    npm run publish-piece PIECE_FOLDER_NAME
+    ```
+  </Step>
+</Steps>
+
+**Congratulations! You can now import the piece from the settings page.**

activepieces-fork/docs/build-pieces/sharing-pieces/contribute.mdx

@@ -0,0 +1,17 @@
+---
+title: "Contribute"
+description: "Learn how to contribute a piece to the main repository."
+---
+
+<Steps>
+   <Step title="Open a pull request">
+     - Build and test your piece.
+     - Open a pull request from your repository to the main fork.
+     - A maintainer will review your work closely.
+   </Step>
+   <Step title="Merge the pull request">
+   - Once the pull request is approved, it will be merged into the main branch.
+   - Your piece will be available within a few minutes.
+   - An automatic GitHub action will package it and create an npm package on npmjs.com.
+   </Step>
+</Steps>

activepieces-fork/docs/build-pieces/sharing-pieces/overview.mdx

@@ -0,0 +1,9 @@
+---
+title: "Overview"
+description: "Learn the different ways to publish your own piece on activepieces."
+---
+
+## Methods
+- [Contribute Back](/build-pieces/sharing-pieces/contribute): Publish your piece by contributing back your piece to main repository.
+- [Community](/build-pieces/sharing-pieces/community): Publish your piece on npm directly and share it with the community.
+- [Private](/build-pieces/sharing-pieces/private): Publish your piece on activepieces privately.

activepieces-fork/docs/build-pieces/sharing-pieces/private.mdx

@@ -0,0 +1,34 @@
+---
+title: "Private"
+description: "Learn how to share your pieces privately."
+---
+
+<Snippet file="enterprise-feature.mdx" />
+
+This guide assumes you have already created a piece and created a private fork of our repository, and you would like to package it as a file and upload it.
+
+<Tip>
+Friendly Tip: There is a CLI to easily upload it to your platform. Please check out [Publish Custom Pieces](../misc/publish-piece).
+</Tip>
+
+
+
+<Steps>
+    <Step title="Build Piece">
+        Build the piece using the following command. Make sure to replace `${name}` with your piece name.
+
+        ```bash
+        npm run pieces -- build --name=${name}
+        ```
+
+        <Info>
+        More information about building pieces can be found [here](../misc/build-piece).
+        </Info>
+    </Step>
+    <Step title="Upload Tarball">
+        Upload the generated tarball inside `dist/packages/pieces/${name}`from Activepieces Platform Admin -> Pieces
+    
+        ![Manage Pieces](/resources/screenshots/install-piece.png)
+
+    </Step>
+</Steps>