<- all tokdocs
2026.09.29@radnolan

Figma Weave's Figma Node Syncs One Way Automatically, and the Video Names the Wrong Direction

AI
Watch on TikTok

View on TikTok ->

A 54-second screen recording that rebuilds a seasonal coffee campaign by pasting Figma frames into Figma Weave as Figma nodes, wiring one generated image into every frame at once, then swapping a headline word through a text input. The workflow is real and the demo is accurate up to one sentence. The narration says "any changes you make in Figma will update on Weave." Figma's own Weave documentation says the opposite about which direction is automatic: changes made in Weave push to the Figma file automatically, while changes made in Figma do not sync automatically and require pressing Update on the Figma node to pull them in. That is a meaningful difference if you plan to keep designing in Figma and expect Weave to follow along.

What the recording actually shows

The starting file is a Figma Design page holding a "Seasonal Campaign" section and a "Social" section for a fictional coffee brand called EMBER. Every frame carries the headline "A little sweeter," the product line "Maple Latte," the eyebrow text "AUTUMN, SIPPED SLOWLY," and a summer beach image of an ice-cream-topped mug. A "Try it now" button sits at the bottom of most layouts.

Those frames get copied and pasted onto the Weave canvas, where each becomes a Figma node carrying its original name: "Campaign / Social," "Campaign / Story," "Campaign / Web Hero," "Campaign / Announcement Square," "Campaign / Cafe Poster," "Campaign / Counter Card," "Campaign / Table Card," "Campaign / Loyalty Offer," "Campaign / Takeaway Insert," "Campaign / Digital Billboard," and a dozen more. The canvas zoom indicator reads 18 percent when the full set is in frame, which gives a sense of the scale being demonstrated. Each node carries an "Add input" control on its lower left and an "Edit" control on its lower right.

An image node labeled "ChatGPT Image 1.0 Edit" sits to the left with a "Run Model" button, generating an autumn version of the mug shot. Its output handle fans out in a spray of connection lines to every Figma node on the canvas at once. Later a Text node containing the word "pumpkiny" fans out the same way in purple. A credit counter in the upper right reads 38.9K.

The shift-drag fan-out is the actual trick

The moment worth stealing from this video is not the Figma node itself. It is the gesture used to attach one output to twenty inputs: grab the image handle, hold Shift, and drag across all the target nodes. One pass wires the whole campaign.

The narration is honest that this leaves work behind. Drawing the connection is not the same as telling each frame which layer to replace, and the video says so: "you've just sent the image to all the nodes, but now you have to link them." Clicking the chain icon opens a small popover titled "Connect to" listing the named layers inside that frame. In the recording it offers a single entry, "HERO IMAGE."

That popover is the quiet requirement underneath the whole workflow. Your Figma layers need real names. A file full of "Rectangle 47" and "Frame 12" produces a "Connect to" list you cannot navigate, and the cost of fixing that lands before you ever open Weave. Figma's documentation describes the same step as connecting an input to a layer inside the frame, added either through "Add Input" on the node or the plus beside Inputs in the side panel, with Text and Image as the input types.

The sync direction, corrected

Here is the claim the video gets backwards. Figma's Weave documentation for the Figma node states that once an input is connected, changes you make in Weave push automatically to the Figma file, and that changes made directly in Figma do not sync automatically. If you edit the design or move a layer in Figma, you press Update on the Figma node in Weave to pull those changes in.

The video's description calls this "a two-way workflow," which is fair as a description of the round trip. The narration then attaches the automatic behavior to the wrong leg of it. Weave to Figma is the automatic direction. Figma to Weave is the manual one.

The practical consequence is small but real. If a designer renames or repositions a layer in the source file while you are iterating in Weave, your Weave canvas is looking at a stale copy until somebody presses Update. Build that press into your process rather than assuming the canvas is live.

Text as a variable is the part that scales

The last third of the recording is the piece that turns a demo into a system. Right-clicking a text layer adds a text input to the node. Connecting a Text node to that input swaps "sweeter" for "pumpkiny" across the campaign. Then the same text gets wired into the image node's prompt as a variable, so the word driving the headline also drives the generated artwork, and changing it to "spicy" moves both at once.

Later frames show the result carried through a second time with a different seasonal word entirely, where the headline reads "A little gingerbread" and the imagery has shifted to gingerbread and spices. One string now controls copy and image across roughly twenty layouts.

The versioning advice in the closing line is the sensible half of this. Duplicate the frames in Figma before the next run so the old variants survive as flat artifacts. Weave holds the workflow, Figma holds the output history.

What this costs and what it assumes

Weave runs on credits, and the recording shows a balance of 38.9K in the corner. Figma's Weave FAQ states that Figma Weave AI credits and Figma AI credits are separate pools, and that actions in Figma Weave consume Weave credits independently. The Weave tools that appear inside Figma Design are free during the beta and do not consume AI credits, which is a different thing from the standalone platform. On pricing the FAQ is direct: "We haven't made any pricing changes yet. We're still learning from users and figuring out how Figma Weave fits best within Figma's plans." Any credit tier numbers you find on third-party pricing blogs are not coming from that page.

Two access requirements sit underneath the demo. The full Weave platform runs at weave.figma.com on a free account using your Figma login, while the Weave tools inside Figma Design require a paid plan. Creating a Figma node also requires edit access to the source file and a linked Figma account under Settings, Profile, Linked accounts.

One timing note on the framing. The video calls this "the new Figma Node," and the node became available to everyone on September 17, 2026. This clip posted September 29. It is a walkthrough of a shipped feature rather than a launch announcement, which is the more useful thing for it to be.

Key Takeaways

  • The narration reverses the sync direction. Weave changes push to Figma automatically. Figma changes require pressing Update on the Figma node to pull them into Weave.
  • Create a Figma node by copying a frame in Figma Design and pasting it onto the Weave canvas. You need edit access to the file and a linked Figma account.
  • Shift-dragging one output handle across many Figma nodes wires the whole set in one pass, which is the highest-leverage gesture in the video.
  • Connecting is a separate step from wiring. The chain icon opens a "Connect to" list of named layers, so your Figma layer names determine whether this is usable at scale.
  • Inputs come in two types, Text and Image, added via "Add Input" on the node or the plus beside Inputs in the side panel.
  • Wiring one Text node into both a headline layer and an image node's prompt lets a single word drive copy and artwork across every layout at once.
  • Duplicate frames in Figma before each new run. Weave holds the workflow, Figma holds the version history.
  • Weave credits are a separate pool from Figma AI credits, and Figma states it has not made pricing changes yet, so treat third-party credit tier figures as unverified.
  • The Figma node shipped to everyone on September 17, 2026. This video posted September 29, 2026.

Resources

Published September 29, 2026. Writeup generated from a favorited TikTok.