ReadMe · Arazzo Workflow

ReadMe Upsert A Changelog Post

Version 1.0.0

Find a changelog post by slug and update it if it exists, otherwise create it.

1 workflow 1 source API 1 provider
View Spec View on GitHub DocumentationDeveloper HubAPI ReferencePortalAnalyticsArtificial IntelligenceMCPBi-Directional SyncArazzoWorkflows

Provider

readme

Workflows

upsert-changelog-post
Update a changelog post if its slug exists, otherwise create it.
Lists changelog posts on the branch, looks for one whose slug matches the target, and branches to update the existing post or create a new one.
3 steps inputs: apiKey, body, branch, slug, title, type outputs: createdSlug, updatedSlug
1
listChangelogs
{$sourceDescriptions.changelogApi.url}#/paths/~1branches~1{branch}~1changelogs/get
List changelog posts on the branch to detect whether the target slug exists.
2
updateChangelog
{$sourceDescriptions.changelogApi.url}#/paths/~1branches~1{branch}~1changelogs~1{slug}/put
Update the existing changelog post identified by slug.
3
createChangelog
{$sourceDescriptions.changelogApi.url}#/paths/~1branches~1{branch}~1changelogs/post
Create a new changelog post when no post with the target slug exists.

Source API Descriptions

Arazzo Workflow Specification

Raw ↑
arazzo: 1.0.1
info:
  title: ReadMe Upsert A Changelog Post
  summary: Find a changelog post by slug and update it if it exists, otherwise create it.
  description: >-
    Lets release tooling idempotently publish a changelog entry. The workflow
    lists changelog posts on the branch, branches on whether a post with the
    target slug is present, and then either updates the matched post or creates
    a new one. 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: changelogApi
  url: ../openapi/readme-changelog-api-openapi.yml
  type: openapi
workflows:
- workflowId: upsert-changelog-post
  summary: Update a changelog post if its slug exists, otherwise create it.
  description: >-
    Lists changelog posts on the branch, looks for one whose slug matches the
    target, and branches to update the existing post or create a new one.
  inputs:
    type: object
    required:
    - branch
    - slug
    - title
    - body
    - type
    properties:
      branch:
        type: string
        description: The branch (version) the changelog post lives on.
      slug:
        type: string
        description: The slug of the changelog post to upsert.
      title:
        type: string
        description: The changelog post title to write.
      body:
        type: string
        description: The Markdown body to write.
      type:
        type: string
        description: The change type (added | fixed | improved | deprecated | removed).
      apiKey:
        type: string
        description: ReadMe API key used as a Bearer token.
  steps:
  - stepId: listChangelogs
    description: List changelog posts on the branch to detect whether the target slug exists.
    operationPath: '{$sourceDescriptions.changelogApi.url}#/paths/~1branches~1{branch}~1changelogs/get'
    parameters:
    - name: branch
      in: path
      value: $inputs.branch
    - name: Authorization
      in: header
      value: "Bearer $inputs.apiKey"
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      changelogs: $response.body
    onSuccess:
    - name: postExists
      type: goto
      stepId: updateChangelog
      criteria:
      - context: $response.body
        condition: $[?(@.slug == $inputs.slug)]
        type: jsonpath
    - name: postMissing
      type: goto
      stepId: createChangelog
      criteria:
      - context: $response.body
        condition: $[?(@.slug == $inputs.slug)].length == 0
        type: jsonpath
  - stepId: updateChangelog
    description: Update the existing changelog post identified by slug.
    operationPath: '{$sourceDescriptions.changelogApi.url}#/paths/~1branches~1{branch}~1changelogs~1{slug}/put'
    parameters:
    - name: branch
      in: path
      value: $inputs.branch
    - name: slug
      in: path
      value: $inputs.slug
    - name: Authorization
      in: header
      value: "Bearer $inputs.apiKey"
    requestBody:
      contentType: application/json
      payload:
        title: $inputs.title
        body: $inputs.body
        type: $inputs.type
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      slug: $response.body#/slug
    onSuccess:
    - name: done
      type: end
  - stepId: createChangelog
    description: Create a new changelog post when no post with the target slug exists.
    operationPath: '{$sourceDescriptions.changelogApi.url}#/paths/~1branches~1{branch}~1changelogs/post'
    parameters:
    - name: branch
      in: path
      value: $inputs.branch
    - name: Authorization
      in: header
      value: "Bearer $inputs.apiKey"
    requestBody:
      contentType: application/json
      payload:
        title: $inputs.title
        body: $inputs.body
        type: $inputs.type
    successCriteria:
    - condition: $statusCode == 201
    outputs:
      slug: $response.body#/slug
  outputs:
    updatedSlug: $steps.updateChangelog.outputs.slug
    createdSlug: $steps.createChangelog.outputs.slug

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/readme-upsert-changelog-post-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.