Skip to main content

Deploying and trigger an Action

An Action is essentially a set of instructions waiting for a command. Once you have built and saved your automation logic, the final step is deciding how and when those instructions are executed.

You can deploy Actions to be triggered manually by business users as they analyze data, or you can configure them to run entirely in the background based on specific process conditions.

Manually executing a trigger

Manual execution puts the power of automation directly into the hands of your business users. By embedding Actions into your Celonis interfaces, users can fix process issues with a single click the moment they spot them.

  • Adding Actions to Studio Components: You can attach your Action to UI elements within your Studio Views, such as a standalone Button or an inline action within a Table. For example, a user looking at a list of blocked orders can click an "Unblock" button directly in their dashboard, instantly triggering the Action in your ERP system.

  • Adding Actions to Tasks: If your team uses Celonis Tasks to manage daily workloads, you can attach Actions directly to these tasks. When a user opens a Task, they will see a button to automatically execute the resolution (e.g., "Send Reminder Email") rather than opening the external system to do it manually.

When setting up manual triggers, you can also request manual input from the user. This prompts a pop-up window requiring the user to enter specific information (like a custom comment, a selected reason code, or a specific date) before the Action executes.

Automatically executing a trigger

For routine or highly predictable processes, you can remove the human element entirely. Automatic Execution allows you to set up rules that trigger your Action in the background whenever specific data conditions are met.

  • Condition-Based Triggers: You define a specific PQL (Process Query Language) condition. Celonis continuously monitors your data model, and the moment a record meets that criteria (e.g., Invoice Age > 30 Days AND Status = Unpaid), the Action automatically fires.

  • Batch Processing: Automatic triggers are excellent for multi-row executions, allowing you to process dozens or hundreds of records simultaneously without user intervention.

Next steps

Once your Actions are deployed and running, it is crucial to monitor their performance and ensure they are executing successfully. Proceed to Monitoring and Management to learn how to track run histories and troubleshoot errors.