Retrieving Data from Celonis
Learn how to initiate and manage digital processes in Emporix's Orchestration Engine (OE) using Celonis signals as triggers.
Last updated
Was this helpful?
OE
Learn how to initiate and manage digital processes in Emporix's Orchestration Engine (OE) using Celonis signals as triggers.
Last updated
Was this helpful?
The Celonis signals and events can be used as triggers for digital processes. To retrieve data from Celonis in your digital process, you can use Make scenarios as triggers, with included Start New Orchestration module or the Celonis Intelligence API modules.
The modules below should be used only if you want to have Celonis signals as triggers for your digital processes. If you want third party systems to send trigger events to OE, use the CloudEvents described in Events Authentication and Configuration documentation.
The Start New Orchestration module is available both as part of OE Modules but also can be used from your Celonis EMS Action Flows. In the later case, you can trigger digital processes as part of your EMS process mining setup. For example, you can use this module to start a digital process based on certain triggered signals.
The Resume Event module is used as a wake up trigger so an action flows can resume a digital process instance. In order to resume a digital process from outside of OE, you must provide the digital process instance id. In Make, you can obtain the instance id through the extractor and/or store it as an augmented attribute on a record.
The Celonis Intelligence API is a software interface that offers regulated access to Celonis Intelligence, enabling its integration with third-party tools and platforms.
The start using Celonis Intelligence API, it has to be enabled on the Celonis side. Contact the Celonis Team for the enablement support.
If you work with Celonis, make sure the Emporix IPs are allowlisted with the IP-based Access Restrictions as documented by the company. You can find the information about Emporix IPs under Firewall Allowlisting.
The module makes it possible to link Make scenarios with triggers from Celonis Knowledge Models. To configure the module, you need to have a trigger set up in your Celonis account for the specific knowledge model you want to use. Only then, you can configure the Record Trigger Event module in Make.
The steps below are used for demonstration purposes to show how a Celonis Knowledge Model trigger can be set up and then used in OE, but for exact guidance and details on the solution, see the Celonis Triggers documentation.
To set up the trigger in your Celonis account:
Go to Studio -> your Space.
Choose your configured Knowledge Model and go to Triggers.
Add a name for the trigger, select the Record that should be monitored by the trigger and use apply Filters to define the record items.
Save the trigger configuration.
To configure the Record Trigger Event module in Make:
In your Make scenario, select the Record Trigger Event as the Celonis Intelligence API module.
Choose to add a new webhook in the module configuration.
Add the name for the subscription. We recommend to add a unique name for the subscription as it later helps in identifying the correct data on Celonis side, in the Knowledge Model. See the images below to see how the Subscription Name in Make module is reflected in Celonis Knowledge Model trigger subscribers.
Choose the Knowledge Model from which you want to gather data, and for which you had previously configured the trigger.
After choosing the Knowledge Model, you can select the trigger from the list of available triggers, for example: new overstock items. The name in the module's drop-down list reflects the name that is visible in the Triggers list in the Celonis Knowledge Model.
Save the module configuration and then the scenario.
When the connection is configured, you can see it as a new subscription in your trigger details, in the Celonis account. When you open the subscribers info, you can see your trigger subscription logs.
To see an example of how the trigger works after receiving a new data load:
In your Celonis account go to Data Pools -> your Data Source -> Data Connections and choose Add Data Connection.
Choose Upload Files and with select the file you want to upload.
The file is visible under Files, choose Import to upload.
Go to Data Pools again -> your Data Source -> Data Jobs and choose Execute Data Job.
Select Full Load and choose Execute Selection.
When the data load job is executed, the Make scenario with the configured Record Trigger Event is started. You can later check the module logs in the scenario runs history.
Whenever you want to remove the subscription to the trigger, you can do so by deleting the webhook in your Make account.
The module enables you to retrieve data related to specific KPIs from a Celonis Knowledge Model. To set it up, first establish a connection to your Celonis account, then select a Knowledge Model from the available options linked to your account. Once a model is chosen, you can specify the KPI from which you want to extract the data.
The module is configured to make an API call to the Celonis Intelligence API to fetch data from Celonis Knowledge Model.
The module allows you to choose the Celonis Knowledge Model from which you want to fetch data. The results are returned in bundles. You can configure the data list using the following fields:
Fields items - use them to select which specifics you want to gather from the data model, the items might include attributes like for example company codes, shipping methods, or vendors.
Filters - you can choose different types of filters: select the filter from a drop-down list of items, or add a custom filter expression, for example PLANT eq "P05".
Sort - define the way the data is displayed on the list. If you want to use multiple fields for sorting, you can put them in an expression with a comma separated list of fields, for example sort=+field1,-field2,field3.
Limit - use it to limit the data amount fetched from the knowledge model, you can set up the max number of returned bundles. The default page size is set to 50.
Depending on your module configuration the data fetched from the knowledge model differs in the output. See the data that is returned with the exemplary mapping setup:
For the Knowledge Model Record Data you can use Breaks as a flow control. Each break lets you define automatic executions and a number of attempts.
