Activepieces is an open-source automation platform that lets you connect apps, build agents and automate workflows with natural language
The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
Scored across 48 tools
Most tools have clearly distinct purposes (flow CRUD, step CRUD, table/record CRUD, discovery, validation, runs), and descriptions explicitly carve out boundaries like ap_add_step vs ap_update_step vs ap_build_flow. A few layered discovery/execution tools (ap_search_actions, ap_research_pieces, ap_get_piece_props; ap_test_flow, ap_test_step, ap_run_action) could still be confused by an agent that does not read the detailed guidance.
The set follows a strong ap_verb_noun snake_case convention throughout (ap_create_flow, ap_delete_step, ap_list_runs, ap_update_record, etc.). Minor deviations exist in noun-phrase tools like ap_flow_structure and ap_setup_guide, and one compound verb in ap_lock_and_publish, but the overall pattern is predictable.
At 48 tools this is a heavy surface, well beyond the typical 3–15 well-scoped range. While the underlying platform is complex enough to justify consolidation, many operations are split across granular tools (step read/write, branch handling, validation, discovery) and would benefit from grouping.
Coverage is strong across flow lifecycle (create, build, update, test, validate, publish, duplicate, delete), step and trigger management, router branches, folders, tables/records/fields, notes, runs, and piece discovery. Minor gaps remain around connection lifecycle (only ap_list_connections and setup guidance, no create/delete connection) and folder/note deletion specifics, but core workflows are covered.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
ap_run_action1 field changedInput schema / requiredPrevious value: -[
- "pieceName",
- "actionName"
-]New value: +[
+ "pieceName",
+ "actionName",
+ "input"
+]ap_update_step1 field changedInput schema / properties / pieceVersionAdded value: +{
+ "anyOf": [
+ {
+ "const": "latest",
+ "type": "string"
+ },
+ {
+ "pattern": "^[0-9]+\\.[0-9]+\\.[0-9]+$",
+ "type": "string"
+ }
+ ],
+ "description": "For PIECE steps: move the step to another version of its piece. Pass \"latest\" or an exact version like \"1.2.3\". Inputs the new version no longer has are dropped, so pass the adjusted input in the same call."
+}ap_run_action1 field changedInput schema / requiredPrevious value: -[
- "pieceName",
- "actionName",
- "input"
-]New value: +[
+ "pieceName",
+ "actionName"
+]ap_add_step1 field changedInput schema / properties / auth / descriptionPrevious value: -"Connection externalId from ap_list_connections. Auto-wrapped as {{connections['externalId']}}."New value: +"Connection externalId from ap_list_connections. Pass the plain id, not a template."ap_run_action2 fields changedInput schema / properties / connectionExternalId / descriptionPrevious value: -"externalId from ap_list_connections. Required if the piece needs auth. Auto-wrapped as {{connections['externalId']}}."New value: +"externalId from ap_list_connections. Required if the piece needs auth. Pass the plain id, not a template."Input schema / requiredPrevious value: -[
- "pieceName",
- "actionName"
-]New value: +[
+ "pieceName",
+ "actionName",
+ "input"
+]ap_update_step1 field changedInput schema / properties / auth / descriptionPrevious value: -"Connection `externalId` from `ap_list_connections`. The tool wraps it automatically as `{{connections['externalId']}}`."New value: +"Connection `externalId` from `ap_list_connections`. Pass the plain id, not a template."ap_update_trigger1 field changedInput schema / properties / auth / descriptionPrevious value: -"Connection `externalId` from `ap_list_connections`. The tool wraps it automatically as `{{connections['externalId']}}`."New value: +"Connection `externalId` from `ap_list_connections`. Pass the plain id, not a template."ap_run_action1 field changedInput schema / requiredPrevious value: -[
- "pieceName",
- "actionName",
- "input"
-]New value: +[
+ "pieceName",
+ "actionName"
+]ap_run_action1 field changedInput schema / requiredPrevious value: -[
- "pieceName",
- "actionName"
-]New value: +[
+ "pieceName",
+ "actionName",
+ "input"
+]ap_list_foldersap_move_flow_to_folderap_build_flow1 field changedInput schema / properties / folderName / descriptionPrevious value: -"Name of an existing folder to place it in. For a solution of several flows and tables, create the folder once with ap_create_folder, then pass the same folderName to each of them."New value: +"Name of an existing folder to place it in. For a solution of several flows and tables, create the folder with ap_create_folder in an earlier step than the calls that use it (never in the same step, they run at once), then pass the same folderName to each of them."ap_create_flow1 field changedInput schema / properties / folderName / descriptionPrevious value: -"Name of an existing folder to place it in. For a solution of several flows and tables, create the folder once with ap_create_folder, then pass the same folderName to each of them."New value: +"Name of an existing folder to place it in. For a solution of several flows and tables, create the folder with ap_create_folder in an earlier step than the calls that use it (never in the same step, they run at once), then pass the same folderName to each of them."ap_create_table1 field changedInput schema / properties / folderName / descriptionPrevious value: -"Name of an existing folder to place it in. For a solution of several flows and tables, create the folder once with ap_create_folder, then pass the same folderName to each of them."New value: +"Name of an existing folder to place it in. For a solution of several flows and tables, create the folder with ap_create_folder in an earlier step than the calls that use it (never in the same step, they run at once), then pass the same folderName to each of them."ap_research_pieces1 field changedInput schema / properties / forIntent / descriptionPrevious value: -"What you are trying to do (e.g. \"list all my open deals\"). When set, each piece also returns recommendedActions — the actions whose AI guidance best matches your intent — so you can pick the right action in one shot. Advisory only; the full action list is always returned."New value: +"What you are trying to do (e.g. \"list all my open deals\"). When set, each piece also returns recommendedActions — the actions whose AI guidance best matches your intent — so you can pick the right action in one shot. Every action and trigger is still listed, but only the ones matching your intent carry their full description."ap_build_flow1 field changedInput schema / properties / folderNameAdded value: +{
+ "description": "Name of an existing folder to place it in. For a solution of several flows and tables, create the folder once with ap_create_folder, then pass the same folderName to each of them.",
+ "maxLength": 255,
+ "minLength": 1,
+ "type": "string"
+}ap_create_flow1 field changedInput schema / properties / folderNameAdded value: +{
+ "description": "Name of an existing folder to place it in. For a solution of several flows and tables, create the folder once with ap_create_folder, then pass the same folderName to each of them.",
+ "maxLength": 255,
+ "minLength": 1,
+ "type": "string"
+}ap_create_folderap_create_table1 field changedInput schema / properties / folderNameAdded value: +{
+ "description": "Name of an existing folder to place it in. For a solution of several flows and tables, create the folder once with ap_create_folder, then pass the same folderName to each of them.",
+ "maxLength": 255,
+ "minLength": 1,
+ "type": "string"
+}ap_run_action1 field changedInput schema / requiredPrevious value: -[
- "pieceName",
- "actionName",
- "input"
-]New value: +[
+ "pieceName",
+ "actionName"
+]ap_validate_flow3 fields changedInput schema / properties / flowId / descriptionPrevious value: -"The id of the flow to validate. Use ap_list_flows to find it."New value: +"The id of one flow to validate. Use ap_list_flows to find it."Input schema / properties / folderNameAdded value: +{
+ "description": "The folder holding a solution of several flows and tables (as created with ap_create_folder), to validate all of them and the connections between them.",
+ "maxLength": 255,
+ "minLength": 1,
+ "type": "string"
+}Input schema / requiredRemoved value: -[
- "flowId"
-]ap_run_action1 field changedInput schema / requiredPrevious value: -[
- "pieceName",
- "actionName"
-]New value: +[
+ "pieceName",
+ "actionName",
+ "input"
+]ap_run_action1 field changedInput schema / requiredPrevious value: -[
- "pieceName",
- "actionName",
- "input"
-]New value: +[
+ "pieceName",
+ "actionName"
+]ap_run_action1 field changedInput schema / requiredPrevious value: -[
- "pieceName",
- "actionName"
-]New value: +[
+ "pieceName",
+ "actionName",
+ "input"
+]ap_run_action1 field changedInput schema / requiredPrevious value: -[
- "pieceName",
- "actionName",
- "input"
-]New value: +[
+ "pieceName",
+ "actionName"
+]ap_add_branchap_add_stepap_build_flowap_change_flow_statusap_create_flowap_create_tableap_delete_branchap_delete_flowap_delete_recordsap_delete_stepap_delete_tableap_duplicate_flowap_find_recordsap_flow_structureap_get_piece_propsap_get_runap_insert_recordsap_list_ai_modelsap_list_connectionsap_list_flowsap_list_runsap_list_tablesap_lock_and_publishap_manage_fieldsap_manage_notesap_read_step_codeap_read_step_settingsap_rename_flowap_research_piecesap_resolve_property_chainap_resolve_property_optionsap_retry_runap_run_actionap_search_actionsap_search_triggersap_set_project_contextap_setup_guideap_test_flowap_test_stepap_update_branchap_update_recordap_update_stepap_update_triggerap_validate_flowap_validate_step_config
Add one secure layer between your agents and this server.