Skip to main content

Workflow Tools

AnyDB MCP can inspect existing automations, discover the workflow capabilities supported by the running server, create or update workflows, execute them, and review their history.

Available tools​

ToolWhat it does
anydb_list_workflowsLists normalized workflow graphs in a workspace.
anydb_get_workflowGets one workflow graph, its stored configuration, and retained execution details.
anydb_get_workflow_execution_historyGets retained executions for a workflow with status, inputs, outputs, and errors.
anydb_list_workflow_triggersLists supported triggers and their exact configuration and output schemas.
anydb_list_workflow_actionsLists registered actions, exact schemas, compatibility, license availability, and script guidance.
anydb_create_workflowCreates a workflow with one trigger and an ordered action chain.
anydb_update_workflowUpdates workflow metadata or replaces the complete ordered action chain.
anydb_update_workflow_triggerEdits an existing trigger's settings without replacing the workflow, trigger ID, or action chain.
anydb_delete_workflowPermanently deletes a workflow, including its trigger and actions.
anydb_execute_workflowSimulates or executes a workflow by ID or name, including workflows invoked by button cells.
  1. Read the authoring guide with anydb_get_authoring_guide.
  2. Call anydb_list_workflows to avoid creating a duplicate.
  3. Call anydb_list_workflow_triggers and anydb_list_workflow_actions for the running server's supported schemas.
  4. Create the workflow disabled and use validateOnly: true when available.
  5. Run a representative execution with simulate: true.
  6. Execute one real representative case when safe.
  7. Inspect anydb_get_workflow_execution_history for outputs and errors before enabling the workflow.

Update an existing workflow​

Omit changes.actions to preserve the current action chain. To add, edit, remove, or reorder actions, send the entire desired final chain. Missing actions or configuration values are removed.

Before revising a script action, read its source from anydb_get_workflow and consult the action_script entry returned by anydb_list_workflow_actions. That catalog is the authoritative reference for the running server's script APIs and rules.

Update a trigger​

Call anydb_get_workflow first and send its complete trigger.config with your changes to anydb_update_workflow_trigger. Omitted properties are removed. Record triggers use templateName, optional fieldNames, parentRecordId, and filter; other triggers use the native config that anydb_get_workflow returns. This tool does not change the trigger type and does not enable the workflow.

Delete a workflow​

anydb_delete_workflow is permanent. Read the workflow first and delete it only when asked. To stop a workflow without deleting it, call anydb_update_workflow with changes.enabled set to false. Protected workflows cannot be deleted.

Execute a button workflow​

A button cell stores its workflow name in BUTTON_ACTION_VALUE. To invoke it through MCP:

  1. Read the record with get_record.
  2. Find the button cell and its BUTTON_ACTION_VALUE.
  3. Call anydb_execute_workflow with that value as workflowName and the record ID as adoid.

Button visibility and locked-state properties affect the AnyDB interface but are not enforced by the MCP execution call. Check those properties yourself when they matter.