Skip to main content
This page explains what the Storefront Builder step does. For the fields it takes, and which are required, see Step types.
Storefront Builder can build your storefront using a plain-language prompt. The result is always a draft that goes live only after you deploy it. On the automation canvas the step appears as Storefront Builder. You can use it to create or update storefront pages, write blog posts, and much more.

​
Example use cases

  • Daily best-sellers guide: a schedule event, insights ranks products, Custom agent writes the article, the builder rewrites the page, approval gates the deploy.
  • Launch page on publish: a product-published event, Custom agent drafts the copy, the builder adds the page as a draft for review.
  • Seasonal refresh: a scheduled rewrite of a landing section with current catalog highlights.

​
Writing the prompt

Describe the change the way a store owner would. Name the page by its URL and pass the content in from upstream steps. The builder owns files, components, and styling.
  • Name the target page by URL: “Update the guide page at /guides/best-sellers, replacing what is there now.”
  • For recurring automations, say “replacing what is there now”. The page itself is the state between runs.
  • Pass content in from upstream insights and ai_reasoning steps. The builder renders content; it does not research it.
  • For SEO or editorial pages, end the prompt with /colossal-content-pages to load the content-page craft skill.

​
Review and deploy

A typical flow is to run Storefront Builder, approval step and then deploy step. This way you will be able to check the results before deploying them. The deploy leg is optional. Without it, the draft waits in the storefront editor and you deploy from there.

​
Constraints

  • One builder runs at a time per store. A step that arrives while another build or chat edit is running waits in a queue.
  • Builder steps cannot run inside map or parallel steps.
  • Builder steps are not allowed in automations that return a synchronous response.
  • The build is verified before the draft is saved. A failed build fails the step and nothing changes.

​
Next steps