Figma · Arazzo Workflow

Figma Audit Team Component

Version 1.0.0

List a team's published components, inspect one, and open its source file.

1 workflow 2 source APIs 1 provider
View Spec View on GitHub CollaborationDesignGraphicsInterfacesPrototypesPrototypingUI/UXArazzoWorkflows

Provider

figma

Workflows

audit-team-component
Trace a team-published component to its metadata and source file.
Lists a team's components, retrieves the first component by key, and opens the file that contains it.
3 steps inputs: pageSize, teamId outputs: componentFileKey, componentName, fileName
1
listTeamComponents
List the components published by the team library so a component can be selected for inspection.
2
getComponent
Retrieve the full metadata for the first published component, including the file key and node id it maps to.
3
openSourceFile
Open the file that contains the component to review its current document state.

Source API Descriptions

Arazzo Workflow Specification

Raw ↑
arazzo: 1.0.1
info:
  title: Figma Audit Team Component
  summary: List a team's published components, inspect one, and open its source file.
  description: >-
    A design-system audit flow that traces a published component back to the
    file it lives in. The workflow lists the components published by a team
    library, takes the key of the first component to retrieve its full
    metadata, and then opens the file that contains the component so its
    current document state can be reviewed. Every step spells out its request
    inline so the flow can be read and executed without opening the underlying
    OpenAPI description. Authentication is carried by the Figma personal access
    token bearer credential declared on each operation's security requirement.
  version: 1.0.0
  x-realizes-capability-ids:
  - BC-4200.30
  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-4200.30
      capability_name: Software Design Management
      spec: figma-files-api-openapi.yml
      confidence: 0.7
    model: Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities, CC BY 4.0
sourceDescriptions:
- name: componentsApi
  url: ../openapi/figma-components-api-openapi.yml
  type: openapi
- name: filesApi
  url: ../openapi/figma-files-api-openapi.yml
  type: openapi
workflows:
- workflowId: audit-team-component
  summary: Trace a team-published component to its metadata and source file.
  description: >-
    Lists a team's components, retrieves the first component by key, and opens
    the file that contains it.
  inputs:
    type: object
    required:
    - teamId
    properties:
      teamId:
        type: string
        description: The ID of the team whose published components are listed.
      pageSize:
        type: integer
        description: Number of components to return per page.
  steps:
  - stepId: listTeamComponents
    description: >-
      List the components published by the team library so a component can be
      selected for inspection.
    operationId: getTeamComponents
    parameters:
    - name: team_id
      in: path
      value: $inputs.teamId
    - name: page_size
      in: query
      value: $inputs.pageSize
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      components: $response.body#/meta/components
      firstComponentKey: $response.body#/meta/components/0/key
  - stepId: getComponent
    description: >-
      Retrieve the full metadata for the first published component, including
      the file key and node id it maps to.
    operationId: getComponent
    parameters:
    - name: key
      in: path
      value: $steps.listTeamComponents.outputs.firstComponentKey
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      componentFileKey: $response.body#/meta/file_key
      componentNodeId: $response.body#/meta/node_id
      componentName: $response.body#/meta/name
  - stepId: openSourceFile
    description: >-
      Open the file that contains the component to review its current document
      state.
    operationId: getFile
    parameters:
    - name: file_key
      in: path
      value: $steps.getComponent.outputs.componentFileKey
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      fileName: $response.body#/name
      lastModified: $response.body#/lastModified
  outputs:
    componentName: $steps.getComponent.outputs.componentName
    componentFileKey: $steps.getComponent.outputs.componentFileKey
    fileName: $steps.openSourceFile.outputs.fileName

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/figma-audit-team-component-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.