FISYCO reads your design files through a Figma account you connect. That account opens the files your libraries point at and receives a webhook each time you publish. This page covers who can connect an account, how to point a library at a file, and what FISYCO reads.
Before you start
- To connect an account for the whole workspace, you're a workspace owner or admin. To connect one for a single project, you're a maintainer of that project.
- The Figma account can open the files you want to sync.
- The file is published as a team library, if you want its components or styles. The reason is explained below.
Connect a Figma account
A project can't be created without a Figma account, so the first connection usually happens there.
- Click Create project. At the Figma step, click Connect Figma.
- Figma asks you to allow access. Approve it, and you return to FISYCO.
- If the workspace already has an account, choose it under Which Figma account should this project read? or click Connect another account.
Choosing an existing account doesn't re-authorize anything. Projects share one connection per account, so the others keep working.
To give a single project its own account, open the project, then Settings → Integrations, and click Connect with Figma. That connection starts limited to the project.
Figma keeps one grant per account for FISYCO. Authorizing the same Figma account in another workspace ends the earlier grant, and the libraries there pause until someone reconnects. Pick the existing account instead of connecting it twice.
Where connections live
Open the account menu, then Workspace settings → Connections. Each Figma account has one row: whose account it is, its status, who connected it, when it was last checked, and which projects read through it. Owners and admins can add an account for the whole workspace with Reconnect at the top of the page.
Two settings decide who can use a connection:
A new connection is a personal account. Only the person who connected it can browse files through it while setting up a library. A service account can be browsed by everyone in its scope, so use a dedicated Figma account for it.
Revoke deletes the stored tokens and pauses the connection's libraries until a project picks another account. Owners, admins and the person who connected it can revoke. Figma has no API to withdraw the grant itself. Connecting the same account again restores access and resumes the paused libraries.
Point a library at a file
A library reads one Figma file. Project maintainers and workspace owners or admins can create one.
- In the project, click Add library, choose the type and click Continue.
- Enter a Name and paste the file's link into Figma file. The file key works too.
- Choose what the library reads. Icons and illustrations ask for Pages and sections: ticking a page selects all of its sections. A tokens library asks for style groups and variable groups instead.
- Finish the remaining steps and click Create library.
FISYCO then subscribes to the file's publish events and runs the first sync straight away. Components libraries are set up from the design system; see Components library.
What FISYCO reads
When you connect, FISYCO asks Figma for read access to file content, versions, library content and your profile, plus permission to manage webhooks. It doesn't ask for permission to edit your files.
Publish the file as a library
The Figma REST API returns components and styles only after they are published as a team library. Until then, FISYCO has nothing to read. A components library on an unpublished file shows This Figma library is not published at the source step. Publish the library in Figma (Assets → Publish) and open the step again.
Publishing is also the signal for automatic syncs. Saving the file isn't enough: Figma's version history includes autosaves, so FISYCO follows publishes instead.
Webhooks after publishing
Each publish sends FISYCO a webhook, and every library on that file syncs on its own. One subscription per account and file serves all projects that use it.
The subscription is listed under Registered webhooks in the project's Settings → Integrations, as Healthy, Broken or Not checked yet. FISYCO asks Figma about it every five minutes. If it stops working, FISYCO checks the file's latest publish every 30 seconds until the webhook is repaired.
Once a library has synced, its changes reach your code as pull requests from the repository you connect in Connect a repository.