Heroku
Give the Sazabi agent the Heroku CLI (heroku) in its sandbox to manage apps, dynos, releases, and logs.
About
This CLI connection makes the Heroku CLI (heroku) available in the Sazabi agent's sandbox. The tool is baked into the sandbox image; connecting it authenticates the already-installed CLI.
Prerequisites
- A Sazabi project.
- A Heroku API key (
HEROKU_API_KEY), available from your Heroku account settings.
Set up in the dashboard
Configure the sandbox in the dashboard under Settings > Sandbox CLIs.
Find Heroku in the catalog
In Settings > Sandbox CLIs, find Heroku under Browse sandbox CLIs and choose to connect it.
Provide credentials
Enter the required value: HEROKU_API_KEY — your Heroku API key. Save to store it securely; Sazabi injects it into the sandbox when the agent runs.
Set up with the CLI
You can also configure the Heroku CLI connection with the Sazabi CLI (installed and authenticated — see CLI reference).
sazabi sandbox-clis set --type heroku --env HEROKU_API_KEY=<your-heroku-key>To validate the credentials without saving, run the same command with test in place of set (the test command also requires the --env flags).
Verify
Ask the agent, in a thread, to run the heroku CLI (a read-only or status command) and confirm it returns real output. If the command is not found, the CLI connection may not be enabled; if it runs unauthenticated or cannot connect, recheck the credentials.
Troubleshooting
Command not found — Confirm the Heroku CLI connection is enabled for the project under Settings > Sandbox CLIs.
Authentication or connection fails — Recheck the credential/connection values under Settings > Sandbox CLIs.