Skip to main content
The Artifact node is used to draft and publish websites, blog posts and apps to your public URL.

Operation modes

An Artifact node with its toolbar popover open showing Operation, Auto-publish, Visibility and File path
The Artifact node has three modes. Select the node and click the operation button on its toolbar (Get artifact, Create artifact or Update artifact) to open its settings, then pick an Operation:
  • Create: make a new artifact from connected content
  • Update: replace an existing artifact’s content
  • Get: fetch the content of an existing artifact
The mode determines which inputs are visible on the node (name only appears for Create, artifact_id appears for Update and Get, etc.).

Create mode

Create mode is selected by default when you add a new Artifact node to the canvas. Connect content (markdown, HTML, or generated text) to the Content input and give it a Name.

Artifact type

The artifact type is inferred from the content’s format at publish time:
  • Website: HTML pages with optional CSS and JS
  • Blog: long-form markdown writing
  • App: HTML that uses the window.runchat bridge to run your published tools

Auto-publish

By default, every run publishes the artifact immediately. Turn off Auto-publish in the toolbar popover if you’d rather review drafts on the Artifacts dashboard before publishing manually.

Visibility

Set Visibility in the toolbar popover to control who can view the published page: Private, Team or Public.

Update mode

Update mode replaces an existing artifact’s content. Provide the Artifact ID (typed or wired in from another node) and the new content.

File path

By default, Update writes to the artifact’s entry point file (e.g. index.html for a website, content.md for a blog). For multi-file artifacts, set File path in the toolbar popover (e.g. index.html or page-2.md) to target a specific file or page within the artifact. Click Make input to wire the path in from another node instead.

Get mode

Get mode fetches an existing artifact’s content. Provide the Artifact ID (typed or wired in) and the node returns the current content. Useful for chaining: read an existing artifact, transform it with an Agent or Code node, and update or create a new version.

Outputs

The node has four output parameters:
  • Content: the artifact’s content as text. Populated in Get mode; not returned by Create or Update.
  • Artifact ID: the artifact’s unique identifier. Newly assigned on Create, passed through on Update and Get.
  • URL: the public URL if the artifact is published, in the form runchat.com/artifacts/<handle>/<slug>.
  • Thumbnail: the artifact’s thumbnail image URL.

Next steps