Sanaf AI
Start free
Images & Design

Figma, worked by an AI employee

Not another app for your team to learn, and not a set of rules for you to build. You hire an AI employee, you give it access to your Figma account, and you ask it for things in Slack or Teams the way you would ask anyone else on the team. There is nothing to map and nothing to maintain.

  • Images & Design
  • Signs in to your account
  • 49 ready-made tools
  • Asked in Slack or Teams
At work

An illustration of how the conversation reads, not a transcript from a client account.

What Figma is

A collaborative interface design tool.

You sign in with your own Figma account, the same way you already do. We never see or hold your password.

How a run works

One message in, the work done in Figma.

  1. 01

    You ask

    You message your AI employee in the chat your team already has open, in one sentence, in your own words.

  2. 02

    It works out the step

    It decides what the job needs in Figma. You do not pick anything from a menu or wire anything together.

  3. 03

    It does the work

    Signed in to your own Figma account, inside the access you granted it, doing the thing you asked for.

  4. 04

    It reports back

    It tells you what it did, in the same thread. If it could not do something, it says so rather than guessing.

49 tools it already has

What it can do in Figma

These are the ready-made tools your AI employee already has in Figma. It is not limited to them, but it never has to be taught these.

  • Add a comment to a filePosts a new comment to a figma file or branch, optionally replying to an existing root comment (replies cannot be nested); region height and region width in client meta must be pos
  • Add a reaction to a commentPosts a specified emoji reaction to an existing comment in a figma file or branch, requiring valid file key and comment id.
  • Create a webhookCreates a figma webhook for a team id to send post notifications for an event type to a publicly accessible https endpoint; an initial ping is sent unless status is paused.
  • Create dev resourcesCreates and attaches multiple uniquely-urled development resources to specified figma nodes, up to 10 per node.
  • Create, modify, or delete variablesManages variables, collections, modes, and their values in a figma file via batch create/update/delete operations; use temporary ids to link new related items in one request and en
  • Delete a commentDeletes a specific comment from a figma file or branch, provided the authenticated user is the original author of the comment.
  • Delete a reactionDeletes a specific emoji reaction from a comment in a figma file; the user must have originally created the reaction.
  • Delete a webhookPermanently deletes an existing webhook, identified by its unique webhook id; this operation is irreversible.
  • Delete dev resourceDeletes a development resource (used to link figma design elements to external developer information like code or tasks) from a specified figma file.
  • Design tokens to tailwindConvert design tokens to tailwind css configuration. takes the output from extractdesigntokens and generates: - tailwind.config.ts/js with theme extensions - optional globals.css w
  • Detect backgroundDetect background layers for selected nodes. uses geometric analysis, z-index ordering, and visual properties to identify potential background layers.
  • Discover Figma Resources🔍 smart figma resource discovery - never guess ids again! 🎯 easiest method: just paste any figma url to get all ids: • file urls: https://www.figma.com/file/abc123/design → get f
  • Download Figma ImagesDownload images from figma file nodes. renders specified nodes as images and downloads them using mercury's filedownloadable infrastructure. supports png, svg, jpg, and pdf formats
  • Extract design tokensExtract design tokens from figma files. combines styles, variables, and extracted values to create a comprehensive design token system.
  • Extract Prototype InteractionsExtract prototype interactions and animations from figma files. analyzes the prototype data to extract: - user interactions (clicks, hovers, etc.) - transition animations - compone
  • Get a webhookRetrieves detailed information about a specific webhook by its id, provided the webhook exists and is accessible to the user.
  • Get activity logsRetrieves activity log events from figma, allowing filtering by event types, time range, and pagination.
  • Get comments in a fileRetrieves all comments from an existing figma file, identified by a valid file key, returning details like content, author, position, and reactions, with an option for markdown for
  • Get componentGet component data with automatic simplification. returns clean, ai-friendly component structure.
  • Get component setRetrieves detailed metadata for a specific published figma component set using its unique key.
  • Get current userRetrieves detailed information for the currently authenticated figma user.
  • Get dev resourcesRetrieves development resources (e.g., jira/github links) for a figma main file, optionally filtering by specific node ids.
  • Get file component setsRetrieves all published component sets from the specified figma main file (file key must not be for a branch).
  • Get file componentsRetrieves published components from a figma file, which must be a main file (not a branch) acting as a library.
  • Get file jsonGet figma file data with automatic simplification. this enhanced version automatically transforms verbose figma json into clean, ai-friendly format with: - css-like property names
  • Get file stylesRetrieves a list of published styles (like colors, text attributes, effects, and layout grids) from a specified main figma file (not a branch).
  • Get files in a projectFetches a list of files in a figma project, optionally including branch metadata.
  • Get image fillsRetrieves temporary (14-day expiry) download urls for all image fills in a figma file; requires imageref from paint objects to map urls.
  • Get library analytics component action dataRetrieves component insertion and detachment analytics for a specified figma library, groupable by 'component' or 'team' and filterable by a date range (yyyy-mm-dd).
  • Get library analytics component usage dataRetrieves component usage analytics for a specified figma library file (identified by file key), with data groupable by 'component' or 'file'.
  • Get library analytics style action dataRetrieves style usage analytics (insertions, detachments) for a figma library, grouped by 'style' or 'team'; if providing a date range, ensure end date is not before start date.
  • Get library analytics style usage dataRetrieves style usage analytics for a figma library (specified by a valid file key), allowing data to be grouped by 'file' or 'style'.
  • Get library analytics variable action dataRetrieves weekly, paginated analytics data on variable insertions and detachments for a specified figma library (identified by file key), groupable by 'variable' or 'team', and fil
  • Get library analytics variable usage dataRetrieves paginated analytics data on variable usage from a specified figma library, grouped by 'file' or 'variable', for libraries with enabled analytics.
  • Get local variablesRetrieves all local/remote variables for a figma file/branch; crucial for obtaining mode-specific values which /v1/files/{file key}/variables/published omits.
  • Get paymentsRetrieves a user's payment information for a figma plugin, widget, or community file; the authenticated identity must own the resource.
  • Get projects in a teamRetrieves projects within a specified figma team that are visible to the authenticated user.
  • Get published variablesRetrieves variables published from a specified figma file; this api is available only to full members of enterprise organizations.
  • Get reactions for a commentRetrieves reactions for a specific comment in a figma file.
  • Get styleRetrieves detailed metadata for a specific style in figma using its unique style key.
  • Get team component setsRetrieves a paginated list of published component sets (collections of reusable ui elements) from a specified figma team's library.
  • Get team componentsRetrieves components published in a specific figma team's library; the team must have published components, otherwise an empty list is returned.
  • Get team stylesRetrieves a paginated list of published styles, such as colors or text attributes, from a specified figma team's library.
  • Get team webhooksRetrieves all webhooks registered for a specified figma team.
  • Get versions of a fileRetrieves the version history for a figma file or branch, as specified by its file key.
  • Get webhook requestsRetrieves a history of webhook requests for a specific figma webhook subscription; data is available for requests sent within the last seven days.
  • Render images of file nodesRenders specified nodes from a figma file as images (jpg, pdf, png, svg), returning a map of node ids to image urls (or null for failed nodes); images expire after 30 days and are
  • Update a webhookUpdates an existing figma webhook, identified by webhook id, allowing modification of its event type, endpoint, passcode, status, or description.
  • Update dev resourcesUpdates the name and/or url of one or more existing figma dev resources, each identified by its unique id.
Access, and who is in charge of it

You stay the boss of your Figma account.

Nothing connects until you approve it. You grant access one app at a time, you can take it back the same way, and everything your AI employee does in there is written down where you can see it.

How we handle your data
  • It signs in to your own Figma account. You are not moving anything into ours.
  • You grant access one app at a time, and you can take it back the same way.
  • Everything it does in Figma is written down, with what it did and when.
  • Anything you tell it to check with you first, it checks with you first.
Other apps in the same corner of the business

It works in Figma and the rest of your software in the same job

A real job rarely stays in one place. Reading a message in one app, checking a record in another and writing the result in a third is one request to your AI employee, not three.

See every app

Questions people ask about Figma

Can an AI employee really work inside Figma?
Yes. It signs in to your own Figma account and works in it the way a new hire would, from the chat your team already has open. Nobody installs anything, and nobody learns a new screen.
Do I have to move anything out of Figma?
No. Nothing moves and nothing is replaced. Your records stay in Figma, your team carries on in the same screens they used yesterday, and your AI employee works alongside them in there.
How does it get into my Figma account?
You sign in with your own Figma account, the same way you already do. We never see or hold your password. You approve it before anything connects, and you can take the access back the same way you gave it.
What can it actually do in Figma?
It has 49 ready-made tools in Figma today, among them Add a comment to a file, Add a reaction to a comment and Create a webhook. The full list is on this page. It is not limited to those, but it never has to be taught them.
Can it use Figma and the rest of my software in the same job?
Yes, and that is usually the point. Reading a message in one app, checking a record in Figma and writing the result somewhere else is one request to your AI employee, not three separate ones you stitch together.
Who decides what it is allowed to do in Figma?
You do. You grant access one app at a time and can withdraw it at any time, anything you ask it to check with you first it checks with you first, and everything it does in Figma is written down with what it did and when.