Deploy & embed

You can build the project in the app, deploy the built assets to a CDN (Cloudflare), and copy a Webflow-ready embed snippet to paste into your site’s custom code.

Requirements

• Signed in — Deploy and embed are available when you’re authenticated (and, when applicable, have an active plan).
• Project builds successfully — Use the terminal Build action first; deployment uses the built output (e.g. JS and CSS).

Deploy flow

1. Run Build from the terminal panel so the project produces its bundle(s) (e.g. app.js, styles/out.css).
2. Click Deploy (or the deploy action in the terminal area). The app uploads the built files to Cloudflare (e.g. R2 or Pages) and invalidates cache as needed.
3. After a successful deploy, you get a base URL for the deployed assets (e.g. https://…/username/project-name/).

Embed snippet

• Click Embed (or the embed action) to get a snippet you can paste into Webflow’s custom code (e.g. in site or page settings).
• The snippet uses a double-script pattern: it tries the local dev origin first (e.g. for local testing), and on error falls back to the deployed URL so published sites always load the deployed version.
• It includes:
  • A <link rel="stylesheet"> for the built CSS (with the same local → deployed fallback).
  • A <script defer> for the built JS (with the same fallback).

After deploying again, the same snippet keeps working because it points at a stable base URL; cache invalidation ensures the new files are served.

Namespace

Deploys are scoped by user and project (e.g. @username/project-name/). The exact path format depends on your Cloudflare setup; the app uses it to avoid collisions between users and projects.