Figma is an amazing collaborative tool that has been around for a while. One of the most interesting feature of Figma is being able to retrieve information of a file using the REST API that Figma provides.
At work, we recently started our transition from Sketch to Figma. As one of the maintainers of the company's design system, I wondered if we could leverage on Figma's API to automate extracting SVGs out from our design file.
Our design system has a collection of icons that are being used throughout our projects. To share icons and assets, our workflow looks like this:
- Extracting the icon(s) from Sketch
- Running the icon(s) through SVGOMG (An SVG optimizer)
- Add the new icon(s) to our assets NPM package
- Do a Pull Request and wait for a review
- After review, merge to master
- Build process that publishes our package
While extracting icons is not difficult, it can get quite mundane and repetitive.
Why not use existing exporting plugins instead?
Our design system has a total of 103 icons, which will continue to grow over time.
Figma API allows you to read Figma files and displays a JSON representation of a file. Within that JSON are layers of the file that are represented by nodes. Each element in Figma is a node, and each node would have properties associated to them.
To use the API, you would need a Personal Access Token that can be generated in
Account > Account Settings > Personal Access Token.
Using Figma in the browser, we can retrieve the
id of an node by clicking on it. This will be displayed in the address bar with the
In this example, selecting the Icons frame gives me
43%3A217 as the node_id, and when decoded using decodedURIComponent gives us
Running the URL through Postman would give us a huge JSON data and we need to decide what to do with that data.
Building the Plugin
The goal was for the plugin to retrieve all nodes and export them out as SVG. To achieve this requires traversing through our JSON to extract out the parts that we want. I also use NodeJS for this to be able to write out SVGs.
This has been cleaned up; the actual data is a lot messier
From the response, we see our icons in the children array. The plugin will loop through this array to extract out two values,
name to be stored in a new array.
With this new array, we loop through it to make a GET request for each icon.
To retrieve the flip flop icon, it would look similar to this request.
This would give us the following response:
And opening that URL gives us our icon.
To get the SVG DOM of the icon, we do yet another GET request:
Which we can then write out as a SVG file using
Plugin in action
There is one limitation which we cannot avoid or bypass. Figma API has a fixed number of request (rate limits) that you can call per minute. The plugin will process 20 requests per 45 seconds to avoid hitting that limit.
What's next for the plugin?
Optimizing the SVGs through an optimizer (SVGO) or being able to detect duplicate names within Figma and dealing with that.