Actions (Skills)
Actions (formerly known as Skills) are the bridge between discovering a process inefficiency in Celonis and actually fixing it in your source systems.Whether you want to automatically update a block in SAP, send a pre-formatted email to a vendor, or create a Jira ticket from a dashboard, Actions allow you to build these workflows without writing any code.
To go from a blank slate to a fully deployed automation, you will generally follow this four-step process:
Step 1: Connecting your source system
Before Celonis can make changes in your external applications (like Salesforce, Coupa, or ServiceNow), you need to establish a secure connection. This gives Celonis the necessary authentication and permissions to push updates.
To learn how to set this up: Setting up connections.
Step 2: Building the Action Logic
Once connected, you need to define exactly what happens when the Action is triggered. You can build this step-by-step using our visual builder, or you can skip the setup entirely by using pre-packaged logic.
To learn how to build the Action logic, see: Building the Action logic
Step 3: Deploying and triggering
An Action does nothing until it is triggered. You can decide exactly how and when your automation runs:
Manual Execution: Embed your Action as a button directly into your Studio Views so business users can trigger it while analyzing data.
Automatic Execution: Set up data-driven triggers so the Action fires automatically in the background whenever specific conditions are met.
To learn how to deploy and trigger actions, see: Deploying and trigger an Action
Step 4: Monitoring executions
Once your Action is live, you can track its performance, audit who triggered it, and troubleshoot any failed runs to ensure your automations remain reliable.
To learn how to monitor executions, see: Monitoring and managing Actions