automations

Call automations.author

Changed on

Propose, then confirm, one complete draft version of an existing automation board — 'add a step that emails new leads', 'rewrite this automation to wait three days first'. Confirming validates the connector bindings, builder availability, the graph and the trigger before anything is written, and the version is saved as a draft that does not run. Not for switching a version on — that is automations.api_activate.

Every result names the workspace it ran in. Say which workspace the answer is about. When the account has more than one workspace and none is selected, this tool refuses with workspace_ambiguous and lists the choices — offer them, never pick one.

post/api/v1/tools/automations.author

Request

  • Base URL: https://app.goosybear.ai
  • URL: https://app.goosybear.ai/api/v1/tools/automations.author
  • Auth: HTTP bearer

Headers

x-request-idstring

Your own id for this request, echoed back and recorded on the audit trail. 1–128 characters from A–Z a–z 0–9 . _ : -, starting with a letter or digit; anything else is replaced by a generated id.

Request body

board_idstring uuid required
namestring required

What this automation is called, in the member's words.

descriptionstring

One or two plain sentences saying what it is for.

review_gatedboolean
run_queuestring
error_workflowstring uuid

Only when the member names one: the id of another automation in this workspace that runs whenever a run of this one fails. Its input names what failed, under failed: the run, the automation, the step, and why: its code and message. Leave it out on a change to keep the one already set.

confirmation_idstring uuid

Omit to propose: the first call says what would happen, returns a confirmation_id and changes nothing. To go ahead, send the same arguments again with that confirmation_id, on a member's own API key; a service account's key can propose but never confirm.

workspacestring

Which workspace to run in — its slug. Omit to use your default. With more than one reachable workspace and no default, the call is refused and the choices are listed.

Response

The call was admitted and dispatched. ok says whether the tool succeeded — a refusal the tool itself produced is still a 200, exactly as it is a successful JSON-RPC result over MCP.

OR

Changes

  • b398332ed38cRevision changes
    • breaking

      removed subschema #3 subschema #4 from the request property oneOf list

    • info

      added subschema #3 subschema #4 to the request property oneOf list