From b2c-cli
Lists, uploads, downloads, and manages files on Salesforce B2C Commerce instances via WebDAV. Use for IMPEX imports/exports, sandbox file transfers, and browsing instance file systems.
How this skill is triggered — by the user, by Claude, or both
Slash command
/b2c-cli:b2c-webdavThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use the `b2c` CLI plugin to perform WebDAV file operations on Salesforce B2C Commerce instances. This includes listing files, uploading, downloading, and managing files across different WebDAV roots.
Use the b2c CLI plugin to perform WebDAV file operations on Salesforce B2C Commerce instances. This includes listing files, uploading, downloading, and managing files across different WebDAV roots.
Tip: If
b2cis not installed globally, usenpx @salesforce/b2c-cliinstead (e.g.,npx @salesforce/b2c-cli webdav ls).
The CLI auto-discovers the target instance and credentials from SFCC_* environment variables, dw.json in the current or parent directories, ~/.mobify, package.json, and configuration plugins. Flags like --server, --client-id, --client-secret, --username, and --password are usually unnecessary — only pass them to override what's auto-detected.
Run b2c setup inspect to see the resolved configuration and which source provided each value (use --json for scripting, --unmask to reveal secrets). For precedence rules and troubleshooting, see the b2c-cli:b2c-config skill.
The --root flag specifies the WebDAV directory:
impex (default) - Import/Export directorytemp - Temporary filescartridges - Code cartridgesrealmdata - Realm datacatalogs - Product catalogslibraries - Content librariesstatic - Static resourceslogs - Application logssecuritylogs - Security logs# list files in the default IMPEX root
b2c webdav ls
# list files in a specific path
b2c webdav ls src/instance
# list files in the cartridges root
b2c webdav ls --root=cartridges
# list files with JSON output
b2c webdav ls --root=impex --json
# download a file from IMPEX (default root)
b2c webdav get src/instance/export.zip
# download to a specific local path
b2c webdav get src/instance/export.zip -o ./downloads/export.zip
# download from a specific root
b2c webdav get customerror.log --root=logs
# output file content to stdout
b2c webdav get src/instance/data.xml -o -
# upload a file to IMPEX
b2c webdav put ./local-file.zip src/instance/
# upload to a specific root
b2c webdav put ./my-cartridge.zip --root=cartridges
# create a directory in IMPEX
b2c webdav mkdir src/instance/my-folder
# create a directory in a specific root
b2c webdav mkdir my-folder --root=temp
# delete a file
b2c webdav rm src/instance/old-export.zip
# delete from a specific root
b2c webdav rm old-file.txt --root=temp
To delete cartridges from a code version, use the cartridges root with the path format {code-version}/{cartridge-name}:
# delete a cartridge from a code version
b2c webdav rm v25_1_0/app_mysite --root=cartridges
# delete multiple cartridges
b2c webdav rm v25_1_0/app_mysite --root=cartridges
b2c webdav rm v25_1_0/int_myintegration --root=cartridges
# list cartridges in a code version first
b2c webdav ls v25_1_0 --root=cartridges
Important: The path is {code-version}/{cartridge-name}, not /cartridges/{code-version}/.... The --root=cartridges (or -r cartridges) flag sets the WebDAV root.
# create a zip archive of a remote directory
b2c webdav zip src/instance/my-folder
# extract a remote zip archive
b2c webdav unzip src/instance/archive.zip
See b2c webdav --help for a full list of available commands and options in the webdav topic.
b2c-cli:b2c-logs - Filtered log retrieval, search, and real-time tailing (preferred for log exploration)b2c-cli:b2c-code - Higher-level code deployment (preferred for cartridge upload)b2c-cli:b2c-job - Import/export site archivesnpx claudepluginhub salesforcecommercecloud/b2c-developer-tooling --plugin b2c-cliManages B2C Commerce cartridge code via deploy, download, activate, and watch commands. Useful for pushing code to sandboxes, pulling code, and setting up dev workflows with live reload.
Builds SFCC B2C Commerce cartridges with directory structure (controllers/, models/, scripts/, templates/, static/), stacking, naming (app_custom_*, plugin_*), path config, and certification requirements. Use for creating or modifying cartridges.
Build backend integrations syncing data between B2C Commerce and ERPs, OMS, WMS, or CRMs using SCAPI Admin APIs with OAuth client credentials.