Temporal · Arazzo Workflow

Temporal Deprovision a User and Confirm Removal

Version 1.0.0

Read a User to confirm it exists, delete it, then verify it is gone.

1 workflow 1 source API 1 provider
View Spec View on GitHub Pro-Code-API-CompositionWorkflowsArazzoWorkflows

Provider

temporal

Workflows

deprovision-user
Confirm, delete, and verify removal of a User.
Chains getUser (confirm it exists), deleteUser (remove it), and a final getUser that branches on a 404 status to verify deletion.
3 steps inputs: bearerToken, userId outputs: finalStatus, stateBeforeDelete
1
confirmUser
Read the User to confirm it exists before deletion and capture its email for the audit record.
2
deleteUser
Delete the User account. A 200 indicates the deletion was accepted.
3
verifyGone
Re-read the User expecting a 404 Not Found, confirming the account was removed.

Source API Descriptions

Arazzo Workflow Specification

Raw ↑
arazzo: 1.0.1
info:
  title: Temporal Deprovision a User and Confirm Removal
  summary: Read a User to confirm it exists, delete it, then verify it is gone.
  description: >-
    Offboarding from Temporal Cloud removes a User account. This workflow reads
    the User to confirm the target exists and capture its email, deletes the
    User, then re-reads expecting a 404 to verify removal. 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
  x-realizes-capability-ids:
  - BC-620.20
  x-capability-derivation:
    method: 'deterministic join: sourceDescriptions -> per-tag OpenAPI -> tag/capability edge. No classification at this step.'
    min_confidence: 0.7
    sources:
    - capability_id: BC-620.20
      capability_name: Identity & Access Management
      spec: temporal-users-api-openapi.yml
      confidence: 0.75
    model: Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities, CC BY 4.0
sourceDescriptions:
- name: usersApi
  url: ../openapi/temporal-users-api-openapi.yml
  type: openapi
workflows:
- workflowId: deprovision-user
  summary: Confirm, delete, and verify removal of a User.
  description: >-
    Chains getUser (confirm it exists), deleteUser (remove it), and a final
    getUser that branches on a 404 status to verify deletion.
  inputs:
    type: object
    required:
    - bearerToken
    - userId
    properties:
      bearerToken:
        type: string
        description: API key used as the Bearer token for Authorization.
      userId:
        type: string
        description: The User identifier to deprovision.
  steps:
  - stepId: confirmUser
    description: >-
      Read the User to confirm it exists before deletion and capture its email
      for the audit record.
    operationId: getUser
    parameters:
    - name: Authorization
      in: header
      value: "Bearer $inputs.bearerToken"
    - name: userId
      in: path
      value: $inputs.userId
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      stateBeforeDelete: $response.body#/state
  - stepId: deleteUser
    description: >-
      Delete the User account. A 200 indicates the deletion was accepted.
    operationId: deleteUser
    parameters:
    - name: Authorization
      in: header
      value: "Bearer $inputs.bearerToken"
    - name: userId
      in: path
      value: $inputs.userId
    successCriteria:
    - condition: $statusCode == 200
  - stepId: verifyGone
    description: >-
      Re-read the User expecting a 404 Not Found, confirming the account was
      removed.
    operationId: getUser
    parameters:
    - name: Authorization
      in: header
      value: "Bearer $inputs.bearerToken"
    - name: userId
      in: path
      value: $inputs.userId
    successCriteria:
    - condition: $statusCode == 404
    outputs:
      finalStatus: $statusCode
  outputs:
    stateBeforeDelete: $steps.confirmUser.outputs.stateBeforeDelete
    finalStatus: $steps.verifyGone.outputs.finalStatus

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/temporal-deprovision-user-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.