Temporal · Arazzo Workflow

Temporal Provision a User and Verify Membership

Version 1.0.0

Create a User, then page Users to confirm the new account appears.

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

Provider

temporal

Workflows

provision-user
Create a User and confirm it via the Users listing.
Chains createUser with listUsers so the newly created account can be confirmed against the live directory.
2 steps inputs: access, bearerToken, email, pageSize outputs: nextPageToken, users
1
createUser
Create the User from the supplied email and access spec.
2
confirmUser
List Users to confirm the new account is present in the account directory and capture the page token for any further paging.

Source API Descriptions

Arazzo Workflow Specification

Raw ↑
arazzo: 1.0.1
info:
  title: Temporal Provision a User and Verify Membership
  summary: Create a User, then page Users to confirm the new account appears.
  description: >-
    Onboarding into Temporal Cloud means creating a User with an email and an
    access spec. This workflow creates the User, then lists Users so a caller can
    confirm the new account is present and capture the page token for further
    paging. 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: provision-user
  summary: Create a User and confirm it via the Users listing.
  description: >-
    Chains createUser with listUsers so the newly created account can be
    confirmed against the live directory.
  inputs:
    type: object
    required:
    - bearerToken
    - email
    - access
    properties:
      bearerToken:
        type: string
        description: API key used as the Bearer token for Authorization.
      email:
        type: string
        description: The email address of the User to create.
      access:
        type: object
        description: The access spec object granting the User roles and scopes.
      pageSize:
        type: integer
        description: Number of Users to return per page when confirming.
        default: 50
  steps:
  - stepId: createUser
    description: >-
      Create the User from the supplied email and access spec.
    operationId: createUser
    parameters:
    - name: Authorization
      in: header
      value: "Bearer $inputs.bearerToken"
    requestBody:
      contentType: application/json
      payload:
        spec:
          email: $inputs.email
          access: $inputs.access
    successCriteria:
    - condition: $statusCode == 200
    onSuccess:
    - name: confirm
      type: goto
      stepId: confirmUser
      criteria:
      - condition: $statusCode == 200
  - stepId: confirmUser
    description: >-
      List Users to confirm the new account is present in the account directory
      and capture the page token for any further paging.
    operationId: listUsers
    parameters:
    - name: Authorization
      in: header
      value: "Bearer $inputs.bearerToken"
    - name: pageSize
      in: query
      value: $inputs.pageSize
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      users: $response.body#/users
      nextPageToken: $response.body#/nextPageToken
  outputs:
    users: $steps.confirmUser.outputs.users
    nextPageToken: $steps.confirmUser.outputs.nextPageToken

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-provision-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.