← Back to Blog

Slack OAuth for AI Agents: TapAuth Now Supports Slack as a Provider

Jonah Schwartz·

Today we're shipping Slack as a first-class OAuth provider in TapAuth. Your AI agents can now authenticate with Slack workspaces, request scoped permissions, and act on behalf of users — all through the same access gateway your agents already use for GitHub, Google, and Vercel.

Why Slack Matters for Agents

Slack is where work happens. It's where teams coordinate, where alerts land, where decisions get made. If your AI agent can read a GitHub PR but can't post a summary to the relevant Slack channel, it's only doing half the job.

But Slack's OAuth flow has quirks. The token response format differs from the OAuth 2.0 spec. Scopes are split between bot tokens and user tokens. Workspace-level installs behave differently from org-level ones. These are exactly the kinds of provider-specific edge cases that TapAuth absorbs so your agent doesn't have to.

How It Works

Same pattern as every other TapAuth provider:

  1. Your agent requests a Slack token through TapAuth's API
  2. If the user hasn't authorized yet, TapAuth handles the OAuth consent flow
  3. TapAuth stores the encrypted token and refreshes it automatically
  4. Your agent gets a scoped, valid token every time it asks

Under the hood, we built a custom OAuth client following the Arctic pattern we use for all providers. Slack's oauth.v2.access endpoint returns tokens in a nested structure that doesn't match standard OAuth responses — our provider class normalizes this so the rest of TapAuth's token pipeline works unchanged.

Scopes

TapAuth requests the scopes your agent actually needs. For Slack, common scopes include channels:read, chat:write, users:read, and identity.basic. You configure these per-connection, not globally — so one agent can read channels while another posts messages, each with minimal privilege.

Getting Started

If you're already using TapAuth, Slack is available now. Add it as a provider in your dashboard, configure your Slack app credentials, and your agents can start authenticating immediately. If you're new to TapAuth, check out the docs to get started.

Slack joins GitHub, Google, Vercel, and Linear in TapAuth's growing provider lineup. Every provider we add is one less OAuth integration your agents have to manage themselves — and one less place for credentials to leak.