Activepieces (BYOK) — connector documentation

MCP endpoint: https://byok-activepieces.connectorbay.com/mcp
REST API: POST https://byok-activepieces.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-activepieces.connectorbay.com/openapi.json
Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
Authentication: your own Activepieces platform API key, sent in the X-Upstream-Key header of every request (never stored, logged or cached)
Health: https://byok-activepieces.connectorbay.com/health · Tool schemas: https://byok-activepieces.connectorbay.com/tools.json
Publisher: Unify Dynamics LLC · connectorbay.com/byok-activepieces · agent@connectorbay.com

What Activepieces (BYOK) is for

Activepieces (BYOK) lets an AI assistant read your own Activepieces data through the Activepieces API with a key you supply (platform API key). Read-only: 9 tools (list_projects, list_flows, list_flow_runs, get_flow_run, count_flow_runs_by_status, list_tables, list_connections, list_variables, list_platform_users). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to cloud.activepieces.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Activepieces. Activepieces and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

"Which Activepieces projects do we have?"
"Which flows in project X are enabled?"
"Which flow runs failed in project X today?"
"What happened in flow run abcdefghij0123456789a?"
"How many flow runs succeeded and failed in project X this week?"
"What Activepieces tables does project X have?"

What it does

list_projects: List the projects of the platform with name, type and analytics counts of users and flows.
list_flows: List the flows of a project with status, current version name, validity and last update.
list_flow_runs: List flow runs of a project, newest first, with flow name, status, start and finish time, failed step and step count. Step inputs and outputs are not returned.
get_flow_run: Get one flow run: status, flow name, timing, failed step and step count. Step data is not returned.
count_flow_runs_by_status: Count a project's flow runs per status (succeeded, failed, running and so on), optionally within a time window.
list_tables: List the tables (built-in database) of a project with name, folder and creation time.
list_connections: List a project's app connections with name, app (piece), type and status. Credentials are not returned.
list_variables: List the names of a project's variables (values are not returned here).
list_platform_users: List the platform's users with name, email, role, status and last active time.

BYOK key

You bring your own Activepieces platform API key (https://cloud.activepieces.com/). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to cloud.activepieces.com over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

https://www.activepieces.com/docs/endpoints/overview (the API this connector calls, with a BYOK key)

Live from the Activepieces API (cloud.activepieces.com) with a BYOK key; documentation: https://www.activepieces.com/docs/endpoints/overview. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Activepieces. Activepieces and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Activepieces account.

Built for: Worldwide. Languages: English.