webflow-cli:cloud
Webflow Cloud
Initialize new projects from templates or an existing GitHub repository, deploy to Webflow Cloud, and manage existing apps (list, inspect, logs, deployments, environments, environment variables). Deploys support two modes: site-attached (deploy to an existing Webflow site) and project app (deploy as an independent app, no existing site required).
Namespaces: apps (canonical) vs cloud (deprecated alias)
webflow apps <command> is the canonical namespace for Webflow Cloud. webflow cloud <command> still works — its init / deploy forms are aliases of the same handler — but is deprecated in favor of apps.
| Canonical | Deprecated cloud alias |
Notes |
|---|---|---|
webflow apps init |
webflow cloud init |
Same options + handler — except --import and its repo-intake flags, which attach to apps init only. |
webflow apps deploy |
webflow cloud deploy |
Same handler — except --json and --dry-run, which attach to apps deploy only. |
| — | webflow cloud create <name> |
Deprecated ahead of removal; prefer apps init (or cloud init if staying on the legacy namespace). |
| — | webflow cloud list |
Lists scaffold templates, not apps. Stays under cloud; there is no apps equivalent. Do not confuse with apps list, which lists workspace apps. |
webflow apps list / get / domains / link / update / delete / environments … / deployments … / logs … / env-vars … |
— | No cloud equivalent. Canonical-only. |
Running a command through cloud init / cloud deploy prints a one-time deprecation notice on stderr pointing at the apps form (suppressed with --json).
Prefer the apps forms in all new work. This skill shows apps commands throughout; every apps init / apps deploy invocation can be run as cloud init / cloud deploy with identical flags, apart from --import (init) and --json/--dry-run (deploy).