A Figma file is two things at once: the design, and the argument about the design. The second one lives in comments, in frame names, and in the pages labelled "explorations" that nobody outside the team ever opens. Six months later, the question is not what the screen looks like — it is why it stopped looking like the other version. The Figma connector is part of askFinz Knowledge, which is still rolling out; here is what it will do, and what it will not.
Find the file by describing the screen
Search for "the checkout step with the saved-card toggle" rather than guessing which project it was filed under.
Recover why a design changed
Comment threads are where the trade-off was made and where a stakeholder's objection was resolved. Connected, those answer questions directly, with the file and frame named.
Keep design decisions searchable next to the spec
The design lives in Figma and the requirement lives in a ticket or a doc. Asking one question across all three is the point; the answer cites each source so you can open it.
What is read, and what is never edited
What crosses, and what stays in Figma
Read
file, page and frame names, text layers, descriptions and comment threads from the projects you select.
Written back
nonenothing. No comments posted, no files edited, no versions created.
Stored
a searchable copy of that text, plus a link back to the file and frame.
Never read
projects and drafts you did not select, and other people's personal drafts.
What you will be granting
Read-only access to the team projects you choose, matching what the connecting member can already open in Figma.
Setting it up
Planned — not available yetWhat connecting it will look like once the connector arrives.
- 01
Authorise Figma from Knowledge and choose the team.
- 02
Select the projects to include; personal drafts stay out unless you add them.
- 03
Decide whether to include comment threads — usually yes, that is the reasoning.
- 04
Set the refresh interval.
Limits, honestly
- One-way and read-only. Figma stays the place designs are made.
- What is searchable is text and comments, not the visual design itself.
- Answers reflect the last refresh, not the frame you renamed a minute ago.
- Prototype flows, version history and plugin data are out of scope for now.