Claude · Arazzo Workflow

Claude Multi-Turn Conversation

Version 1.0.0

Send a first user turn, then continue the conversation with a follow-up that includes the assistant's reply.

1 workflow 1 source API 1 provider
View Spec View on GitHub Artificial IntelligenceChatbotsConversational AIGenerative AILarge Language ModelsMachine-LearningNatural Language ProcessingArazzoWorkflows

Provider

claude

Workflows

multi-turn-conversation
Chain two Messages API calls into a single multi-turn conversation.
Sends an opening user prompt, then sends a follow-up prompt that includes the prior user and assistant turns so the model continues with full context.
2 steps inputs: anthropicVersion, apiKey, firstPrompt, followUpPrompt, maxTokens, model outputs: content, firstMessageId, followUpMessageId, usage
1
openingTurn
Send the opening user message and capture the assistant's reply content so it can be replayed as context in the next turn.
2
followUpTurn
Send the follow-up user message with the prior user turn and assistant reply included so the model continues the conversation with full context.

Source API Descriptions

Arazzo Workflow Specification

Raw ↑
arazzo: 1.0.1
info:
  title: Claude Multi-Turn Conversation
  summary: Send a first user turn, then continue the conversation with a follow-up that includes the assistant's reply.
  description: >-
    A two-turn conversation flow. The workflow sends an opening user message,
    captures the assistant's text reply, and then issues a second request that
    replays the full conversation — the original user turn, the assistant
    response, and a new follow-up user turn — so the model has the prior context.
    This demonstrates how the stateless Messages API is chained into a
    multi-turn dialogue. Every step spells out its request inline — including
    the required x-api-key and anthropic-version headers — so the flow can be
    read and executed without opening the underlying OpenAPI description.
  version: 1.0.0
sourceDescriptions:
- name: messagesApi
  url: ../openapi/claude-messages-api-openapi.yml
  type: openapi
workflows:
- workflowId: multi-turn-conversation
  summary: Chain two Messages API calls into a single multi-turn conversation.
  description: >-
    Sends an opening user prompt, then sends a follow-up prompt that includes
    the prior user and assistant turns so the model continues with full context.
  inputs:
    type: object
    required:
    - apiKey
    - model
    - firstPrompt
    - followUpPrompt
    properties:
      apiKey:
        type: string
        description: Anthropic API key sent in the x-api-key header.
      anthropicVersion:
        type: string
        description: Value for the required anthropic-version header.
        default: '2023-06-01'
      model:
        type: string
        description: The model to use for both turns of the conversation.
      firstPrompt:
        type: string
        description: The opening user message.
      followUpPrompt:
        type: string
        description: The follow-up user message sent after the assistant replies.
      maxTokens:
        type: integer
        description: Maximum number of tokens to generate per turn.
        default: 1024
  steps:
  - stepId: openingTurn
    description: >-
      Send the opening user message and capture the assistant's reply content
      so it can be replayed as context in the next turn.
    operationId: createMessage
    parameters:
    - name: x-api-key
      in: header
      value: $inputs.apiKey
    - name: anthropic-version
      in: header
      value: $inputs.anthropicVersion
    requestBody:
      contentType: application/json
      payload:
        model: $inputs.model
        max_tokens: $inputs.maxTokens
        messages:
        - role: user
          content: $inputs.firstPrompt
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      firstMessageId: $response.body#/id
      assistantContent: $response.body#/content
      stopReason: $response.body#/stop_reason
  - stepId: followUpTurn
    description: >-
      Send the follow-up user message with the prior user turn and assistant
      reply included so the model continues the conversation with full context.
    operationId: createMessage
    parameters:
    - name: x-api-key
      in: header
      value: $inputs.apiKey
    - name: anthropic-version
      in: header
      value: $inputs.anthropicVersion
    requestBody:
      contentType: application/json
      payload:
        model: $inputs.model
        max_tokens: $inputs.maxTokens
        messages:
        - role: user
          content: $inputs.firstPrompt
        - role: assistant
          content: $steps.openingTurn.outputs.assistantContent
        - role: user
          content: $inputs.followUpPrompt
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      followUpMessageId: $response.body#/id
      content: $response.body#/content
      stopReason: $response.body#/stop_reason
      usage: $response.body#/usage
  outputs:
    firstMessageId: $steps.openingTurn.outputs.firstMessageId
    followUpMessageId: $steps.followUpTurn.outputs.followUpMessageId
    content: $steps.followUpTurn.outputs.content
    usage: $steps.followUpTurn.outputs.usage

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/claude-multi-turn-conversation-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.