Google Cloud Platform · Arazzo Workflow

Google Cloud Platform Rename Folder and Poll Operation

Version 1.0.0

Read a folder, patch its display name, poll the operation, then confirm the new name.

1 workflow 2 source APIs 1 provider
View Spec View on GitHub API ManagementCloud ComputingInfrastructurePlatform-as-a-ServiceArazzoWorkflows

Provider

google-cloud-platform

Workflows

rename-folder-and-poll
Rename a Google Cloud folder and wait for the operation to complete.
Reads the current display name, patches the folder, polls the operation until done, then re-reads to confirm.
4 steps inputs: displayName, folderId outputs: newName, operationName, previousName
1
getBefore
Read the folder to capture the current display name before the change.
2
patchFolder
Patch the folder display name with an update mask scoped to displayName. Returns a long-running Operation whose name is used to poll.
3
pollOperation
Poll the patch operation by name until the done flag is true.
4
getAfter
Re-read the folder to confirm the new display name took effect.

Source API Descriptions

Arazzo Workflow Specification

Raw ↑
arazzo: 1.0.1
info:
  title: Google Cloud Platform Rename Folder and Poll Operation
  summary: Read a folder, patch its display name, poll the operation, then confirm the new name.
  description: >-
    Updates the display name of an existing folder. Folder updates are
    asynchronous, so the patch call returns a long-running Operation whose name
    is polled with operations.get until done, after which the folder is re-read
    to confirm the new display name. 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: foldersApi
  url: ../openapi/google-cloud-platform-folders-api-openapi.yml
  type: openapi
- name: operationsApi
  url: ../openapi/google-cloud-platform-operations-api-openapi.yml
  type: openapi
workflows:
- workflowId: rename-folder-and-poll
  summary: Rename a Google Cloud folder and wait for the operation to complete.
  description: >-
    Reads the current display name, patches the folder, polls the operation
    until done, then re-reads to confirm.
  inputs:
    type: object
    required:
    - folderId
    - displayName
    properties:
      folderId:
        type: string
        description: The folder resource id to rename (e.g. 500123).
      displayName:
        type: string
        description: The new display name to set on the folder.
  steps:
  - stepId: getBefore
    description: >-
      Read the folder to capture the current display name before the change.
    operationId: cloudresourcemanager.folders.get
    parameters:
    - name: folderId
      in: path
      value: $inputs.folderId
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      previousName: $response.body#/displayName
  - stepId: patchFolder
    description: >-
      Patch the folder display name with an update mask scoped to displayName.
      Returns a long-running Operation whose name is used to poll.
    operationId: cloudresourcemanager.folders.patch
    parameters:
    - name: folderId
      in: path
      value: $inputs.folderId
    - name: updateMask
      in: query
      value: displayName
    requestBody:
      contentType: application/json
      payload:
        displayName: $inputs.displayName
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      operationName: $response.body#/name
  - stepId: pollOperation
    description: >-
      Poll the patch operation by name until the done flag is true.
    operationId: cloudresourcemanager.operations.get
    parameters:
    - name: name
      in: path
      value: $steps.patchFolder.outputs.operationName
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      done: $response.body#/done
    onSuccess:
    - name: operationComplete
      type: goto
      stepId: getAfter
      criteria:
      - context: $response.body
        condition: $.done == true
        type: jsonpath
    - name: stillRunning
      type: goto
      stepId: pollOperation
      criteria:
      - context: $response.body
        condition: $.done == false
        type: jsonpath
  - stepId: getAfter
    description: >-
      Re-read the folder to confirm the new display name took effect.
    operationId: cloudresourcemanager.folders.get
    parameters:
    - name: folderId
      in: path
      value: $inputs.folderId
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      newName: $response.body#/displayName
  outputs:
    previousName: $steps.getBefore.outputs.previousName
    newName: $steps.getAfter.outputs.newName
    operationName: $steps.patchFolder.outputs.operationName

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/google-cloud-platform-rename-folder-and-poll-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.