Integration
Connect Figma to Polaris
A Figma token belongs to a person, and Polaris shows you which person it verified, which is the detail worth checking before you store it.
What connecting buys
Connecting Figma gives a Polaris worker access to design files and comments through a personal access token. Polaris verifies the token against Figma before storing it and displays the account email Figma returned. Because the token carries one person's access, the account you create it on decides the boundary, and the connection is authorized once for the whole organisation.
- Credential
- Personal access token
- Verified live
- Figma returns the account email
- Boundary
- The token owner's file access
Design work that is not designing
The reason to connect Figma is rarely to have an AI push pixels. It is the surrounding work: the review notes nobody wrote up, the handoff spec that lags the file by three days, the component that got renamed in one place and not in the other, the comment thread with four open questions in it.
That work is text about a design, and it is the kind of task that sits in a backlog for a month because it belongs to whoever has the least going on that week.
What the connection gives a worker
Bounded by what the token's owner can open in Figma. Nothing broader.
Design files
The file is the source of truth for a handoff note or a review summary, and reading it beats working from a screenshot somebody pasted in a channel.
Comments
Comment threads are where design decisions actually get made and where they reliably get lost. A worker that can read them can turn them into tracked tasks.
A basis for consistency checks
Auditing whether a set of files still follows the same conventions is tedious for a person and unbothered work for a machine.
Handoff context
A design review or an asset handoff written from the file rather than from memory is the difference between a spec engineers trust and one they re-ask about.
Connecting Figma
- 1
Create a personal access token
From Figma's settings. The value starts with figd_ and is shown once, so paste it straight into Polaris.
- 2
Pick the account deliberately
The token inherits that account's file access. If your team has a limited account for tooling, use it rather than the design lead's login.
- 3
Authorize as an owner or admin
Polaris calls Figma with the token, refuses it if Figma does, and shows you the account email it verified before storing anything.
Workers and work this connection feeds
Twenty minutes of every design review goes on finding the file
The agenda written the day before, with last review's unresolved threads at the top.
Is this final? Asked for the fourth time this month
A completeness check before build starts, so the question is answered before it is asked.
The component was renamed and the documentation was not
A weekly drift report between the component library and the documentation that describes it.
Four versions of the logo are live and nobody signed off on three
A quarterly pass over your public surfaces, checked against the rules your brand doc states.
Hire an AI technical writer
The documentation debt on your team is not a writing problem, it is a nobody-has-two-free-hours problem, and this is the worker for those two hours.
Hire an AI project coordinator
The unglamorous half of running projects, done every week without anyone having to be the person who nags.
Questions people ask
+Can an AI worker edit my Figma files?
Treat this connection as access to read design files and comments. The work it feeds is written output such as review notes, handoff specs and consistency audits, delivered as comments and docs in Polaris for a person to close.
+Which Figma files does the connection cover?
Whatever the token's owner can open. Figma personal access tokens carry that person's access, so choosing the account is choosing the scope. Polaris shows you the account email it verified so the choice is visible rather than assumed.
+How is the Figma token stored?
Server-side, one row per organisation, written only after Figma accepted it. The browser never reads it back, and revoking deletes it for every worker carrying the connection at once.
+What happens when the token expires or is rotated?
Figma starts rejecting it and the worker loses access. Paste a replacement into the same connect panel and it overwrites the stored value after the same live check. There is no need to touch individual workers.
Related
Every tool a Polaris worker can be given
One catalog, one credential per tool per organisation, authorized by an owner and used by every worker who carries it.
Twenty minutes of every design review goes on finding the file
The agenda written the day before, with last review's unresolved threads at the top.
Is this final? Asked for the fourth time this month
A completeness check before build starts, so the question is answered before it is asked.
Design work an AI teammate can take, and the part it cannot
Five jobs around the work, none of them the work itself. Taste stays where it belongs.
Hire an AI project coordinator
The unglamorous half of running projects, done every week without anyone having to be the person who nags.
Connect Slack to Polaris
Six scopes, no access to direct messages, and a bot that only reads the channels somebody invited it into.