For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Resources
Get started
GuidesExamplesChangelog
GuidesExamplesChangelog
  • Code Components
    • Introduction
    • Component Architecture
    • Styling Components
  • Importing Code Components
    • Quick start: Importing code components
    • Installation
    • Define a code component
    • Bundling & Import
  • Generating AI Code Components
    • Quick start: Generating AI code components
  • FAQs
    • FAQs and troubleshooting
  • Reference
    • Webflow CLI
    • Prop Types
LogoLogo
Resources
Get started
On this page
  • Installation
  • Commands
  • Import
  • Bundle
  • Log
  • CI/CD workflows
  • Troubleshooting
Reference

Webflow CLI

Learn about the Webflow CLI and DevLink.
Was this page helpful?
Previous

Define a code component

Next
Built with

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:

$npm i --save-dev @webflow/webflow-cli

Commands

Import

To share your library to your Workspace, use the following command:

$webflow devlink import

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:

Command OptionDescriptionDefault
--manifestProvide the path to the webflow.json file.Scans the current directory for webflow.json.
--api-tokenPass a Workspace API token.Uses WEBFLOW_WORKSPACE_API_TOKEN from the .env file.
--no-inputAvoid prompting or doing anything interactive. Useful for CI/CD pipelines.No
--verboseDisplay more information for debugging purposes.No
--devBundle in development mode for debugging purposes. This will disable minification and source maps.No

Bundle

Bundle your library locally for debugging and testing. The import command automatically bundles your library, but you can use bundle for local development.

$webflow devlink bundle --public-path http://localhost:4000/

Options

Command OptionDescription
--public-pathRequired. The URL where you can serve your library.
--forceForces the bundler to finish compiling, even if there are warnings.
--devBundle in development mode for debugging purposes. This will disable minification and source maps.
--debug-bundlerPrint the final configuration being used by webpack.

Log

Get the logs with debug information for your last library import.

$webflow log

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
$webflow devlink import --no-input

Troubleshooting

Authentication

If you’re having trouble authenticating with your Workspace, try the following:

  • Check your .env file for the WEBFLOW_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.

    $webflow devlink import --verbose

  • If you’re still having trouble, try running the share command with the --api-token flag to manually pass in your API token.

    $webflow devlink import --api-token <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.