Microsoft Power Automate · Arazzo Workflow

Microsoft Power Automate Audit a Flow's Connector Dependencies

Version 1.0.0

Resolve the connectors and connections a single flow depends on.

1 workflow 3 source APIs 1 provider
View Spec View on GitHub AutomationBusiness ProcessIntegrationLow-CodeMicrosoftPower PlatformRPAWorkflowsArazzoWorkflows

Provider

microsoft-power-automate

Workflows

connector-dependency-audit
Resolve a flow's connector and connection dependencies for migration or licensing review.
Reads a flow's connection references and definition summary, then resolves the environment's connector catalog, a specific connector's detail, and the environment's connections so the flow's true dependency set is known.
4 steps inputs: apiName, environmentName, flowName outputs: connectionReferences, connections, connectorIsCustom, connectorTier, connectors, flowDisplayName
1
readFlow
Read the flow to surface the connection references it declares and the definition summary listing the connector each action calls.
2
listEnvironmentConnectors
List the connectors registered in the environment so the flow's declared dependencies can be checked against what the environment actually offers.
3
resolveConnector
Resolve the connector in detail to establish its display name, tier, and whether it is a custom API. Tier is what determines premium licensing, and custom APIs are what break an environment-to-environment migration.
4
listEnvironmentConnections
List the environment's connections so each connection reference the flow declares can be matched to a real, authenticated connection.

Source API Descriptions

Arazzo Workflow Specification

Raw ↑
arazzo: 1.0.1
info:
  title: Microsoft Power Automate Audit a Flow's Connector Dependencies
  summary: Resolve the connectors and connections a single flow depends on.
  description: >-
    Before migrating a flow between environments, or answering whether a flow
    touches a premium or custom connector, an operator has to resolve what the
    flow actually depends on. This workflow reads the flow to surface its
    connection references and action-level connector usage, lists the connectors
    registered in the environment, resolves one connector in detail to establish
    its tier and whether it is a custom API, and lists the environment's
    connections to confirm the flow's references are backed by real credentials.
    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: connectionsApi
  url: ../openapi/microsoft-power-automate-connections-api-openapi.yml
  type: openapi
- name: connectorsApi
  url: ../openapi/microsoft-power-automate-connectors-api-openapi.yml
  type: openapi
- name: flowsApi
  url: ../openapi/microsoft-power-automate-flows-api-openapi.yml
  type: openapi
workflows:
- workflowId: connector-dependency-audit
  summary: Resolve a flow's connector and connection dependencies for migration or licensing review.
  description: >-
    Reads a flow's connection references and definition summary, then resolves
    the environment's connector catalog, a specific connector's detail, and the
    environment's connections so the flow's true dependency set is known.
  inputs:
    type: object
    required:
    - environmentName
    - flowName
    - apiName
    properties:
      environmentName:
        type: string
        description: The name of the environment holding the flow.
      flowName:
        type: string
        description: The name or ID of the flow to audit.
      apiName:
        type: string
        description: >-
          The name of the connector to resolve in detail (e.g.
          shared_commondataserviceforapps).
  steps:
  - stepId: readFlow
    description: >-
      Read the flow to surface the connection references it declares and the
      definition summary listing the connector each action calls.
    operationId: getFlow
    parameters:
    - name: environmentName
      in: path
      value: $inputs.environmentName
    - name: flowName
      in: path
      value: $inputs.flowName
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      displayName: $response.body#/properties/displayName
      connectionReferences: $response.body#/properties/connectionReferences
      definitionSummary: $response.body#/properties/definitionSummary
      actions: $response.body#/properties/definitionSummary/actions
  - stepId: listEnvironmentConnectors
    description: >-
      List the connectors registered in the environment so the flow's declared
      dependencies can be checked against what the environment actually offers.
    operationId: listConnectors
    parameters:
    - name: environmentName
      in: path
      value: $inputs.environmentName
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      connectors: $response.body#/value
  - stepId: resolveConnector
    description: >-
      Resolve the connector in detail to establish its display name, tier, and
      whether it is a custom API. Tier is what determines premium licensing, and
      custom APIs are what break an environment-to-environment migration.
    operationId: getConnector
    parameters:
    - name: environmentName
      in: path
      value: $inputs.environmentName
    - name: apiName
      in: path
      value: $inputs.apiName
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      connectorDisplayName: $response.body#/properties/displayName
      tier: $response.body#/properties/tier
      isCustomApi: $response.body#/properties/isCustomApi
  - stepId: listEnvironmentConnections
    description: >-
      List the environment's connections so each connection reference the flow
      declares can be matched to a real, authenticated connection.
    operationId: listConnections
    parameters:
    - name: environmentName
      in: path
      value: $inputs.environmentName
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      connections: $response.body#/value
  outputs:
    flowDisplayName: $steps.readFlow.outputs.displayName
    connectionReferences: $steps.readFlow.outputs.connectionReferences
    connectors: $steps.listEnvironmentConnectors.outputs.connectors
    connectorTier: $steps.resolveConnector.outputs.tier
    connectorIsCustom: $steps.resolveConnector.outputs.isCustomApi
    connections: $steps.listEnvironmentConnections.outputs.connections

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-power-automate-connector-dependency-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.