Turn Figma design work into journey context

How Figma works with Custory

The Figma integration connects design work to the customer journey it is meant to improve. Instead of keeping screens, prototypes, and design discussion separate from journey insight, Custory lets teams place those assets directly next to the touchpoints, problems, and opportunities they relate to.

That gives designers, PMs, and researchers a clearer shared view of what is being designed, what part of the journey it supports, and how proposed changes connect back to real customer friction.

What teams use it for

Review design in customer context

Teams use Figma in Custory when they want to see screens, flows, and prototypes beside the journey steps they affect, rather than discussing design choices in isolation.

Improve handoff between research and design

Linking files to pain points and touchpoints helps designers understand the problem behind a change and helps researchers show where evidence supports the proposed direction.

Keep the whole flow visible

Instead of focusing on one screen at a time, teams can connect full user flows and prototypes back to the broader journey so design decisions stay grounded in the real experience.

How it works

After connecting Figma, Custory can pull in the files, projects, frames, prototypes, and comments your team wants to reference. Those assets can then be attached to journey steps, touchpoints, or specific pain points so the right design context appears where decisions are being made.

The integration works well for both active product work and longer-term journey maintenance. It helps teams compare intended flows with real customer experience and keep design thinking tied to live journey evidence instead of static review decks.

Core capabilities

Figma covers the core design workflows teams usually need in Custory: importing files and projects, attaching frames or full flows to touchpoints, embedding interactive prototypes, referencing design comments, and keeping design assets visible alongside customer feedback and follow-up work.

Whether you are reviewing onboarding, checkout, activation, or support flows, the integration helps everyone work from the same visual source of truth without losing the operational context around it.

Access and privacy

Custory only reads the Figma files, comments, and project structure your team has chosen to connect. Access follows Figma's existing permission model, which means the integration cannot expand visibility beyond what users already have access to in Figma.

Tokens are stored securely, data is transferred over secure APIs, and access can be revoked at any time from Figma or from Custory's integration settings.