Forms & Surveys
Audit Figma designs against your design system with Gemini and Slack
When an API call/webhook arrives, it processes form answers with Google Gemini using Data Table, Google Docs, Slack.
What it does
## Audit Figma designs against your design system and track every fix ### How it works Design QA usually happens once, in a meeting, and nobody checks whether the feedback was applied. This template turns it into a loop that runs every time a designer saves a version in Figma (or on demand from a form). 1. Only frames that changed since their last audit are processed (fingerprints in an n8n Data Table). 2. Automated checks read the Figma node tree: WCAG contrast, font size, tap targets, colours and type that are not linked to a style or variable, and copies that look detached from a component. It also measures token coverage. 3. A Gemini AI agent looks at the screenshot, the layer list and the design guide (Google Doc). It reports new visual issues pinned to real layers, can inspect a layer through a tool, and decides which of its earlier findings are fixed. 4. Every finding has a stable id. New ones become Figma comments, still-open ones are not repeated, and fixed ones get a "✅ Fixed" reply in their thread with the number of days it took. 5. Slack gets a summary after each audit and a weekly design-health report. ### Setup steps 1. Create a Figma personal access token (file content read, comments write) and add it as a Header Auth credential named X-Figma-Token on every Figma HTTP node and on the agent tool. 2. Connect Google Docs, Slack (bot token with chat:write, invited to the channel) and a Google Gemini (PaLM) API credential. 3. Fill in Workflow Configuration. The two data tables are created automatically on the first run. 4. Register a Figma webhook (FILE_VERSION_UPDATE) to the production URL of Figma Version Saved with the same passcode, or just use the form. ### Customization Tune thresholds in the configuration, set reviewLanguage for comments in another language, or swap Slack for Gmail or Teams. The workflow timeout (Settings, 20 min) stops a run if the AI model stops responding; frames finished before that keep their results and the rest are picked up next run.
The steps
- Figma Version Saved
- Design Audit Request Form
- Every Monday 9:00
- Parse Figma Event
- Parse Form Request
- Mark Weekly Run
- Workflow Configuration
- Ensure Findings Table
- Ensure Frames Table
- Audit or Weekly Report?
- Is Valid Request?
- Load Design Guide
- Get Figma File
- List Target Frames
45 steps in total.
Similar automations
Code, Git & Developer ToolsComment on Jira Issues When Figma Versions Are Saved3 stepsCode, Git & Developer ToolsComment on Jira Issues When Figma Files Are Versioned4 stepsWeb Scraping & ResearchAudit Google Maps local leads with Apify Local Lead Audit and Google Sheets8 stepsWeb Scraping & ResearchRun a weekly SEO sitemap audit and track changes with Slack and Google Sheets28 steps