Azure Web PubSub · Arazzo Workflow

Azure Web PubSub Grant Permission if Missing

Version 1.0.0

Check whether a connection already holds a permission, granting it only when absent.

1 workflow 1 source API 1 provider
View Spec View on GitHub MessagingPub-SubReal-TimeServerlessWebSocketsArazzoWorkflows

Provider

microsoft-azure-web-pubsub

Workflows

grant-permission-if-missing
Check a connection's permission, then grant it only if not already held.
Probes a permission with checkPermission and branches: when the HEAD returns 404 it grants via grantPermission, when it returns 200 it ends.
2 steps inputs: accessToken, apiVersion, connectionId, hub, permission, targetName outputs: checkStatus, grantStatus
1
checkPermission
webPubSub_checkPermission
Probe whether the connection already holds the permission. A 200 means it does; a 404 means it does not.
2
grantPermission
webPubSub_grantPermission
Grant the connection the permission, optionally scoped to a target group name.

Source API Descriptions

Arazzo Workflow Specification

Raw ↑
arazzo: 1.0.1
info:
  title: Azure Web PubSub Grant Permission if Missing
  summary: Check whether a connection already holds a permission, granting it only when absent.
  description: >-
    An idempotent authorization pattern: before granting, the app server checks
    whether the connection already holds the permission so it does not issue a
    redundant grant. When the permission is missing it is granted; when already
    present the flow ends. Each step inlines its request — Authorization bearer
    header, required api-version query, and documented HEAD 200/404 and PUT 200
    status codes — so the flow is self-describing.
  version: 1.0.0
sourceDescriptions:
- name: webPubSubApi
  url: ../openapi/microsoft-azure-web-pubsub-openapi.yml
  type: openapi
workflows:
- workflowId: grant-permission-if-missing
  summary: Check a connection's permission, then grant it only if not already held.
  description: >-
    Probes a permission with checkPermission and branches: when the HEAD returns
    404 it grants via grantPermission, when it returns 200 it ends.
  inputs:
    type: object
    required:
    - accessToken
    - hub
    - permission
    - connectionId
    properties:
      accessToken:
        type: string
        description: JWT bearer token for the Web PubSub data plane.
      apiVersion:
        type: string
        description: Data plane REST API version.
        default: "2024-01-01"
      hub:
        type: string
        description: Target hub name.
      permission:
        type: string
        description: Permission to check and grant.
        enum:
        - sendToGroup
        - joinLeaveGroup
      connectionId:
        type: string
        description: The connection id to check and grant.
      targetName:
        type: string
        description: Optional target group name the permission applies to.
  steps:
  - stepId: checkPermission
    description: >-
      Probe whether the connection already holds the permission. A 200 means it
      does; a 404 means it does not.
    operationId: webPubSub_checkPermission
    parameters:
    - name: Authorization
      in: header
      value: "Bearer $inputs.accessToken"
    - name: hub
      in: path
      value: $inputs.hub
    - name: permission
      in: path
      value: $inputs.permission
    - name: connectionId
      in: path
      value: $inputs.connectionId
    - name: api-version
      in: query
      value: $inputs.apiVersion
    successCriteria:
    - condition: $statusCode == 200 || $statusCode == 404
    outputs:
      checkStatus: $statusCode
    onSuccess:
    - name: permissionMissing
      type: goto
      stepId: grantPermission
      criteria:
      - condition: $statusCode == 404
    - name: permissionPresent
      type: end
      criteria:
      - condition: $statusCode == 200
  - stepId: grantPermission
    description: >-
      Grant the connection the permission, optionally scoped to a target group
      name.
    operationId: webPubSub_grantPermission
    parameters:
    - name: Authorization
      in: header
      value: "Bearer $inputs.accessToken"
    - name: hub
      in: path
      value: $inputs.hub
    - name: permission
      in: path
      value: $inputs.permission
    - name: connectionId
      in: path
      value: $inputs.connectionId
    - name: api-version
      in: query
      value: $inputs.apiVersion
    - name: targetName
      in: query
      value: $inputs.targetName
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      grantStatus: $statusCode
  outputs:
    checkStatus: $steps.checkPermission.outputs.checkStatus
    grantStatus: $steps.grantPermission.outputs.grantStatus

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-azure-web-pubsub-grant-permission-if-missing-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 email required.

A second provider on the same verified email joins the account you already have.