Skip to main content

Planned Releases

The features listed below will be released in the coming months. The information provides advance notification about new features. The dates are subject to change. However, we strive to keep the date information as accurate as possible, giving daily updates.

You can find information about released features in our Release Notes and documentation.

Tip

Use CTRL+F or Command+F to search for specific terms.

DATA INTEGRATION Extractor Builder - Improved user experience (2025-09)

Extractor Builder is our Celonis Platform component that allows customers to connect to any source system exposing REST APIs. With this launch, we are introducing a new and improved guided user interface which simplifies and accelerates the data integration process.

The enhanced Extractor Builder now includes:

  • Improved navigation: Visual overview screen and new menu bar allowing for quicker navigation between the configuration pages.

  • Integrated data connection setup: Allowing the creating of a data connection as part of the process directly in Extractor Builder.

  • Simplified authentication configuration: Simplified process to select and configure the right authentication method by providing examples and in-product documentation.

  • Extraction tests and previews: Directly validate and test the extraction for an endpoint and retrieve a preview of your data.

For more information, head to Enhanced Extractor Builder (Private Preview).

Custom extractor builder window with the overview of setting up a new extractor.

DATA INTEGRATION Changes to Celonis IP addresses: Action required after 2025-09-17

Important

These changes affect the eu-2, eu-3, jp-1, uk-1 and us-2 realms only. If you're on any other realm and/or don't use IP allowlisting for Celonis-originating traffic, these changes will not affect you and no action is required.

  1. Ensure all your system IP allowlists contain the IPs listed in Celonis IPs as origin.

  2. Remove the following IPs from all allowlists in your realm(s).

    Realm

    IPs to be removed after 2025-09-17

    eu-2

    13.73.158.49

    13.80.109.60

    168.63.109.207

    eu-3

    20.218.91.128

    20.218.105.182

    jp-1

    52.243.46.143

    uk-1

    51.132.48.184

    us-2

    20.187.3.129 

    52.183.80.180

    40.65.121.189

Decommissioning API and application keys: Action required before 2025-12-31

Important

These changes affect users who currently use API keys and/or application keys for the Audit Log, Platform Adoption and Team Login History APIs.

If you don’t use APIs or application keys in your applications or in third-party systems for these APIs, these changes will not affect you and no action is required.

Why we’re making these changes

We’re moving away from using API and application keys to the OAuth 2.0 authorization standard to provide a more secure, streamlined and efficient developer journey.

Users currently generate long-term API keys or application keys in the Celonis Platform. These keys are then embedded in applications and allow data to be requested or pushed using Celonis APIs. As these keys typically have a long life, cannot be rotated and their scope cannot be limited, any application with an embedded API or application key can access almost all Celonis APIs.

With OAuth 2.0, scoping means OAuth-enabled clients can access permitted APIs only. This follows the security principle of least privilege so an OAuth client only has the privileges required to perform a certain task.

Action required before 2025-12-31

  1. Identify any systems and/or applications that use API or application keys to call any of the following APIs:

    1. Audit Log API.

    2. Platform Adoption API.

    3. Team Login History API.

  2. Migrate these systems and/or applications to OAuth 2.0.

For information on enabling OAuth 2.0 on the Celonis Platform, see Using an OAuth 2.0 token in Celonis.

Note

In future, we're aiming to move to OAuth 2.0 for all Celonis use cases. If you're using other Celonis APIs that already support OAuth 2.0, you can move to OAuth 2.0 for these APIs too. We’re also adding OAth 2.0 support for Action Flows and On-premise clients and will let you know when this is available