sendsets-cli

Driving SendSets through the sendsets CLI

sendsets is the customer CLI: it signs in as a person, keeps its own credential, and speaks only the public REST API. Every command is bounded by the scopes the sign-in approved. Never open, print or copy the CLI's stored credential; sendsets auth status --json says everything an agent needs.

If the binary is not on PATH, install it without a toolchain or root:

Install it with brew install addisonhoff/tap/sendsets (macOS, Linux) or scoop bucket add sendsets https://github.com/AddisonHoff/homebrew-tap then scoop install sendsets (Windows). Without a package manager, download the archive for your platform and checksums.txt from https://github.com/AddisonHoff/sendsets-releases/releases/latest, check the archive against checksums.txt, and unpack the sendsets binary onto PATH. It is also inside the backend image on a self-hosted instance (docker compose -p sendsets exec backend sendsets ...).

It is not sendsetsctl. That one talks to Postgres and exists for recovery and accounts (the sendsets-ops skill). If both are available and the task is product work, use sendsets.

The setup order

From nothing to a launched campaign, every step is a command and every failure prints a fix: line:

sendsets login --hostname sendsetsapi.com   # or SENDSETS_TOKEN=ssk_... plus SENDSETS_HOST=sendsetsapi.com
sendsets whoami                     # workspace, credential, scopes, agent policy
sendsets doctor                     # what is set up, what is not, a fix per gap; exit 1 when not ready
sendsets connection create --name app --base-url https://app.example.com/sendsets   # secret printed once
sendsets connection test CONNECTION_ID
sendsets mailbox add --provider outlook                                           # prints a Microsoft consent link
sendsets mailbox provision providers                                                              # what can be ordered, with live per-mailbox pricing
sendsets mailbox provision renewals                                                               # when managed domains renew, and anything needing a person
sendsets mailbox provision --provider google --count 3 --domain acme-outreach.com --warmup --wait   # SendSets Cloud: managed inboxes, checkout link for the user
sendsets mailbox provision --provider google --count 25 --domains a.com,b.com,c.com --warmup        # spread mailboxes across several domains
sendsets mailbox test MAILBOX_ID
sendsets mailbox warmup enable MAILBOX_ID
sendsets events send trial.started --email [email protected] --data '{"plan":"pro"}'
sendsets campaign create --name "Q3" --daily-limit 25 --stop-on-reply                         # 25 per mailbox per day, not per campaign
sendsets campaign add-step CAMPAIGN_ID --subject "..." --body-plain "Hi {{.FirstName}}"
sendsets campaign add-step CAMPAIGN_ID --kind app_action --connection CONNECTION_ID --path /audit --output-key audit --inputs '{"domain":"{{.Company}}"}'
sendsets campaign add-step CAMPAIGN_ID --kind wait_for_event --event report.opened --timeout-minutes 4320
sendsets campaign set-senders CAMPAIGN_ID --input '{"senders":[{"email_account_id":"MAILBOX_ID"}]}'
sendsets campaign validate CAMPAIGN_ID     # exit 1 with the problems and fixes when it cannot launch
sendsets campaign test CAMPAIGN_ID --prospect [email protected] --wait   # real mail, real app calls, one prospect
sendsets events send report.opened --email [email protected]             # from another shell when the test waits
sendsets campaign start CAMPAIGN_ID        # policy or human approval decides