Setting up connections
Before you can build an Action that updates external records or sends messages, you must give Celonis permission to communicate with your target system.
A Connection is a secure, authenticated link between Celonis and a third-party application (such as Salesforce, ServiceNow, or your email provider). It securely stores your login credentials or API tokens so that Celonis can push data to those systems on your behalf.
Key concepts for connections
Build Once, Reuse Anywhere: You do not need to configure a new connection for every single Action you build. Once you successfully authenticate a connection to a system (e.g., your company's Jira environment), you can reuse that same connection across multiple different automations.
Application-Specific Authentication: Because every external system handles security differently, the requirements for establishing a connection will vary. Some systems require a simple username and password, some use API Keys, and others require OAuth 2.0 authorization.
User Context: Depending on the system and authentication type, Actions can execute under a "System/Integration User" (where all changes look like they were made by a generic bot) or under the specific business user who triggered the Action.
General connection workflow
While the exact setup varies by application, establishing a new connection generally follows these steps:
Select your application: From the action builder or your team's connection management hub, select the specific target application you want to connect to (e.g., Jira, SAP, Microsoft Teams).
Provide credentials: Enter the required authentication details. If the application uses OAuth (like Google Workspace or Salesforce), you may be temporarily redirected to that application's login screen to grant Celonis access.
Test the link: Always test your connection to verify that the credentials are valid and that Celonis has the correct permissions to reach the target system.
Save and Assign: Name your connection clearly (e.g., "Production Salesforce" vs. "Sandbox Salesforce") so you and your team can easily identify it when building Actions later.