data

Call data.run_row_action

Press a row's button in a Data table, as a member clicking it would — 'process the Acme meeting', 'run the research button on that row'. A button is a column of type action (data.api_describe lists them); pressing it starts every automation built on its event with the row as input, and those may spend credits or send what they were built to send. It answers in two calls: without confirmation_id it proposes, names the table, button and row, and presses nothing; the same call again with that confirmation_id, on a member's own API key, presses it once. Not for adding a row — that is data.api_append.

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/data.run_row_action

Request

  • Base URL: https://app.goosybear.ai
  • URL: https://app.goosybear.ai/api/v1/tools/data.run_row_action
  • 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

table_idstring uuid required

The table whose row button is pressed.

row_idstring uuid required

The row the button is pressed on, as data.query returned it.

column_keystring required

The key of the table's action column — the button. data.describe lists it with type: action and the event it sends.

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

No recorded changes to this operation across all 6 revisions of this API.