Skip to main content
Slack is a bundled OAuth2 provider in authsome. Workspace channels and chat write. Add more scopes through --scopes.

​
At a glance

​
Prerequisites

You need to register an OAuth app with Slack once. Create a Slack app in the API portal. Under OAuth & Permissions, add http://127.0.0.1:7998/auth/callback/oauth as a redirect URL. The redirect URI must be:
This is the only callback URL authsome’s PKCE flow listens on. Dashboard: https://api.slack.com/apps.
Slack’s OAuth v2 endpoint does not require PKCE. Authsome runs the standard authorization-code flow.

​
Log in

The first time, authsome opens a local form at http://127.0.0.1:7998 to collect your client_id and client_secret. They are encrypted in your vault and reused on every subsequent login. A second browser window then opens to https://slack.com/oauth/v2/authorize for the authorization step. Verify:

​
Custom scopes

The bundled definition requests channels:read, chat:write. Override at login time:
The granted scopes are stored on the connection and visible in authsome get slack.

​
Multiple accounts

Pass --connection <name> on login and on every read command to keep two or more accounts on the same provider side by side. See Multiple connections per provider for the full pattern.

​
Use the token

Run the agent under the proxy (recommended).
Under the proxy, authsome sets SLACK_ACCESS_TOKEN=authsome-proxy-managed in the child’s environment and injects the real token into outbound requests to slack.com. The child process never sees the actual value. Refresh tokens are never exported.

​
Override the bundled definition

User-registered files always win over bundled definitions.

​
What’s next

Run agents with the proxy

Inject the access token into outbound requests without exposing it.

Multiple connections per provider

Keep two or more accounts on the same provider side by side.

OAuth providers

All bundled OAuth providers.