Skip to content
For LLMsView as Markdown·

Figma

undefined

DetailValue
CategoryDesign
Base URLhttps://api.figma.com/v1
AuthenticationAPI Key
Endpoints7
Connector keyfigma

Using Figma in a workflow

  1. Go to Connections and click New Connection.
  2. Pick Figma from the marketplace.
  3. Enter your credentials (see Authentication above for what's expected).
  4. In a workflow, drop an API Call node and select this connection.
  5. Pick the operation you need from the Operation dropdown — the full list is below.

Available endpoints

EndpointSummary
GET Get File
GET Get File Nodes
GET Render Images
GET List Comments
GET List Components
GET List Styles
GET List Team Projects

Each endpoint is documented in full below. Use the outline on the right to jump to one.

GET

Get File

DetailValue
Operation IDget_file_0
MethodGET
Path``

Parameters

No parameters.

Using this endpoint in a workflow

  1. Add an API Call node to your workflow.
  2. Pick your Figma connection from the Connection dropdown.
  3. In the Operation dropdown, select get_file_0.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Figma API reference.

GET

Get File Nodes

DetailValue
Operation IDget_file_nodes_1
MethodGET
Path``

Parameters

No parameters.

Using this endpoint in a workflow

  1. Add an API Call node to your workflow.
  2. Pick your Figma connection from the Connection dropdown.
  3. In the Operation dropdown, select get_file_nodes_1.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Figma API reference.

GET

Render Images

DetailValue
Operation IDrender_images_2
MethodGET
Path``

Parameters

No parameters.

Using this endpoint in a workflow

  1. Add an API Call node to your workflow.
  2. Pick your Figma connection from the Connection dropdown.
  3. In the Operation dropdown, select render_images_2.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Figma API reference.

GET

List Comments

DetailValue
Operation IDlist_comments_3
MethodGET
Path``

Parameters

No parameters.

Using this endpoint in a workflow

  1. Add an API Call node to your workflow.
  2. Pick your Figma connection from the Connection dropdown.
  3. In the Operation dropdown, select list_comments_3.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Figma API reference.

GET

List Components

DetailValue
Operation IDlist_components_4
MethodGET
Path``

Parameters

No parameters.

Using this endpoint in a workflow

  1. Add an API Call node to your workflow.
  2. Pick your Figma connection from the Connection dropdown.
  3. In the Operation dropdown, select list_components_4.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Figma API reference.

GET

List Styles

DetailValue
Operation IDlist_styles_5
MethodGET
Path``

Parameters

No parameters.

Using this endpoint in a workflow

  1. Add an API Call node to your workflow.
  2. Pick your Figma connection from the Connection dropdown.
  3. In the Operation dropdown, select list_styles_5.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Figma API reference.

GET

List Team Projects

DetailValue
Operation IDlist_team_projects_6
MethodGET
Path``

Parameters

No parameters.

Using this endpoint in a workflow

  1. Add an API Call node to your workflow.
  2. Pick your Figma connection from the Connection dropdown.
  3. In the Operation dropdown, select list_team_projects_6.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Figma API reference.