3832166 - Outbound HTTP notification after Data Action or Multi Action completion in SAP Analytics Cloud

• Need to send an outbound HTTP request/webhook after successful completion of a Data Action or Multi Action.
• Need an SAP-supported way to notify an external system that planning data changed without continuous polling.
• Clarification requested whether Multi Actions or other services (for example, Event Mesh) can be used to initiate an external call on completion.
• Questions around supported authentication for outbound HTTP calls (for example, OAuth), and whether browser-based OAuth is required or supported for this scenario.

• SAP Analytics Cloud 

SAP Analytics Cloud does not natively provide an automatic outbound HTTP/webhook event upon completion of a Data Action or Multi Action.

1. Use a Multi Action to orchestrate the end-to-end planning flow and place an API step at the end to call an external REST endpoint after the planning steps complete successfully.
2. Sequence the steps as: Data Action step → Publish/Version Management step (if applicable) → API step (outbound HTTP call).
3. Create an HTTP API Connection in SAP Analytics Cloud for the external system and select OAuth 2.0 Client Credentials (non-interactive) when the external provider supports it. Provide the token URL, client ID, and client secret from the external OAuth configuration.
4. Verify the external OAuth token endpoint returns token_type as exactly “Bearer” or “BearerToken”, otherwise the connection save can fail and appear as authentication failure.
5. Configure the Multi Action API step to use the HTTP API Connection and call the target endpoint (for example, a lightweight notify endpoint). This achieves an event-driven pattern without continuous polling of the Data Export API.
6. Do not use browser-based/interactive OAuth for this use case. Interactive OAuth (App Integration > OAuth Clients) is for inbound access to SAP Analytics Cloud APIs and is not required to call out from a scheduled Multi Action. Note: Client Credentials is not supported for the unrelated multi-action public API inbound trigger scenario (refer to the referenced note); this does not affect the outbound API step approach.

• Refer to: Integrate External Applications Using Multi Actions (API step)
• Refer to: Set Up Third-Party Access with OAuth Clients
• Refer to: SAP Note 3408915
• Refer to: Integrate external applications using Multi Actions (community)
• Refer to: Snowflake key-pair authentication update (community)

SAP Analytics Cloud, Multi Action API step, outbound HTTP, webhook, Data Action completion, event-driven integration, HTTP API Connection, OAuth 2.0 Client Credentials, REST callback, publish step, avoid polling, data export API, token_type Bearer, planning automation, external notification , KBA , LOD-ANA-PL-DA , Data Actions , Problem