Action - Celonis: Execute Workflow
Skills Deprecation
Effective August 1st 2025, Skills features can no longer be purchased as part of a Celonis Platform license. Celonis continues to maintain Skills (by fixing bugs and ensuring that performance remains strong) but no further feature development will take place.
To continue working with your process improvement and automation use cases, we suggest using our Action Flows, Views, and/or Orchestration Engine features.
Automate actions directly from your signals by triggering multi-step workflows with a single click.
To successfully use the Celonis: Execute Workflow action within a Skill, you should ensure the following prerequisites are met:
Existing Workflow or Permissions: Since this action triggers an automated process, you must either:
Have an existing Workflow already configured in your Celonis environment that you wish to link.
Have the necessary permissions to create a new Workflow if you plan to build one from scratch during the configuration.
Action Engine Setup: The Action Engine must be active and configured within your project, as this specific action is designed to be triggered directly from the Signal Details interface.
Skill Configuration: You need to be in the process of setting up a Skill. The Execute Workflow option is an optional component of the "Action configuration" step within the Skill builder.
Bot/Automation Access: If your multi-step workflow relies on external bots to automate recurring procedures, ensure that the service accounts or bot credentials required for those backend tasks are properly authenticated.
To configure the Celonis: Execute Workflow action within your Skill, follow these steps:
Select the Action Type: In the Action configuration (optional) section of your Skill builder, click on Add Action and select Celonis: Execute Workflow from the dropdown menu.
Connect the Workflow: Choose how you want to link the automation:
Link Existing: Select a predefined workflow from your library.
Create New: If the specific automation doesn't exist yet, select the option to create a new workflow. This will allow you to define the multi-step process or bot-driven execution required for the task.
Map Dynamic Placeholders: To ensure the workflow acts on the correct data, use dynamic placeholders from your Signal’s result table.
Example: Map an
Invoice_IDorCustomer_Numberplaceholder so that when a user clicks the action in their My Inbox, the workflow knows exactly which record to process.
Configure Automated Status Updates (Optional): Under General settings, you can define what happens to the Signal once the workflow is triggered. For instance:
Set the Signal status to In Progress automatically upon execution.
Route the Signal to a different user or state once the multi-step process begins.
Save and test:
Save your Skill configuration.
Verify the result in the Signal Details view to ensure the action button appears correctly for the business user and triggers the intended backend automation.