Webflow CLI
The Webflow CLI is the command line interface for developers to interact with Webflow. Use the CLI to manage DevLink by:
- Authenticating with your Webflow workspace or site
- Bundling components into importable libraries
- Exporting components from Webflow
- Importing components into Webflow
You can use the CLI directly in your project or in CI/CD pipelines to automate library imports.
Installation
The Webflow CLI is available as a package on npm. You can install it to your project with the following command:
Commands
Import
To share your library to your Workspace, use the following command:
This command will:
- Authorize your workspace: The CLI will check for a Workspace authentication token in your
.env
file. If one isn’t found, the CLI will prompt you to authenticate by opening a browser window to the Workspace authorization page. - Bundle your library: The CLI will bundle your library, and ask you to confirm the components you want to share.
- Upload your library to your Workspace
Options
You can use the following options to customize sharing:
Bundle
Bundle your library locally for debugging and testing. The share
command automatically bundles your library, but you can use bundle
for local development.
Options
Log
Get the logs with debug information for your last library import.
CI/CD workflows
Use the CLI in automated workflows by adding the --no-input
option to avoid interactive prompts.
Important: Implement change detection before sharing to avoid unintentionally removing components:
- Compare current library state with previous import
- Only share when components have actually changed
Troubleshooting
Authentication
If you’re having trouble authenticating with your Workspace, try the following:
-
Check your
.env
file for theWEBFLOW_WORKSPACE_API_TOKEN
variable. Be sure to use a Workspace API token, not a Site API token. -
Try running the share command with the
--verbose
flag to see if there is additional information in the output. -
If you’re still having trouble, try running the share command with the
--api-token
flag to manually pass in your API token.
Prompts for component removal
If the CLI is warning you that you’re about to remove components, it’s because the CLI is comparing the current library state with the previous import. Be sure your component name matches the name in the previous . Otherwise, the CLI will create a new component and remove the old one.