Slack
Install the ABM.dev Slack app in your workspace. One-click OAuth provisions a bot token so you can post enrichment notifications, approvals, and webhooks into any channel.
What the app does today
- Slack OAuth 2 install flow with secure state parameter
- Bot token scoped to
chat:write,commands, andincoming-webhook - One workspace per org, stored encrypted at rest
- Installations list + disconnect from your dashboard
Still in beta
Install the app
Kick off the Slack OAuth flow by hitting /api/v1/slack/install. You'll be redirected to Slack to pick a workspace and authorise the ABM.dev app.
After approval Slack sends you back to /settings/integrations?slack=success and the bot token is stored (encrypted) against your organisation.
List installations
Confirm the install landed by calling the installations endpoint. Tokens are never returned — you'll see the team, bot user, and install timestamp.
curl -s https://api.abm.dev/v1/slack/installations \
-H "x-api-key: YOUR_API_KEY" | jq .Disconnect a workspace
Revoke the installation by DELETE-ing the team from the same endpoint. This removes the stored bot token.
curl -X DELETE \
https://api.abm.dev/v1/slack/installations/TEAM_ID \
-H "x-api-key: YOUR_API_KEY"Token rotation
Self-hosting configuration
If you're running your own ABM.dev deployment, set these app settings so the OAuth flow can complete:
| Setting | Description |
|---|---|
Slack:ClientId | OAuth client ID from your Slack app config. |
Slack:ClientSecret | OAuth client secret from your Slack app. |
Slack:RedirectBaseUrl | Public URL of your API (e.g. https://api.abm.dev). The callback path /api/v1/slack/oauth/callback is appended automatically. |