SAP Integration Suite · Arazzo Workflow

SAP Integration Suite Trace Message By GUID

Version 1.0.0

Read a single message processing log by GUID, pull its adapter attributes, and find correlated messages.

1 workflow 1 source API 1 provider
View Spec View on GitHub API ManagementCloud IntegrationEnterprise IntegrationEvent MeshiPaaSSAPSAP BTPArazzoWorkflows

Provider

sap-integration-suite

Workflows

trace-message-by-guid
Read a message log, fetch adapter attributes, and list correlated messages.
Reads a message processing log by GUID, retrieves its adapter attributes, and lists messages sharing its correlation id to reconstruct the exchange.
3 steps inputs: messageGuid outputs: adapterAttributes, correlatedLogs, correlationId, status
1
getLog
Read the message processing log by GUID to capture status and correlation id.
2
getAdapterAttributes
Retrieve adapter-specific attributes for the traced message.
3
listCorrelated
List other message processing logs sharing the same correlation id to reconstruct the full exchange.

Source API Descriptions

Arazzo Workflow Specification

Raw ↑
arazzo: 1.0.1
info:
  title: SAP Integration Suite Trace Message By GUID
  summary: Read a single message processing log by GUID, pull its adapter attributes, and find correlated messages.
  description: >-
    A single-message tracing workflow for Cloud Integration. The workflow reads
    a message processing log by its GUID to capture its status and correlation
    id, retrieves the adapter-specific attributes for that message, and then
    lists other message processing logs sharing the same correlation id so a
    full message exchange can be reconstructed. Every step spells out its
    request inline so the flow can be read and executed without opening the
    underlying OpenAPI description.
  version: 1.0.0
sourceDescriptions:
- name: messageProcessingLogsApi
  url: ../openapi/sap-integration-suite-message-processing-logs-api-openapi.yml
  type: openapi
workflows:
- workflowId: trace-message-by-guid
  summary: Read a message log, fetch adapter attributes, and list correlated messages.
  description: >-
    Reads a message processing log by GUID, retrieves its adapter attributes,
    and lists messages sharing its correlation id to reconstruct the exchange.
  inputs:
    type: object
    required:
    - messageGuid
    properties:
      messageGuid:
        type: string
        description: GUID of the message processing log to trace.
  steps:
  - stepId: getLog
    description: Read the message processing log by GUID to capture status and correlation id.
    operationId: getMessageProcessingLog
    parameters:
    - name: MessageGuid
      in: path
      value: $inputs.messageGuid
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      status: $response.body#/d/Status
      correlationId: $response.body#/d/CorrelationId
      integrationFlowName: $response.body#/d/IntegrationFlowName
  - stepId: getAdapterAttributes
    description: Retrieve adapter-specific attributes for the traced message.
    operationId: getMessageProcessingLogAdapterAttributes
    parameters:
    - name: MessageGuid
      in: path
      value: $inputs.messageGuid
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      adapterAttributes: $response.body#/d
  - stepId: listCorrelated
    description: >-
      List other message processing logs sharing the same correlation id to
      reconstruct the full exchange.
    operationId: listMessageProcessingLogs
    parameters:
    - name: $filter
      in: query
      value: "CorrelationId eq '$steps.getLog.outputs.correlationId'"
    - name: $orderby
      in: query
      value: "LogStart asc"
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      correlatedLogs: $response.body#/d/results
  outputs:
    status: $steps.getLog.outputs.status
    correlationId: $steps.getLog.outputs.correlationId
    adapterAttributes: $steps.getAdapterAttributes.outputs.adapterAttributes
    correlatedLogs: $steps.listCorrelated.outputs.correlatedLogs

Work with this as data

Every workflow here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for arazzo workflows

4 MCP tools reach this
  • find_arazzoBrowse and filter every workflow in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This workflow
curl "https://apis.io/api/v1/arazzo/sap-integration-suite-trace-message-by-guid-workflow"
All arazzo workflows
curl "https://apis.io/api/v1/arazzo?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.