plugsync-cli
Command-line client for plugsync, managing HubSpot connectors like code: pull a connector's config to a local directory, edit it, push it back to the draft, diff against a published version, validate, preview a publish, and manage plugins -- all without cloning the plugsync backend repo.
push writes the draft and stops. Publishing is opt-in (push --publish),
so a config never reaches production as a side effect of saving a file.
Install
pip install plugsync-cli
Requires Python 3.12+.
Quickstart
plugsync auth login -e you@example.com
plugsync pull my-connector
api_url defaults to the hosted platform (https://app.plugsync.com), so
there's nothing to configure for the common case. Point it elsewhere with
plugsync config set api_url <url>. plugsync auth login saves a bearer
credential to ~/.plugsync/config.yaml that every subsequent command
reuses. PLUGSYNC_API_URL / PLUGSYNC_API_KEY environment variables
override the config file, handy for CI.
Commands
| Command | Purpose |
|---|---|
plugsync auth login / logout |
Authenticate (email/password JWT, or a long-lived org API key with --token) |
plugsync config set/get/show |
Manage ~/.plugsync/config.yaml |
plugsync pull <name> |
Download a connector's draft as a local directory (--revision N for a published version) |
plugsync push <name> |
Upload a local connector directory to the draft (--publish to also publish) |
plugsync diff <name> |
Diff local files vs. a published version |
plugsync validate <name> |
Preflight the draft; non-zero exit on an error |
plugsync preview <name> |
Preview a publish's effects and its preflight findings |
plugsync log <name> |
Show a connector's published version history |
plugsync rollback <name> |
Restore a published version into the draft |
plugsync plugin init/push/list/status/logs/metrics/invoke/promote/publish/rollback |
Author and manage plugins (Enterprise tier) |
Run plugsync --help or plugsync <command> --help for the full option list.
Compatibility
This CLI ships on its own release cadence, independent of the plugsync backend. It declares the minimum API version it expects and checks it against the API at the start of any command that talks to it, warning (never failing outright) if the API is older than expected.
Documentation
Full reference docs, including the plugin authoring dev-loop, live at docs.plugsync.com and in the plugsync repository.
License
Proprietary. This CLI talks to the plugsync SaaS API; see plugsync.com/terms for the terms governing use of the plugsync service.
1 maintainer
Metadata
1 maintainer
Release files for plugsync-cli 0.4.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| plugsync_cli-0.4.0.tar.gz | 82.8 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| plugsync_cli-0.4.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 133.5 kB
Release files / plugsync_cli-0.4.0.tar.gz
| Download URL | plugsync_cli-0.4.0.tar.gz |
|---|---|
| Size | 82.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8121c52274961aee2599702c198930581a796507be943c00681da5eeb66f8e06
|
|
BLAKE2b-256 checksum How to use checksums |
d67255b1537e5d89eb937f464fdd9a4fb64c6504b09a7eb809d7af4dd000bc6e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 8, 2026.
Transparency logRelease files / plugsync_cli-0.4.0-py3-none-any.whl
| Download URL | plugsync_cli-0.4.0-py3-none-any.whl |
|---|---|
| Size | 50.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ecfffc46e5e46c27e8068877eda4d78d30fa261f01e6316cd0ce5dc6f3c46756
|
|
BLAKE2b-256 checksum How to use checksums |
25261c61e39969f7f6960f583fd4743a20bea9ef2b27804fca1c88ed6365be93
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 8, 2026.
Transparency logSecurity for plugsync-cli 0.4.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for plugsync_cli-0.4.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 8, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
