SAP Automation Pilot ships 15 new features in Q3 2026 – including native AI-agent authentication, a persistent key-value storage shared across executions, and over 60 new provided commands.
If you’re running automations on SAP Business Technology Platform (BTP), your toolkit just got a serious upgrade. This quarter touches everything from how you connect to external systems, to how automations persist data between runs, to how you track what’s actually happening across your landscape. Here’s the full picture.
New to the product?
It’s a low-code/no-code automation service on SAP BTP that helps DevOps and Operations teams automate cloud operations – with over 300 built-in commands and a serverless script execution environment. More details about the product can be found at:
Usage Statistics Dashboard
SAP Automation Pilot now has a built-in dashboard that shows you how your automations are actually being used. You can see the number of executions by day and hour, which commands get triggered most, success rates, and how much of your quota you’ve consumed – all with time-range filtering. If you’ve been piecing this picture together manually or through external tools, it’s now right inside the service. For more information, see Working with Executions.
Subexecutions Panel in Execution Details
When you open an execution’s details page, there’s now a dedicated Subexecutions section that lists everything the parent execution triggered. Subexecutions also get tagged automatically – autopi:parentExecutorPath tells you which executor started them, and for ParallelForEach, autopi:parentBatchIndex tells you which batch they belonged to. No more jumping back and forth to understand what a complex command actually did. For more information, see Monitoring Executions.
Capture HTTP User-Agent as a Service Tag
When an external system triggers an execution via the API, SAP Automation Pilot now reads the User-Agent header from the HTTP request and stores it as a read-only autopi:userAgent service tag. This means that even when multiple systems share the same service account, you can tell which one triggered which execution – directly from the details page or by filtering via the API. It takes zero configuration on the SAP Automation Pilot side – the caller just needs to set a meaningful User-Agent header, which is a one-line change in any HTTP request. For more information, see Tags.
Configurable Table Columns with Custom Tag-Based Columns
The entity tables in SAP Automation Pilot – Commands, Inputs, Executions, Scheduled Executions – can now be personalized. You can show or hide predefined columns, reorder them, and add custom columns based on your tag keys. So if your team tags executions by environment, region, or ticket number, those values can now show up as their own columns instead of being buried inside each execution’s detail view. For more information, see Configuring Table Columns.
Command Clone with Multiple Cloning Modes
Cloning commands now gives you three distinct modes. Clone Full Command copies the entire configuration into a new command, so you can adapt and extend it without touching the source – this one is available for custom commands. Clone Contract Only keeps the same input and output keys but gives you an empty implementation to build from scratch. Clone as Wrapper creates a new command with a single executor that calls the source command, with all parameters automatically mapped – so you can add logic around it without reconfiguring anything manually. Both Clone Contract Only and Clone as Wrapper are available for provided commands as well, giving you a proper starting point when building on top of SAP-provided content. For more information, see Cloning Commands.
Secure Service Account Integration for AI Agents
Service accounts in SAP Automation Pilot now support token-based authentication – meaning the credentials can be used as a Bearer token or an API key, on top of the existing Basic authentication. The service account type has been renamed to API Token / Basic and the password field is now called token to reflect this.
Why does this matter? Because MCP clients, Joule, and most third-party agent frameworks expect token-based auth. Until now, wiring them into SAP Automation Pilot required workarounds. Now it’s a native, one-step setup. Alongside this, a new MCP permission lets you scope exactly which MCP server endpoints a service account can access – so you can give an AI agent the ability to trigger automations without granting access to anything beyond what the agent needs.
If you’re building agent-driven Ops workflows, this is the feature that makes it practical. For more information, see Managing Service Account Permissions.
Native Destination Service Integration & HTTP Request Enhancements
The new HttpRequestViaDestination command lets you execute HTTP requests by referencing a destination from the SAP Destination Service directly. URL resolution, authentication, proxy settings, certificates – all of it is pulled from the destination configuration automatically. No more duplicating credentials and connection details inside SAP Automation Pilot. If you’re already managing your connectivity through the SAP Destination Service, your automations can now plug straight into that setup. For more information see HTTP Operations (http-sapcp) Catalog.
SendEmail STARTTLS Support
The SendEmail command now supports STARTTLS encryption through a new encryptionMode input key. Previously, sending emails through public SMTP servers that require STARTTLS meant routing traffic through SAP Cloud Connector. Now you can connect directly – one less hop, one less thing to configure. For more information, see Email Operations (email-sapcp) Catalog.
Cross-Execution Runtime Storage
Until now, each execution in SAP Automation Pilot lived in isolation – once it finished, its data went with it. That changes with the new Cross-Execution Runtime Storage: a tenant-scoped, encrypted key/value storage that any execution can read from and write to. Three commands handle everything – PutValue, GetValue, and DeleteValue.
This unlocks automation scenarios that simply weren’t practical before. Executions can now pass state to each other, track progress across multi-step workflows, cache shared configuration, or coordinate processes – all without relying on external storage. If you’ve ever built a workaround to share data between executions, this is the clean, built-in replacement. For more information, see Execution Runtime Storage.
SAP Integration Suite Provided Catalog
SAP Automation Pilot now ships a dedicated catalog for SAP Integration Suite – 21 ready-to-use commands covering integration flow lifecycle management, configuration updates, monitoring of deployed integration flows, and directory management. All accessible directly from the provided catalogs, no custom command building required.
This is a significant expansion. SAP Integration Suite is one of the most widely used services on SAP BTP, and until now, automating operations around it meant building everything from scratch using HTTP requests. With a provided catalog in place, teams can automate routine integration operations – deploying flows, checking statuses, updating configurations.
If you’re managing integration landscapes at scale, this catalog saves a lot of custom work. For more information, see SAP Integration Suite (is-sapcp) Catalog.
SAP HANA Cloud Lifecycle Management Commands
A new SAP HANA Cloud Administration catalog brings 40 commands for managing SAP HANA Cloud instances – covering provisioning, lifecycle management, configuration, and observability across both Cloud Foundry and Other Environment deployment types.
We covered this catalog in depth in a dedicated blog post – you can find it here: Meet the SAP HANA Cloud Administration Catalog for SAP Automation Pilot
Granular Skip Options for ParallelForEach Failures
When a ParallelForEach step fails, the Skip dialog now offers two distinct options – skip only the current failed batch and continue processing the remaining ones, or skip all remaining batches and move on to the next executor in the parent command. Previously, skipping meant stopping everything. Now you can isolate a failure without halting the entire parallel run. For more information, see Controlling Executions with Actions.
Custom Tags for ParallelForEach Subexecutions
You can now assign tags to ParallelForEach subexecutions dynamically using expressions. Instead of entering tags manually for each subexecution, you reference a complete tag set from an input and it gets applied automatically, making it easier to organize, filter, and trace parallel workloads at scale. For more information, see ParallelForEach.
Auto-Abort Stale Failed Executions
A new Auto-Abort Failed Executions feature automatically aborts executions that remain in a Failed state without updates for a configurable duration (1–168 hours). Your execution list stays clean without manual intervention. For more information, see Additional Features.
Immediate Deletion of Completed Executions
You can now delete completed executions on the spot instead of waiting for the retention cleanup cycle. Setting the retention value to 0 causes immediate deletion as soon as an execution reaches a completed status. When an execution is done and you no longer need it, it’s gone, keeping your execution list manageable without relying on automated retention policies. For more information, see Additional Features.
Learn More & Stay Connected
-
What’s New in SAP Automation Pilot – full release notes and changelog
-
Release Navigator for SAP Automation Pilot – find release notes, blog posts, and related resources in one place
#SAPCHANNEL