Every step in an Orchestrator process can execute one or more actions. Actions are interactions with the system that enable automation and process flow control. There are various types of actions, each with its own properties and configuration, depending on the functionality it provides.

However, all actions share a set of common properties that must be configured during their setup.

Common Properties for All Actions

• Label:

  • A user-friendly name for the action, helping to identify its purpose.
  • This field is required.

• Name:

  • A unique identifier for the action within the process.
  • This field is required and it’s autopopulated when tu set the Label. You cand modify it

• Inputs:

  • Define the parameters that the action will use for its execution. There are two types of inputs:
    • Predefined:
    • These inputs have predefined names.
    • You must fill in the value for each predefined input.
    • Some predefined inputs are mandatory, while others are optional.
    • Additional:
    • These inputs are not mandatory.
    • You need to manually set both the name and the value for each additional input.
    • This flexibility allows you to pass custom data to the action.

4. Outputs:
   • Actions may return output data, which can be used by subsequent steps in the process.
   • Outputs allow for dynamic data flow between actions within the process.

Configuring Actions

To configure an action within a step:

1. Select the desired action type.
2. Complete the Label and Name fields.
3. Provide the necessary Inputs:
   • Fill in mandatory predefined inputs.
   • Add additional inputs if needed, specifying their name and value.
4. Review and configure the Outputs section to handle any data returned by the action.
5. Save the configuration to apply changes.
   • Important: If you move away from the action without saving, all changes will be lost.

Action Types

Each action type has its own properties and behavior. For a full list of available actions and their specific configurations, refer to the Actions Overview Section.

Custom Logic

• Apex
• Flow

Integration

• Send to JMS Queue

Marketing Cloud

• Create Journey
• Send Event

Orchestrator Actions

• Deactivate Event Hub:
• Fire Event:
• Un/Ignore Event:

SOQL / DML Operations

• Delete Record:
• Get Record:
• Insert Record:
• Update Record:
• Upsert Record:
• SOQL:

User Interface

• Advanced Navigation:
• Go to Record Page:
• Push Notification:
• Show Toast:

Wattyo Actions

• Action Plan Activity:
• Batch:
• Exception:
• Orchestrator Process: