Compound Actions
platform.extensions.compound-actions
A compound action runs several steps without the user in the loop: actions, scripts, branches, loops and parallel steps. Use it for orchestration, and for the body of a system plugin.
To learn what compound actions do, see Compound Actions in the Tool Studio docs.
- Endpoint:
/platform/extensions/compound-actions| Methods: GET, PATCH, POST - Request shape: fields go at the top level of the JSON body, with no
resourcewrapper. The item’sidgoes in the URL for reads and updates, not in the body. - Updates: a JSON merge-patch with
version: {num, change_description}from your last read. Lists of objects merge row by row, so read first and send the whole list when you remove or reorder rows. See Tool Studio. - References: Steps in
workflow_stepscall actions by theirsignature.name. Plugins and conversational processes call the compound action by itsid.
Endpoints
All paths are relative to https://api.moveworks.ai/configurations/v1alpha1. Each endpoint page lists the request and response schema, an example, and the errors it can return.
Rules the API checks
signature.nameis unique in your organization.- Send
workflow_steps(JSON) orworkflow_steps_yaml(write-only), never both. - Every
action_namein a step must be thesignature.nameof an existing action or a built-in action such asget_user_by_email. - A step’s output is available to later steps as
data.<output_key>.