Connect Figma to Crush
Give Crush governed access to Figma’s 47 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Figma to Crush in four steps
Admins approve the server once. Everyone in Crush then gets it through the same governed connection.
- 1
Approve Figma in Runlayer
Add Figma from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect Crush to Runlayer
Users add the Runlayer Plugin to Crush by following Runlayer’s setup guide. Crush reaches Figma’s 47 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
Crush setup guide - 3
Sign in to Figma
Each user signs in to Figma with OAuth. Runlayer keeps the tokens out of the client’s configuration.
- 4
Use Figma from Crush
Figma’s approved tools appear in Crush. Every call is checked against policy and recorded.
Tools
47 Figma tools in Crush
Runlayer policy decides which of these Crush users can call. 23 read data only and 5 can change or delete data.
Add code connect mapping
Map a Figma node to a code component in your codebase using Code Connect.
Create generative plugin
Creates a new generative plugin in the authenticated user's account library and returns its id.
Create new file
Create a new blank Figma file.
Create shader
Set kind to effect for a shader that transforms the layer beneath it, or fill for a shader that generates its own pixels.
Download assets
Download assets from a Figma file for a single node: an exported render, the original source images, and SVGs of the vector layers.
Export video
Export a Figma timeline node as an MP4 video.
Generate diagram
Create a flowchart, decision tree, gantt chart, sequence diagram, state diagram, or entity relationship diagram in FigJam, using Mermaid.js.
Generate Figma design
Capture a live web page by URL into an existing Figma design file.
Control
What Runlayer can see and stop in Crush
Some controls apply to every client at the gateway. Others depend on what Crush exposes to Runlayer.
Gateway policy (available)
Every Figma call from Crush passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Crush as the client, the tool, and the policy and scanner decisions.
Native enforcement adapter (not available)
Runlayer has no device-side adapter for Crush yet, so control happens at the gateway.
Frequently asked questions
Connect more