What Are Compound Actions?

Compound Actions allow developers to orchestrate multiple actions into a single, cohesive automation. They enable complex task execution by combining:

1. Input Variables (This defines what data is needed for the Workflow to execute)
2. Individual Actions (HTTP calls, APIthon Scripts, Built-in Actions)
3. Control Flow Logic (Conditionals, Loops, Return, etc.)

In Pre-April 2025 versions of the Plugin Workspace, Compound Actions are then “promoted” to Plugins so that they can be accessible by end users in their bot.

In Post-April 2025 versions of the Plugin Workspace, Compound Actions are a part of the plugin through an "Action Activities" but are not required for plugins.

When should I use a compound action?

In Pre-April 2025 versions of the Plugin Workspace, you should always create a compound action, even if you wish to have a plugin only use on action. After creating the compound action, you will then promote the compound action to a plugin.

In Post-April 2025 versions of the Plugin Workspace, Compound Actions are no longer required as you can chain together actions directly inside of a plugin or have plugins with only one action.

We recommend using Compound Actions when you want to chain together actions to accomplish a determined task inside of an Action Activity. In this way, Compound Actions are less "intelligent" and more workflow focused.

We recommend chaining actions together in a plugin instead of using a compound action if you wish to have a more conversational and dynamic experience with your end users. This includes having the Moveworks AI Assistant follow business processes and interact through multiple turns with users. See Plugins for more information.