Cisco Webex Post a Message and Reply in Thread

arazzo: 1.0.1
info:
  title: Cisco Webex Post a Message and Reply in Thread
  summary: Post a parent message to a room and then post a threaded reply to it.
  description: >-
    Creates a threaded conversation in a space. The workflow posts a parent
    message into a room, captures its message ID, and then posts a second
    message as a threaded reply by referencing the parent via parentId. 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: messagingApi
  url: ../openapi/cisco-webex-messaging-openapi.yml
  type: openapi
workflows:
- workflowId: reply-in-thread
  summary: Post a parent message, then post a threaded reply.
  description: >-
    Posts a parent message into a room and then posts a reply threaded under
    it using the parent message ID.
  inputs:
    type: object
    required:
    - accessToken
    - roomId
    - parentMarkdown
    - replyMarkdown
    properties:
      accessToken:
        type: string
        description: Webex API bearer access token.
      roomId:
        type: string
        description: The room ID to post the messages into.
      parentMarkdown:
        type: string
        description: The markdown content of the parent message.
      replyMarkdown:
        type: string
        description: The markdown content of the threaded reply.
  steps:
  - stepId: postParent
    description: Post the parent message into the room.
    operationId: createMessage
    parameters:
    - name: Authorization
      in: header
      value: Bearer $inputs.accessToken
    requestBody:
      contentType: application/json
      payload:
        roomId: $inputs.roomId
        markdown: $inputs.parentMarkdown
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      parentMessageId: $response.body#/id
  - stepId: postReply
    description: >-
      Post a threaded reply that references the parent message via parentId so
      it appears under the parent in the thread.
    operationId: createMessage
    parameters:
    - name: Authorization
      in: header
      value: Bearer $inputs.accessToken
    requestBody:
      contentType: application/json
      payload:
        roomId: $inputs.roomId
        parentId: $steps.postParent.outputs.parentMessageId
        markdown: $inputs.replyMarkdown
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      replyMessageId: $response.body#/id
  outputs:
    parentMessageId: $steps.postParent.outputs.parentMessageId
    replyMessageId: $steps.postReply.outputs.replyMessageId