Figma · Arazzo Workflow

Figma Render File Node Images

Version 1.0.0

Open a file, drill into specific nodes, and render them to image URLs.

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

Provider

figma

Workflows

render-file-node-images
Render selected nodes of a Figma file to downloadable image URLs.
Retrieves the file document, validates the requested nodes, and renders them to image URLs that remain available for fourteen days.
3 steps inputs: fileKey, format, ids, scale outputs: fileName, images
1
getFile
Retrieve the document tree for the file to confirm it exists and is accessible before drilling into specific nodes.
2
getNodes
Fetch the specific nodes referenced by the supplied ids to confirm they are present in the document before rendering.
3
renderImages
Render the requested nodes to temporary image URLs in the requested format and scale.

Source API Descriptions

Arazzo Workflow Specification

Raw ↑
arazzo: 1.0.1
info:
  title: Figma Render File Node Images
  summary: Open a file, drill into specific nodes, and render them to image URLs.
  description: >-
    The canonical Figma design-to-asset flow. The workflow first retrieves the
    document tree for a file, then fetches the specific nodes the caller is
    interested in to confirm they exist, and finally renders those nodes to
    temporary image URLs in the requested format and scale. 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: filesApi
  url: ../openapi/figma-files-api-openapi.yml
  type: openapi
workflows:
- workflowId: render-file-node-images
  summary: Render selected nodes of a Figma file to downloadable image URLs.
  description: >-
    Retrieves the file document, validates the requested nodes, and renders
    them to image URLs that remain available for fourteen days.
  inputs:
    type: object
    required:
    - fileKey
    - ids
    properties:
      fileKey:
        type: string
        description: The key of the Figma file (from figma.com/file/{file_key}/...).
      ids:
        type: string
        description: Comma-separated list of node IDs to render.
      format:
        type: string
        description: Image output format (jpg, png, svg, or pdf).
      scale:
        type: number
        description: Image scaling factor between 0.01 and 4.
  steps:
  - stepId: getFile
    description: >-
      Retrieve the document tree for the file to confirm it exists and is
      accessible before drilling into specific nodes.
    operationId: getFile
    parameters:
    - name: file_key
      in: path
      value: $inputs.fileKey
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      fileName: $response.body#/name
      lastModified: $response.body#/lastModified
      version: $response.body#/version
  - stepId: getNodes
    description: >-
      Fetch the specific nodes referenced by the supplied ids to confirm they
      are present in the document before rendering.
    operationId: getFileNodes
    parameters:
    - name: file_key
      in: path
      value: $inputs.fileKey
    - name: ids
      in: query
      value: $inputs.ids
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      nodes: $response.body#/nodes
  - stepId: renderImages
    description: >-
      Render the requested nodes to temporary image URLs in the requested
      format and scale.
    operationId: getImages
    parameters:
    - name: file_key
      in: path
      value: $inputs.fileKey
    - name: ids
      in: query
      value: $inputs.ids
    - name: format
      in: query
      value: $inputs.format
    - name: scale
      in: query
      value: $inputs.scale
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      images: $response.body#/images
      err: $response.body#/err
  outputs:
    fileName: $steps.getFile.outputs.fileName
    images: $steps.renderImages.outputs.images

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-render-file-node-images-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.