The Blowhorn CLI
Everything the Mac app does, the CLI does too. That is why any agent can run Blowhorn.
How it works
- 1
Install Blowhorn
Blowhorn for Mac and the Blowhorn Chrome extension. Your posts go out from your own signed-in Chrome.
- 2
Built to be driven
Every app feature, as a command. A few lines and CLI knows the commands.
- 3
Say what you want
CLI turns it into blowhorn commands. You approve what publishes.
Built to be driven
Reads take --json. Writes take --expected-fingerprint so an agent never stomps a newer edit. Anything that publishes takes --dry-run. One switch stops every Mac at once, with a recorded reason.
blowhorn schedule status --json
blowhorn schedule pause --all --reason "launch moved to Thursday"
blowhorn schedule resume --allA few commands
blowhorn post --check-queue
blowhorn post --profile all --dry-run
blowhorn schedule list --due-only --profile all
blowhorn schedule trigger-now 7
blowhorn schedule pause --row 7
blowhorn analytics --platform x --profile all
blowhorn report --dry-runWhere it pays off
Scripts and cron
Plain commands with exit codes, so a shell script can run a launch the same way an agent does.
A fleet of Macs
Every Mac signed in to your account works the same schedule, coordinated so the same post isn't sent from two Macs.
Pause control
schedule pause --all stops every Mac; --row N parks one job everywhere; resume picks up where you left off.
Questions
Where do I find every command?
Run blowhorn -h for the full list with examples, or read the CLI reference in the docs.
Can I see what a command will do first?
Yes. Commands that act take --dry-run, and post --check-queue lists pending posts without publishing.
What happens when a post fails?
Within a run, Blowhorn doesn't retry a failed post; if a post goes out but can't be recorded, it stops that profile's queue; scheduled retries are off by default.
One message out, many ears in
Get Blowhorn for Mac, then let CLI do the talking.