Input arguments define the external data a Compound Action requires to run, sourced from plugin triggers (e.g., webhooks) or upstream callers like a conversation process. They act as entry points, ensuring workflows receive validated, typed inputs, think user email for personalization or ticket IDs for routing, before diving into steps. By declaring them upfront, you enable dynamic execution while enforcing structure, reducing runtime errors and easing integration.

In the Editor, you set up Input Arguments by pressing on the Input Args button.

The input arguments panel, showing the list of arguments with "user_email" and controls for search.

Setting Up Input Arguments

Access the Input Arguments tab in the Compound Action Editor to add, edit, or remove them. Each argument needs a name, data type, optional description, and required flag. Saving updates the config instantly.

Create New: Click "Create New" to open a new form to create an argument.
Define Details: Enter name (e.g., user_email), select the type, add a description, and toggle required.

Available Data Types

Type	Description	Example Value
`string`	Text or identifiers	`"[email protected]"`
`integer`	Whole numbers	`42`
`number`	Decimals or floats	`3.14`
`boolean`	True/false flags	`true`
`object`	Key-value pair structures	`{ "role": "admin" }`
`User`	Moveworks user object	`{ "id": "123", "email_addr": "[email protected]" }`
`List[T]`	List of the selected type	`List[string] -> ["[email protected]", "[email protected]"]`

Usage in Compound Actions

Inputs get stored in the data bank and flow into steps via data mapping (e.g., data.user_email in action args).

steps:
  - action:
      action_name: validate_email
      input_args:
        email: data.user_email  # From declared string arg
      output_key: validation_result
  - switch:
      cases:
        - condition: validation_result.valid == true
          steps:
            - notify:
                recipient_id: data.user_id  # Another input
                message: '''Email confirmed!'''