Figma node — connect frames into Weave workflows
Turn the design frame into a workflow node, connect text, images and styles, and branch into multiple results. Ports and connections are the core visual language.
View HTML source
<!doctype html><html lang="zh-CN"><meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1"><title>Figma node — connect frames into Weave workflows · sequence</title><style>html,body{margin:0;width:100%;height:100%;overflow:hidden;background:#171819}canvas{display:block;width:100%;height:100%;object-fit:contain}</style><body data-mode="sequence"><canvas width="1000" height="600"></canvas><script src="data.js"></script><script src="common.js"></script><script src="scene.js"></script><script src="bridge.js"></script></body></html>Motion and composition
Local motion · Composition rules
Establish the design source before turning it into a node

Move from the use case into copying the design, then transition the familiar frame onto the node canvas. Retain its thumbnail or name in the source node so viewers do not mistake it for another asset.
Make input and output directions clear
Send images, text and styles into their corresponding ports; the central design node receives the inputs and branches results out the other side. Reveal lines as connections are made, anchor their endpoints to ports, and keep them stable after connection.
Every line explains a data relationship
Match input-node names to destination slots, and use multiple output branches to show different applications of the same design. Avoid adding random connections to make the workflow look complex; give each new parameter its own label and clear position first.
| Area | Arrangement |
|---|---|
| Input | Arrange by parameter type |
| Design node | Preserve the source design's identity |
| Output | Branches correspond to different deliverables |
| Co-branded closing frame | Use simple connections to reflect workflow relationships |
Keep nodes lightweight on a dark canvas
Establish hierarchy through a dark-gray background, light text, a pale-purple main node and teal secondary accents. Use sans-serif node labels and avoid undersized port text; connections should be quieter than nodes, with selected states brighter than ordinary relationships.
Define interfaces before changing the workflow
The design tool and automation platform can change. List the available input fields and output deliverables first, then replace node names, thumbnails and brands; every connection needs a clear responsibility at its source and purpose at its destination.
Sections and rhythm
Click a section to seek to it in the choreography example above.






Visual references · Discrete still frames
Creating other themes
- Replace the design and workflow tools while preserving source → parameters → multiple outputs.
Production constraints
Source design frame / Node container / Input port / Text node / Image node / Output branches
- Turn a design frame into a connectable node, connect text and images to their respective slots, then branch the output into different use cases.
- Connections must land on the correct ports rather than linking randomly as decoration.