Run the same site publishing pipeline from Flowgen, using a connected Website checkpoint and an explicit Preview or Live target.
Where: Flowgen -> Add -> Web & Apps -> Publish Site
Before you start
- A Website bundle connected to doc_in.
- A saved Website checkpoint. Open and save the Website Editor once if the document has never produced one.
- Publishing permission and a signed-in account for site creation when needed.
Key ideas
- The Website document is authoritative: Publish Site reads the connected Website’s saved .fmo checkpoint and site identity. It does not publish an unrelated open editor store or invent separate domain/watermark controls.
- Preview is the default: Preview/staging is for review and can expire. Live/production changes the public site. A target_in word can override the card only when it is recognized.
- Same pipeline as editor Publish: The node uses the site’s normal publish lifecycle, domain, watermark, plan rules, and no-change detection. It is a canvas entry point, not a second publisher.
Steps
- Connect Website to doc_in.
- Choose Preview or Live. For an automated choice, connect target_in with preview/staging or live/production; a readable wire wins.
- Run the node. For Live, do so only after the user explicitly asked for a public publish.
- Open the returned address and verify the actual target, domain, content, and staging expiry when present.
- Use the Addresses tab reached from Publish to manage the site’s current addresses.
Sockets
- Website / doc_in: one editor document bundle.
- Where / target_in: one readable target word.
- Published address / text_out: the resulting URL.
Target vocabulary
- preview or staging -> Preview.
- live or production -> Live.
- Unrecognized text is ignored with a warning and the card selection remains in effect.
- Default: Preview.
Inherited publishing rules
- The document’s site project identity is reused.
- Domain, plan, and watermark rules come from the site/account.
- A Preview result can include an expiry.
- A no-change publish reports that nothing changed rather than manufacturing a new deployment.
- Template and entry changes participate in site dirty-state detection.
Tips
- Keep the card on Preview in reusable flows and drive Live through a deliberate approval/target input.
- Save the Website before publishing after structural edits.
- Use Pause for Approval immediately before an automated Live target.
Limitations and important notes
- The node cannot publish an unsaved/empty Website checkpoint.
- Preview expiry is controlled by the publishing service.
- Live is an external action and should not be inferred from a vague request.
- The node publishes the site; it does not create CMS entries.
Troubleshooting
Publish says the Website has no saved document
Open Website Editor, wait for the document to load, save it, then run Publish Site again.
The wrong target was used
Inspect target_in. A recognized wire wins over the card; invalid text is ignored and leaves the card target active.