Appmixer · Arazzo Workflow

Appmixer Replay an Unprocessed Message

Version 1.0.0

List unprocessed messages and put the first one back into the engine.

1 workflow 1 source API 1 provider
View Spec View on GitHub AgenticAutomationEmbedded iPaaSIntegrationLow-CodeWorkflowsArazzoWorkflows

Provider

appmixer

Workflows

replay-unprocessed-message
Reprocess the first message in the unprocessed backlog.
Retrieves the list of unprocessed messages and, when at least one exists, reprocesses the first message back through the engine.
2 steps inputs: token outputs: reprocessedMessageId
1
listUnprocessedMessages
List the messages that failed to be processed by the engine.
2
reprocessMessage
Put the first unprocessed message back into the Appmixer engine.

Source API Descriptions

Arazzo Workflow Specification

Raw ↑
arazzo: 1.0.1
info:
  title: Appmixer Replay an Unprocessed Message
  summary: List unprocessed messages and put the first one back into the engine.
  description: >-
    A dead-letter recovery pattern for the Appmixer engine. The workflow lists
    the unprocessed messages that failed to be handled, takes the first message
    in the backlog, and reprocesses it by putting it back into the Appmixer
    engine so the flow run can complete. This lets operators replay stuck
    messages without manual reconstruction.
  version: 1.0.0
sourceDescriptions:
- name: messagesApi
  url: ../openapi/appmixer-messages-api-openapi.yml
  type: openapi
workflows:
- workflowId: replay-unprocessed-message
  summary: Reprocess the first message in the unprocessed backlog.
  description: >-
    Retrieves the list of unprocessed messages and, when at least one exists,
    reprocesses the first message back through the engine.
  inputs:
    type: object
    required:
    - token
    properties:
      token:
        type: string
        description: Appmixer access token obtained from /user/auth.
  steps:
  - stepId: listUnprocessedMessages
    description: List the messages that failed to be processed by the engine.
    operationId: listUnprocessedMessages
    parameters:
    - name: Authorization
      in: header
      value: Bearer $inputs.token
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      firstMessageId: $response.body#/0/messageId
    onSuccess:
    - name: hasMessages
      type: goto
      stepId: reprocessMessage
      criteria:
      - context: $response.body
        condition: $.length > 0
        type: jsonpath
    - name: noMessages
      type: end
      criteria:
      - context: $response.body
        condition: $.length == 0
        type: jsonpath
  - stepId: reprocessMessage
    description: Put the first unprocessed message back into the Appmixer engine.
    operationId: reprocessMessage
    parameters:
    - name: Authorization
      in: header
      value: Bearer $inputs.token
    - name: messageId
      in: path
      value: $steps.listUnprocessedMessages.outputs.firstMessageId
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      reprocessedMessageId: $steps.listUnprocessedMessages.outputs.firstMessageId
  outputs:
    reprocessedMessageId: $steps.reprocessMessage.outputs.reprocessedMessageId

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/appmixer-reprocess-unprocessed-message-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.