How to Build a Figma File for Jurni
Last updated: August 25, 2026
Last updated: August 2026
Overview
This guide shows you how to prepare a Figma file so Jurni can turn it into an agentic shopping journey with the fewest revisions. Figma gives the engine your content and structure. Jurni layers in your brand system, product data, animations, and conversion intelligence on top of it.
Follow the steps in order. Most import issues come from work skipped before the file reaches Jurni.
Prerequisites
A Figma account with access to the file
Admin access to your Jurni workspace settings
Final copy, approved imagery, and confirmed product and offer details
Your Shopify catalog connected, if the journey includes a product section
1. Connect your Figma account
Go to Settings> Integrations in Jurni.
Open the Figma connection and authorize with OAuth.
Confirm the connection shows as active.
Files do not need to be public. Once authorized, Jurni can read private files in your Figma account.
Tip: If a file imports incorrectly, check the connection status before you start debugging the design.
2. Configure your brand settings first
Set your brand system in Jurni before importing Figma Configure:
Fonts, including the correct font variants
Colors
Border radius
Button typography and defaults
Each experience is created as an independent copy of your shop-level brand settings. Changing brand settings later does not update experiences that already exist, so getting this right first saves rework.
After an experience is created, review its own theme, especially typography. Use brand tokens for text wherever possible and reserve custom fonts for cases that genuinely need them.
3. Prepare your Figma file
The import reads your page structure from the way the file is organized. It works best with Figma sections, frames, and a clean layer hierarchy. Your file does not need to be perfectly grouped for the import to run, but a well organized file produces a more accurate result.
Before you import:
Include both a mobile and a desktop version in the same file, side by side. This is required for the import to build responsive layouts correctly.
Build the experience out fully in Figma. The import recreates what is in the file, so anything left unfinished will need to be completed in Jurni afterward.
Name your frames clearly so the intended pages and breakpoints are easy to identify.
Have your content final before you build:
Approved image and asset bank at full quality
Final, proofread copy
Correct product, variant, and offer details
Any required legal or compliance content
A defined footer or other shared sections
Off-brand output is usually a content problem rather than a design problem.
4. Import into Jurni
Open the Agent> click +> Figma
Copy the Figma link and paste it into Jurni.
Prompt the Agent to build out the Figma file pixel perfect. Add any supporting images, screenshots, or files alongside the link if the design references assets that are not in the file.
5. Review both breakpoints after import
Jurni treats desktop and mobile as distinct experiences. Edits made in desktop mode apply to desktop only, so review mobile separately rather than assuming changes carry across.
Start with mobile, then move to standard desktop
Check wide screens at 1440px and above for max widths, typography, and layout consistency
6. What the import brings across
Jurni performs best when Figma provides a strong foundation, followed by review and iteration in the editor. Plan a short QA and prompting pass after import, especially for:
Area | What to check |
|---|---|
Typography | Font substitutions and incorrect font sizes |
Layering | Overlays, and image to text alignment |
Responsiveness | Behavior between breakpoints and on wide screens |
Graphics | Vector rendering |
Interactivity | Sections built around movement or custom behavior |
7. Parallax and animations
Parallax effects and other animations are not imported from Figma. The import brings in your content and structure only. Animations are added in Jurni after the file is imported.
There is no special way to lay out a Figma file for parallax. Two things to keep in mind:
Every element that will carry a parallax effect needs to exist in the Figma file as content.
The effect itself, and any further animation edits, are applied in Jurni once the import is complete.
For bespoke interactive components, flag them at the start of the project. Some need additional prompting or custom code. Keep a simpler fallback ready, such as an accordion, so your launch date does not depend on a single effect.
8. Design with reusable Jurni sections in mind
Build your first one or two pages carefully to the standard you want.
Save approved sections for reuse.
Turn that work into one or two reusable templates instead of starting each page from scratch.
Choose the right section type:
Saved sections: use when each page needs its own editable instance
Global sections: use when one edit should apply everywhere
For product sections and buy boxes, start from an existing saved product section and expose the product selector. This keeps price, discount, and images dynamic from Shopify rather than static in the design.
9. QA checklist before publishing
Save your work before previewing. Preview renders the last saved version.
Brand fonts, colors, border radius, and button styles match your brand system
Mobile, standard desktop, and wide desktop all reviewed
Every button, link, and scroll-to-section target works
Product, price, variants, discounts, and selling plans pull correctly
Animations and parallax effects applied and tested in Jurni
Image quality holds at full width
Copy is final and accurate
Footer and global sections are included
Recommended workflow
Configure Jurni brand settings.
Finalize Figma desktop and mobile frames, side by side and fully built out.
Import using the Figma link, plus any supporting assets.
Build and QA one page to the required standard, including animations.
Save approved repeated elements as global sections.
Convert that work into one or two reusable templates.
Troubleshooting
Issue | Likely cause | Fix |
|---|---|---|
File will not import | Figma connection inactive or expired | Reauthorize Figma in Settings |
Fonts look wrong | Brand fonts or font variants not configured | Set fonts in brand settings, then reapply brand tokens in the journey theme |
Mobile layout is broken | No mobile version in the file, or only the desktop frame was linked | Add a mobile version alongside the desktop one and reimport |
Sections are missing | The design was not finished in Figma before import | Complete the missing sections directly in Jurni |
Animations did not carry over | Expected behavior | Apply parallax and animation effects in Jurni after import |
Brand updates are not showing | The journey was created before the change | Update the theme on that journey directly |
Price or images are static | Product selector not exposed | Rebuild the section from a saved product section with the selector enabled |
Preview looks outdated | Unsaved changes | Save, then preview again |
Related articles
Configuring your brand settings in Jurni
Saved sections vs global sections
Connecting Shopify to Jurni
Adding animations and parallax effects
Publishing and QA checklist for agentic shopping journeys
Still stuck? Contact the Jurni support team with your file link and journey name, and we will take a look.