Microsoft Word · Arazzo Workflow

Microsoft Word Rename Move and Audit Document

Version 1.0.0

Rename a Word document, move it to a new folder, and list its version history.

1 workflow 2 source APIs 1 provider
View Spec View on GitHub DocumentsMicrosoft-365OfficeProductivityWord ProcessingArazzoWorkflows

Provider

microsoft-word

Workflows

rename-move-audit
Rename a document, relocate it, and review its versions.
Updates a drive item's name, moves it under a new parent folder, and lists the resulting version history.
3 steps inputs: itemId, newName, targetFolderId outputs: itemId, latestVersionId, name
1
renameItem
Rename the document by updating its name metadata. Graph returns 200 with the updated drive item.
2
moveItem
Move the document into the destination folder by updating its parent reference. Graph returns 200 with the moved drive item.
3
listVersions
List the version history of the relocated document so the change can be audited. Graph returns 200 with the collection of versions.

Source API Descriptions

Arazzo Workflow Specification

Raw ↑
arazzo: 1.0.1
info:
  title: Microsoft Word Rename Move and Audit Document
  summary: Rename a Word document, move it to a new folder, and list its version history.
  description: >-
    A document housekeeping flow for OneDrive using Microsoft Graph. The workflow
    renames a drive item by updating its metadata, moves it into a different
    parent folder, and then lists the version history so the relocation can be
    audited. 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: driveItemsApi
  url: ../openapi/microsoft-word-drive-items-api-openapi.yml
  type: openapi
- name: versionsApi
  url: ../openapi/microsoft-word-versions-api-openapi.yml
  type: openapi
workflows:
- workflowId: rename-move-audit
  summary: Rename a document, relocate it, and review its versions.
  description: >-
    Updates a drive item's name, moves it under a new parent folder, and lists
    the resulting version history.
  inputs:
    type: object
    required:
    - itemId
    - newName
    - targetFolderId
    properties:
      itemId:
        type: string
        description: The drive item identifier of the document.
      newName:
        type: string
        description: The new name to apply to the document.
      targetFolderId:
        type: string
        description: The identifier of the destination parent folder.
  steps:
  - stepId: renameItem
    description: >-
      Rename the document by updating its name metadata. Graph returns 200 with
      the updated drive item.
    operationId: updateDriveItem
    parameters:
    - name: item-id
      in: path
      value: $inputs.itemId
    requestBody:
      contentType: application/json
      payload:
        name: $inputs.newName
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      itemId: $response.body#/id
      name: $response.body#/name
  - stepId: moveItem
    description: >-
      Move the document into the destination folder by updating its parent
      reference. Graph returns 200 with the moved drive item.
    operationId: moveDriveItem
    parameters:
    - name: item-id
      in: path
      value: $steps.renameItem.outputs.itemId
    requestBody:
      contentType: application/json
      payload:
        parentReference:
          id: $inputs.targetFolderId
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      itemId: $response.body#/id
      parentId: $response.body#/parentReference/id
  - stepId: listVersions
    description: >-
      List the version history of the relocated document so the change can be
      audited. Graph returns 200 with the collection of versions.
    operationId: listVersions
    parameters:
    - name: item-id
      in: path
      value: $steps.moveItem.outputs.itemId
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      versions: $response.body#/value
      latestVersionId: $response.body#/value/0/id
  outputs:
    itemId: $steps.moveItem.outputs.itemId
    name: $steps.renameItem.outputs.name
    latestVersionId: $steps.listVersions.outputs.latestVersionId

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/microsoft-word-rename-move-and-audit-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.