Question 1

Can Ana read Figma file contents?

Accepted Answer

Ana can access file metadata, version history, components, styles, and comments via the Figma REST API. The full rendered design tree is also available but is usually summarized by Ana rather than returned raw, since the tree can be very large for complex files.

Question 2

Does Ana support Figma dev mode data?

Accepted Answer

Yes. Dev mode assets, status annotations, and design tokens are all accessible through the Figma API, and the TextQL connector surfaces them so Ana can join design readiness signals with warehouse release data in a single question.

Question 3

How are Figma tokens secured?

Accepted Answer

OAuth tokens and personal access tokens are encrypted at rest in TextQL's credential vault and injected at the network layer by our egress proxy. Ana's Python sandbox never sees the raw token value, and refresh cycles happen transparently outside the sandbox.

Question 4

Which Figma plans work with this connector?

Accepted Answer

Any Figma plan that includes API access works, which is all paid plans (Professional, Organization, Enterprise). Free plan users can connect with a personal access token but may encounter rate limits for heavy usage.

Question 5

Can Ana post Figma comments?

Accepted Answer

Yes with write scopes. By default the connector is read-only. Admins can grant write scopes during OAuth setup to let Ana post comments on files, which is useful for workflows where Ana needs to flag design issues automatically.