# Figma integrations: files, comments and projects

> Start a Tray.ai workflow when Figma sends “File updated”. Connect Figma to the rest of your design and creative stack with Tray.ai.

**Canonical page:** https://tray.ai/connectors/figma-integrations/
**Categories:** Design and creative
**Connects through:** HTTP Connector

## Overview

Figma is a collaborative design tool where teams create interfaces, prototypes, and design systems together in the browser, with comments and version history built in. Tray.ai connects to Figma through the HTTP Connector, so your workflows can call the Figma API alongside the rest of your stack.

## Use cases

### Files

Read files in Figma from any Tray.ai workflow. The Figma API covers calls such as get a file and render file images.

- Get a file
- Render file images
- List file versions

### Comments

Read, create, and delete comments in Figma from any Tray.ai workflow. The Figma API covers calls such as list comments and post a comment.

- List comments
- Post a comment
- Delete a comment

### Projects

Read projects in Figma from any Tray.ai workflow. The Figma API covers calls such as list team projects and list project files.

- List team projects
- List project files

### Webhooks

Read and create webhooks in Figma from any Tray.ai workflow. The Figma API covers calls such as list webhooks and create a webhook.

- List webhooks
- Create a webhook
- List webhook requests

### Figma events

Start a Tray.ai workflow the moment something happens in Figma. Figma sends events such as file updated and file deleted to a Tray.ai webhook trigger.

- File updated
- File deleted
- File version updated

## Challenges Tray.ai solves

### Keeping Figma credentials out of logs

A raw API call usually means pasting a key or token into the request, where it ends up in step inputs, logs, and screenshots.

**How Tray.ai helps:** Store Figma credentials once as a Tray.ai authentication and reference them from the HTTP Connector. Tray.ai masks authentication values in logs, so the secret never shows up in a step's input or output.

### Going from the Figma API docs to a working call

Translating an example request from API docs into a workflow step means copying the method, URL, headers, and body by hand.

**How Tray.ai helps:** Paste a cURL example from the Figma API docs into the HTTP Connector and Tray.ai fills in the method, URL, headers, and body for you.

### Handling files and non-JSON responses

Not every API answers in JSON. Some return XML, files, or binary data, or expect a multipart upload.

**How Tray.ai helps:** The HTTP Connector parses JSON and XML responses, returns files you can pass to the next step, and sends multipart form data for uploads.

## Frequently asked questions

### Does Tray.ai connect to Figma?

Yes. Tray.ai connects to Figma through the HTTP Connector, which calls the Figma API directly. Any call the Figma API documents can run as a step in a Tray.ai workflow.

### How does Tray.ai authenticate with Figma?

The Figma API uses a bearer token and OAuth 2.0. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated Figma connector?

Figma runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated Figma connector from the Figma API.

## Learn more

- Intelligent Integration: https://tray.ai/platform/intelligent-ipaas/
- Merlin Agent Builder: https://tray.ai/platform/merlin-agent-builder/
- Agent Gateway for MCP: https://tray.ai/platform/agent-gateway/
- Book a demo: https://tray.ai/contact/