Connect Figma to WPOS using a personal access token. Read frames and components, scope the design, and build a WordPress page from your source file.
A design handoff needs more than a screenshot. The Figma integration lets WPOS inspect accessible file data and components so the selected design can inform the WordPress page being built. Start with a specific frame and a clear destination page to keep the implementation focused.
A Figma account. Free works for personal files. Team files require the appropriate seat. View access to any file you want WPOS to read. The file key for each design, the segment after /file/ in the file URL.
Choose Figma in Settings → Connectors. Generate a personal access token in Figma under Settings → Security, set its expiry and the required read scopes, then paste it into the Figma connection panel in WPOS.
Use this Figma frame as the source for a new WordPress page. Read its structure and assets, then build and check the page against the selected frame.
Compare the resulting page with the selected frame at desktop and mobile widths. Check text, images, spacing and links, and confirm that the connected Figma account can access the actual source file.
Use the connected account for a specific task, with the permissions and plan available to you.
Provide a specific Figma frame so the agent has a bounded design to implement on the site.
Read accessible components and file structure to understand the design’s reusable elements.
Use source-file information alongside the brief instead of relying solely on a flattened screenshot.
Return to the relevant frame when refining the WordPress implementation, then verify the published layout.
Connection requirements, workflow limits and troubleshooting from the WPOS documentation.
Connect Figma to WPOS using a personal access token. Read frames and components, scope the design, and build a WordPress page from your source file.
Choose Figma in Settings → Connectors. Generate a personal access token in Figma under Settings → Security, set its expiry and the required read scopes, then paste it into the Figma connection panel in WPOS.
The token only grants the access held by its Figma account. Large files can return too much data, so specify a frame or page. Token expiry or revocation requires a new connection credential.
Most often the token reached the expiry date set when it was generated, and nothing warns you beforehand. It can also mean the token was revoked. Generate a new token and reconnect.
The token belongs to an account without access to that file, or the file key is wrong. Confirm the connected account can open it, and re-copy the key from the URL.
Treat it as compromised. Delete it in Settings, then Security, then Personal access tokens, generate a replacement, and reconnect. Deleting it in Figma is the only thing that actually revokes it.
Connect your account and give WPOS a specific WordPress task. Start free with 5,000 credits, one live site and a staging sandbox.
Start free