Import from Figma turns one selected Figma frame into a new app artifact. It generates an editable web experience; it does not synchronize later Figma changes back and forth.
Availability and before you start
Choose the destination workspace, which is the access-controlled area that will contain the new artifact. Make sure you can create there. Have a Figma link you are allowed to use and be ready to authorize access when AgentGrid.io asks.
Steps in the app
- Open New → Import from Figma.
- Provide the Figma source and complete the consent or authorization step.
- Choose one frame.
- Select the destination workspace when prompted and start generation.
- Open the new app artifact and review the generated result.
One import selects one frame and creates one app artifact. Supported design content is converted to generated web files; unsupported or unusually complex design behavior may require cleanup after generation.
Free-plan allowance
Free teams receive five successful imports total across both methods. It is one combined allowance, not five of each. Artifact capacity and import allowance are separate. A quota refusal should open or relay the upgrade path, not trigger retries. Deleting an imported artifact does not restore an already consumed import.
See Plans and usage and Limits and quotas.
Errors and recovery
- For an invalid or inaccessible link, verify the source and your Figma access.
- If authorization expires or is denied, complete consent again rather than repeatedly starting generation.
- If no usable frame appears, select a supported frame or simplify the source.
- Review partial generation and fix it in the artifact instead of assuming every Figma behavior maps to the web.
- Do not retry access, artifact-capacity, or import-allowance refusals until a human resolves them.
A connected agent can edit the generated artifact after creation. This page does not claim a separate public CLI Figma-import command.