feat(activepieces): Zenrows piece for Activepieces, as a code host

.github/workflows/activepieces.yml

@@ -0,0 +1,43 @@
+name: Activepieces piece
+
+on:
+  push:
+    branches: [main]
+    paths:
+      - platforms/activepieces/**
+      - dist/activepieces/**
+      - shared/text/**
+      - scripts/**
+      - .github/workflows/activepieces.yml
+  pull_request:
+    paths:
+      - platforms/activepieces/**
+      - dist/activepieces/**
+      - shared/text/**
+      - scripts/**
+      - .github/workflows/activepieces.yml
+
+permissions:
+  contents: read
+
+jobs:
+  check:
+    name: Lint, build and test in activepieces
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+      - uses: actions/setup-node@949feb2413d6458794dcd2491c4babbbce0c15c1 # v7.1.0
+        with:
+          node-version: 24
+      - run: npm ci
+      # activepieces' packageManager at the pinned commit. If they differ,
+      # check.sh installs the right version instead.
+      - uses: oven-sh/setup-bun@0c5077e51419868618aeaa5fe8019c62421857d6 # v2.2.0
+        with:
+          bun-version: "1.4.0"
+      - uses: actions/cache@55cc8345863c7cc4c66a329aec7e433d2d1c52a9 # v6.1.0
+        with:
+          path: ~/.bun/install/cache
+          key: bun-activepieces-${{ hashFiles('platforms/activepieces/vars.yaml') }}
+          restore-keys: bun-activepieces-
+      - run: platforms/activepieces/scripts/check.sh

CONTRIBUTING.md

@@ -53,7 +53,7 @@ A fact that more than one place states (what an error code means, what a request
 
 ## Code hosts
 
-`kind: code` in `vars.yaml` makes a host whose output isn't a plugin but files for somewhere else: code for another project (a piece as it sits in that project's repo), or a listing a marketplace reads. A code host ships only its own files, with `{{…}}` filled in source files too: no shared skills, `LICENSE` or assets, and no `plugin.json`. Its `README.md` documents it here and isn't shipped or rendered; `npm run validate` requires one, and the render fails if the host has a `skills/` folder. It needs no release-please entry until it's released from this repo.
+`kind: code` in `vars.yaml` makes a host whose output isn't a plugin but files for somewhere else: code for another project (a piece as it sits in that project's repo), or a listing a marketplace reads. A code host ships only its own files, with `{{…}}` filled in source files too: no shared skills, `LICENSE` or assets, and no `plugin.json`. Its `README.md` documents it here and isn't shipped or rendered; `npm run validate` requires one, and the render fails if the host has a `skills/` folder. It needs no release-please entry until it's released from this repo. If it's code, its `scripts/check.sh` can build and test `dist/<host>/` the way the target project does, run by its own workflow (`platforms/activepieces/` does).
 
 ## Tests
 

README.md

@@ -9,6 +9,7 @@ Each host's guide covers installing the plugin and signing in to Zenrows. You si
 <!-- hosts:start (generated by npm run render from platforms/; don't edit) -->
 | Host | Setup guide |
 |---|---|
+| Activepieces | [platforms/activepieces/README.md](platforms/activepieces/README.md) |
 | GitHub Copilot | [dist/copilot/README.md](dist/copilot/README.md) |
 <!-- hosts:end -->