Install or update an add-on from a ZIP file

Paid versionModules

Add-ons are installed or updated from a trusted link in one conversation, with checks before and after and a copy of the old files.

What it replaces: 30-60 min per add-on update

What you write to Claude

„update the paynow module to the 2.4.1 zip from this github release link. check the shop before and after and tell me if anything in the logs changes”

The problem

A client's payment add-on has a new version on the author's site. Updating it means logging into their back office, downloading, uploading and hoping.

What Claude does

  1. Claude checks the shop and the installed version first.
  2. It downloads the package and shows its name, version, source and fingerprint before anything happens.
  3. After your yes it installs or updates the add-on, keeping a copy of the old files.
  4. It checks the shop and error messages again and reports any difference.

What you get

The add-on runs the new version, with a before-and-after check and the old files kept as a copy.

You stay in control

You see every change before it is saved and nothing happens without your yes. Work on add-ons uses a separate, extra-protected connection, usually set up by whoever looks after your shop, and add-on files are backed up before they change.

See pricing

Related use cases

For developers
Area
4 · Modules
Connector
service connector
In the free Audit
no, paid version only
For
Agency / freelancer, Developer
Tools
ps_check_shop_health, ps_list_modules, ps_get_logs, ps_install_module, ps_inspect_page, ps_restore_file_backup

Step by step

  1. Baseline with ps_check_shop_health, ps_list_modules (installed version) and ps_get_logs.
  2. Calls ps_install_module (action install or update, url = https ZIP); the preview downloads and checks the package: module name and version, source, SHA-256, a single module folder, no unsafe paths.
  3. After approval installs or updates (usually 20-60 s); an update backs up the module files first.
  4. Re-checks with ps_check_shop_health, ps_get_logs and ps_inspect_page on key pages.
  5. Recommends doing it on a staging domain first (free on every licence).

Safety

Modules (block 4) work only through the service connector (separate token accepted only from allowlisted IP addresses) and are off after installation; the owner gets an e-mail when the block is switched on. Every write shows a preview, runs only after your approval (one-time token) and is logged in the change history. A ZIP is code that runs on the shop's server, so install only from trusted sources; only https links are accepted. Module files of an update can be restored from the backup, but database changes made by the module's own upgrade cannot be undone.

Last updated: 2026-10-05