Introduction
As organizations continue to operate across increasingly complex hybrid landscapes, the ability to automate tasks securely across cloud and on‑premise environments becomes essential. SAP Automation Pilot, combined with SAP Cloud Connector, delivers exactly that – an integrated approach that allows teams to orchestrate and execute automation scenarios involving systems that are not directly reachable from the public Internet. This powerful pairing enables secure, controlled, and efficient operations, helping teams streamline workflows while maintaining strict network boundaries.
What is SAP Automation Pilot?
SAP Automation Pilot is a cloud-based service within SAP BTP that streamlines DevOps processes. This low-code/no-code engine offers over 300 pre-built commands for various DevOps tasks, while also allowing users to create custom commands. Highly scalable and integrating seamlessly with SAP services and third-party tools, SAP Automation Pilot empowers teams to reduce operational overhead and enhance efficiency across their technology stack. More details about the product can be found at:
SAP Automation Pilot Documentation
Learn more about SAP Cloud Connector
SAP Cloud Connector provides a secure and efficient bridge between SAP BTP applications and on‑premise systems. With its straightforward setup and clear configuration options, it enables organizations to tap into their existing on‑prem assets without exposing their full internal landscape.
Operating as an on‑premises agent, it uses a reverse‑invoke approach to ensure safe communication with SAP BTP – no inbound traffic required. Built for enterprise continuity, it supports high‑availability scenarios, automatically restores broken connections, and delivers detailed audit logging. The result is a reliable, controlled, and secure foundation for business‑critical integrations. More details can be found at:
Integrating SAP Automation Pilot with SAP Cloud Connector
SAP Automation Pilot and SAP Cloud Connector work together to extend automation into private, on‑premise environments, securely and without opening inbound access. Automation Pilot orchestrates and executes operational tasks, while the Cloud Connector provides the protected bridge to internal systems. SAP Automation Pilot extends several of its standard commands to work seamlessly with systems accessed through the Cloud Connector:
Executing HTTP Requests
You can trigger HTTP calls to internal services exposed via the Cloud Connector. The familiar HttpRequest command has been enhanced with additional parameters that enable Cloud Connector usage, making it easy to route requests securely to on‑premise systems. When making HTTP requests through the Cloud Connector, it’s best to increase the default timeout value, as these calls may take longer due to additional network routing and processing. Additionally, when using the HTTPS protocol, make sure to explicitly set the port to 443 in the URL to ensure the request is routed correctly through the connector. For more information, see Executing HTTP Requests.
Sending Emails
If your organization relies on private SMTP servers, these can also be accessed through the Cloud Connector. The SendEmail command now supports additional input keys, allowing Automation Pilot to send emails through internal mail servers without exposing them externally. For more information, see Sending Emails.
Using Jenkins Commands
All Jenkins commands in the Automation Pilot catalog now support Cloud Connector integration as well. This is especially useful if you operate your own private Jenkins instance, enabling secure automation scenarios that interact directly with your internal CI/CD infrastructure. For more information, see Using Jenkins Commands.
Executing an HTTP GET Request Through the Cloud Connector
Prerequisites
1. You have a Cloud Connector installation. See Installation.
2. You have connected the Cloud Connector to the subaccount where SAP Automation Pilot is enabled. See Adding and Managing Subaccounts.
3. You have specified the internal system that you want to access in the Cloud Connector. This will allow SAP Automation Pilot to access the system. The procedure is specific to the protocol that you are using for communication. For more information, see Configure Access Control.
4. You have ensured that the internal system can make outbound calls to the region-specific Automation Pilot Connectivity Proxy endpoint. This connection is often blocked by default due to corporate outbound firewall rules, so you might need to add the endpoints to the firewall’s allowlist. See a list of the Automation Pilot Connectivity Proxy endpoints in Service Availability.
These steps are also linked in SAP Automation Pilot Documentation.
Once the Cloud Connector is successfully linked, you can view all relevant connection details directly in the Cloud Connectors view in the SAP BTP cockpit that can be found uder Connectivity. This includes the Location ID, connected Resources, Host, Protocol, Back-End type, and Description. For the next steps, you will need the Location ID.
In our example setup, we’ve created a command in Automation Pilot that includes two executors configured to reach an on‑premise HTTP endpoint. For the first executor, choose Edit to configure the required fields. In Method, from the dropdown menu, choose GET, then provide the URL of the endpoint you want to access.
In the Cloud Connector tab, located in the Smart View of the command, turn on the toggle to enable the Cloud Connector and enter the corresponding Location ID, ensuring the request is sent through the correct on‑premise connection.
For the second executor, we follow the same configuration approach as before, this time supplying a different URL so the command can target another on‑premise endpoint exposed through the Cloud Connector.
If you are using OAuth authentication, you can also switch on the Technical User Propagation toggle. This allows SAP Automation Pilot to forward the identity of the technical user defined through the OAuth client. In practice, this means the request can access the on‑premise system on behalf of that technical user, ensuring the correct authorizations are applied without requiring additional credentials. For more information, see SAP BTP Connectivity.
Customer Success Story: Johnson Controls International (JCI)
Thanks to the integration of SAP Automation Pilot with SAP Cloud Connector, JCI was able to operate its large and complex on‑premise SAP landscape securely. JCI eliminated over 3,000 hours of manual work and transformed routine monitoring into a strategic capability.
You can read the full customer story here 👉 SAP Community Blog: “SAP Automation Pilot – Empowering IT Operations with AI Insights”
Wrap-Up
The integration between SAP Automation Pilot and SAP Cloud Connector provides a secure and efficient way to automate operations across hybrid landscapes. With extended command support, reliable on‑premise access, and seamless execution of internal requests, teams can simplify their workflows and improve operational consistency. This combination delivers the flexibility and control needed to automate confidently in complex enterprise environments.
IntroductionAs organizations continue to operate across increasingly complex hybrid landscapes, the ability to automate tasks securely across cloud and on‑premise environments becomes essential. SAP Automation Pilot, combined with SAP Cloud Connector, delivers exactly that – an integrated approach that allows teams to orchestrate and execute automation scenarios involving systems that are not directly reachable from the public Internet. This powerful pairing enables secure, controlled, and efficient operations, helping teams streamline workflows while maintaining strict network boundaries. What is SAP Automation Pilot?SAP Automation Pilot is a cloud-based service within SAP BTP that streamlines DevOps processes. This low-code/no-code engine offers over 300 pre-built commands for various DevOps tasks, while also allowing users to create custom commands. Highly scalable and integrating seamlessly with SAP services and third-party tools, SAP Automation Pilot empowers teams to reduce operational overhead and enhance efficiency across their technology stack. More details about the product can be found at:SAP Discovery CenterSAP Automation Pilot Documentation Learn more about SAP Cloud ConnectorSAP Cloud Connector provides a secure and efficient bridge between SAP BTP applications and on‑premise systems. With its straightforward setup and clear configuration options, it enables organizations to tap into their existing on‑prem assets without exposing their full internal landscape.Operating as an on‑premises agent, it uses a reverse‑invoke approach to ensure safe communication with SAP BTP – no inbound traffic required. Built for enterprise continuity, it supports high‑availability scenarios, automatically restores broken connections, and delivers detailed audit logging. The result is a reliable, controlled, and secure foundation for business‑critical integrations. More details can be found at:SAP BTP Connectivity Integrating SAP Automation Pilot with SAP Cloud ConnectorSAP Automation Pilot and SAP Cloud Connector work together to extend automation into private, on‑premise environments, securely and without opening inbound access. Automation Pilot orchestrates and executes operational tasks, while the Cloud Connector provides the protected bridge to internal systems. SAP Automation Pilot extends several of its standard commands to work seamlessly with systems accessed through the Cloud Connector:Executing HTTP RequestsYou can trigger HTTP calls to internal services exposed via the Cloud Connector. The familiar HttpRequest command has been enhanced with additional parameters that enable Cloud Connector usage, making it easy to route requests securely to on‑premise systems. When making HTTP requests through the Cloud Connector, it’s best to increase the default timeout value, as these calls may take longer due to additional network routing and processing. Additionally, when using the HTTPS protocol, make sure to explicitly set the port to 443 in the URL to ensure the request is routed correctly through the connector. For more information, see Executing HTTP Requests.Sending EmailsIf your organization relies on private SMTP servers, these can also be accessed through the Cloud Connector. The SendEmail command now supports additional input keys, allowing Automation Pilot to send emails through internal mail servers without exposing them externally. For more information, see Sending Emails.Using Jenkins CommandsAll Jenkins commands in the Automation Pilot catalog now support Cloud Connector integration as well. This is especially useful if you operate your own private Jenkins instance, enabling secure automation scenarios that interact directly with your internal CI/CD infrastructure. For more information, see Using Jenkins Commands. Executing an HTTP GET Request Through the Cloud ConnectorPrerequisites1. You have a Cloud Connector installation. See Installation.2. You have connected the Cloud Connector to the subaccount where SAP Automation Pilot is enabled. See Adding and Managing Subaccounts.3. You have specified the internal system that you want to access in the Cloud Connector. This will allow SAP Automation Pilot to access the system. The procedure is specific to the protocol that you are using for communication. For more information, see Configure Access Control.4. You have ensured that the internal system can make outbound calls to the region-specific Automation Pilot Connectivity Proxy endpoint. This connection is often blocked by default due to corporate outbound firewall rules, so you might need to add the endpoints to the firewall’s allowlist. See a list of the Automation Pilot Connectivity Proxy endpoints in Service Availability.These steps are also linked in SAP Automation Pilot Documentation.Once the Cloud Connector is successfully linked, you can view all relevant connection details directly in the Cloud Connectors view in the SAP BTP cockpit that can be found uder Connectivity. This includes the Location ID, connected Resources, Host, Protocol, Back-End type, and Description. For the next steps, you will need the Location ID. In our example setup, we’ve created a command in Automation Pilot that includes two executors configured to reach an on‑premise HTTP endpoint. For the first executor, choose Edit to configure the required fields. In Method, from the dropdown menu, choose GET, then provide the URL of the endpoint you want to access. In the Cloud Connector tab, located in the Smart View of the command, turn on the toggle to enable the Cloud Connector and enter the corresponding Location ID, ensuring the request is sent through the correct on‑premise connection. For the second executor, we follow the same configuration approach as before, this time supplying a different URL so the command can target another on‑premise endpoint exposed through the Cloud Connector. If you are using OAuth authentication, you can also switch on the Technical User Propagation toggle. This allows SAP Automation Pilot to forward the identity of the technical user defined through the OAuth client. In practice, this means the request can access the on‑premise system on behalf of that technical user, ensuring the correct authorizations are applied without requiring additional credentials. For more information, see SAP BTP Connectivity. Customer Success Story: Johnson Controls International (JCI)Thanks to the integration of SAP Automation Pilot with SAP Cloud Connector, JCI was able to operate its large and complex on‑premise SAP landscape securely. JCI eliminated over 3,000 hours of manual work and transformed routine monitoring into a strategic capability.You can read the full customer story here 👉 SAP Community Blog: “SAP Automation Pilot – Empowering IT Operations with AI Insights” Wrap-UpThe integration between SAP Automation Pilot and SAP Cloud Connector provides a secure and efficient way to automate operations across hybrid landscapes. With extended command support, reliable on‑premise access, and seamless execution of internal requests, teams can simplify their workflows and improve operational consistency. This combination delivers the flexibility and control needed to automate confidently in complex enterprise environments. Read More Technology Blog Posts by SAP articles
#SAP
#SAPTechnologyblog
