A token pipeline replaces the manual chain of "open Figma, export, paste, fix formatting, open a pull request" with steps that run the same way every time.
What a pipeline does
- Run on its own, for example when a Figma library is published.
- Read tokens from the source: Figma Variables and styles, or a token file.
- Compare them with what code already has. Reliable pipelines match by stable ID, so a rename stays a rename.
- Generate the formats code needs: DTCG files, CSS custom properties, SCSS, TypeScript.
- Deliver the change as a pull request that people review and merge.
How common it is
Less than you'd expect. In the zeroheight Design Systems Report 2026, "only 40% of teams have any kind of token pipelines established, which means they are manually syncing their tokens between design, docs and code" (zeroheight, 147 practitioners).
What makes one reliable
The format is the easy part; Style Dictionary and similar tools handle it. The hard parts are identity and review. A pipeline that matches tokens by name turns every rename into a deletion plus an addition, and a pipeline that regenerates everything at once produces diffs nobody can review.