Figma · Arazzo Workflow

Figma Post and Verify Comment

Version 1.0.0

Post a new comment to a file, then read the thread back to confirm it landed.

1 workflow 1 source API 1 provider
View Spec View on GitHub CollaborationDesignGraphicsInterfacesPrototypesPrototypingUI/UXArazzoWorkflows

Provider

figma

Workflows

post-and-verify-comment
Post a comment to a Figma file and verify it by reading the thread.
Posts a comment message to a file and then re-reads the comment thread to confirm the comment was created.
2 steps inputs: fileKey, message outputs: commentId, comments
1
postComment
Post a new root-level comment with the supplied message text onto the file.
2
verifyComments
Read the file comment thread back so the newly created comment can be confirmed present.

Source API Descriptions

Arazzo Workflow Specification

Raw ↑
arazzo: 1.0.1
info:
  title: Figma Post and Verify Comment
  summary: Post a new comment to a file, then read the thread back to confirm it landed.
  description: >-
    A write-then-read confirmation flow for file feedback. The workflow posts a
    new comment onto a file, optionally pinned to a canvas position, and then
    reads the file's comment thread back so the caller can confirm the new
    comment is present. 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
sourceDescriptions:
- name: commentsApi
  url: ../openapi/figma-comments-api-openapi.yml
  type: openapi
workflows:
- workflowId: post-and-verify-comment
  summary: Post a comment to a Figma file and verify it by reading the thread.
  description: >-
    Posts a comment message to a file and then re-reads the comment thread to
    confirm the comment was created.
  inputs:
    type: object
    required:
    - fileKey
    - message
    properties:
      fileKey:
        type: string
        description: The key of the Figma file to comment on.
      message:
        type: string
        description: The text body of the comment to post.
  steps:
  - stepId: postComment
    description: >-
      Post a new root-level comment with the supplied message text onto the
      file.
    operationId: postComment
    parameters:
    - name: file_key
      in: path
      value: $inputs.fileKey
    requestBody:
      contentType: application/json
      payload:
        message: $inputs.message
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      commentId: $response.body#/id
      orderId: $response.body#/order_id
      createdAt: $response.body#/created_at
  - stepId: verifyComments
    description: >-
      Read the file comment thread back so the newly created comment can be
      confirmed present.
    operationId: getComments
    parameters:
    - name: file_key
      in: path
      value: $inputs.fileKey
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      comments: $response.body#/comments
  outputs:
    commentId: $steps.postComment.outputs.commentId
    comments: $steps.verifyComments.outputs.comments

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-post-and-verify-comment-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.