Skip to main content
The Save to Element node turns a run’s images into a reusable Element — at execution time, as part of the flow. Feed it a photo and its generated variations, and it writes them into your library, then emits the saved element so downstream nodes can reference it in the same run. Because it runs with the flow, the capture is repeatable: re-running the agent keeps the element up to date, and published apps can build elements from their users’ uploads automatically.

​
When to use

  • Turn a photo plus generated variations into a reusable character
  • Keep a product’s best generated views together as one element
  • Build elements automatically from app-mode user uploads
Common pattern: upload_image → edit_image → save_to_element → generate_image.

​
Inputs

​
Images
image
required
The images to save. Connect as many as you like — the original photo and any generated variations.

​
Outputs

​
Element
element
The saved element, ready to wire into generation nodes.

​
Configuration

​
Mode
select
default:"Create new"
Create new makes a fresh element from this run’s images. Update existing writes into an element you pick from your library.
​
Name / Subject type / Description
text
Create mode: how the new element appears in your library. Subject type is one of character, product, object, scene, or style.
​
Existing images
select
default:"Keep & append"
Update mode: Keep & append adds this run’s images to the element’s gallery (already-present images are not duplicated); Replace overwrites the gallery with this run’s images.
Only elements in your own workspace can be updated — curated library elements are read-only. If no images reach the node, nothing is saved and downstream nodes skip.