Skip to main content

Celonis Action Engine Sensor

The Celonis Action Engine Sensor bridges the gap between process insights and automated execution. By integrating Process Automation Skills directly into the Action Engine, you can transform manual oversight into immediate, intelligent action.

Integrating your Skills with the Action Engine is beneficial because it:

  • Closes the Loop: Moves beyond just identifying process inefficiencies (Signals) to resolving them instantly with automated workflows.

  • Simplifies User Experience: Business users don't need to leave the Action Engine interface to trigger complex automations; the "Action" button handles the heavy lifting.

  • Ensures Data Integrity: The sensor automatically maps Signal attributes to Skill parameters, reducing manual data entry errors and ensuring the automation has the exact context it needs to run successfully.

Before configuring the Action Engine sensor, you need:

  • A published Process Automation Skill in Celonis Studio.

  • Administrative or Edit access to the Action Engine configuration.

To allow users to trigger an automation directly from a Signal, follow these steps:

  1. Open Action Configuration: Navigate to the Action Engine configuration page and select Add Action.

  2. Select your Skill: Browse the available packages to find the Skill you want to trigger. Select it and provide a clear, recognizable name for the action (e.g., "Update Purchase Order" or "Send Vendor Notification").

  3. Define Automation Parameters (Optional): If your Skill requires specific data to execute:

    • In Process Automation: Ensure you have defined the mandatory input parameters required for the Skill's execution.

    • In Action Engine: Map these parameters to the available Signal Attributes. Use placeholders to ensure the Skill receives the correct data from the specific Signal being viewed.

  4. Save and Deploy: Save your configuration. The Skill will now appear as a clickable action within the relevant Action Engine Signals.

Note

Parameters that are marked as mandatory within individual actions in your Skill will automatically be required when the Skill is triggered via the Action Engine.

Related topics