Integrations
Connect Bumpkit to the tools your team uses.
Connect Bumpkit to the tools your team uses.
Connect and manage
Connect on the dashboard's Integrations page, or from the CLI and API. Owners and admins connect, change, test and disconnect. Anything marked Coming soon can't be connected yet. Secrets are encrypted before they're stored (see Data Handling), and each change is written to the audit log as integration.connect or integration.disconnect; tests and retries are logged as integration.test, integration.test.failed and integration.retry.
If a delivery fails, for example because a webhook was deleted or a key was revoked, the integration's card on the Integrations page turns amber and its page says what failed and how to fix it, with a Reconnect form. bumpkit integrations list prints the same reason.
bumpkit integrations list
bumpkit integrations connect slack
bumpkit integrations test slack
bumpkit integrations disconnect slack --yesThe CLI never takes a secret from your shell history: leave the secret flag out to be prompted, or pass - to read it from standard input. The integrations_list, integrations_connect, integrations_test and integrations_disconnect MCP tools do the same from your agent.
| Endpoint | Purpose |
|---|---|
GET /v1/integrations |
Each integration's name, connected, a masked detail and last_error when the last delivery failed; an integration with several parts also lists its capabilities, each with key, name, connected and coming_soon |
PUT /v1/integrations/{name} |
Connect: url, api_key, team, host, project_id (and settings for change management) |
DELETE /v1/integrations/{name} |
Disconnect |
POST /v1/integrations/{name}/test |
Send a test message or check the connection |