For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Logo
DeveloperAcademyCommunityStatus
ReferenceGuides
ReferenceGuides
  • Agent Studio
    • Overview
    • Quickstart Guides
    • Core Concepts
    • Conversation Process
    • Actions
      • LLM Actions
      • Built-in Actions
      • HTTP Actions
      • Script Actions
      • Compound Actions
        • Action
        • Switch
        • For Loop
        • Parallel
        • Return
        • Try Catch and Raise Error
        • Notify
        • Input Arguments
        • Progress Updates
        • Compound Action Patterns
        • Compound Action Data Bank
        • Compound Action Examples
        • Troubleshooting Compound Actions
    • Connectors
    • System Triggers
    • Agent Architect
    • Cookbooks
    • Development and Testing
    • AI Agent Marketplace
    • Developer Tools
  • Agentic AI
    • LLM Fundamentals
    • The Agentic Reasoning Engine
    • Memory Constructs
    • Conversational Context
    • Guardrails
    • Grounding and Hallucinations
    • Continuous Learning
    • LLMs & SLMs
    • Steerability Tools
    • Multilingual Support
  • Core Platform
    • User Identity
    • Moveworks Agent (On-Prem)
    • Approvals Engine
    • Entity Catalog
    • Moveworks Data Objects
    • Security Information and Event Management (SIEM) Logs Overview
DeveloperAcademyCommunityStatus
On this page
  • Why Use Compound Actions
  • The steps Key
  • Getting Started
Agent StudioActions

Compound Actions

||View as Markdown|
Was this page helpful?
Edit this page
Previous

Action

Next
Built with

Compound Actions empower developers to build sophisticated, multi-step automations within Agent Studio, chaining actions, data transformations, and logic into reusable AI workflows.

Think of Compound Actions as an orchestration layer that can:

  • Collect input arguments from data sources
  • Execute actions to complete tasks
  • Conditionally run different branches of logic
  • Loop over items and run steps for each item
  • Run steps at the same time
  • Return information to the user or processes
  • Handle error gracefully
  • Notify users with interactive messages and buttons

Why Use Compound Actions

  • Modularity: Break down monolithic agents into testable, composable steps.
  • Efficiency: Parallelize tasks or loop over lists to cut execution time.
  • Resilience: Built-in error handling and early exits keep workflows robust.
  • Interactivity: Notify users mid-flow with buttons for seamless handoffs.

The steps Key

The steps key defines a sequence of expressions executed in order, forming the backbone of multi-step Compound Actions. It groups logic cleanly, ensuring predictable flow while enabling nesting for controls like switch or parallel. Use it whenever chaining more than one expression, it’s required for compound structures to maintain order and scope.

1steps:
2 - action:
3 action_name: fetch_user_data
4 output_key: user_info
5 input_args:
6 user_id: data.requestor_id
7 - switch: # Nested control
8 cases:
9 - condition: user_info.role == "admin"
10 steps:
11 - return:
12 output_mapper:
13 access: '''granted'''

Getting Started

  1. Prerequisites: Familiarity with Moveworks Data Mappers and DSL

  2. Use the Low Code Editor: Get started fast with the low code editor. Switching back to code mode will generate the compound action script for you and viceversa.

Comments

YAML comments (#) are supported and preserved during edits, but switching between low-code and code views will strip them.

See it in action: Quickstart #5: Webhook Ambient Agent · Quickstart #6: Expense Approval