Can the ChatGPT Slack integration DM individual users?

Yes, the agent can send DMs when the user has interacted with it or consented. For cold outreach via DM (e.g., agent notifying a user about a ticket), admin config controls whether the agent can initiate.

Does it work with Slack Connect (shared channels)?

Yes, but carefully. The agent will see messages from external org members in a Connect channel. Scope what the agent reads and writes in shared channels explicitly — these are the highest-risk surface.

Can we use Slack's Workflow Builder with Workspace Agents?

They coexist but don't integrate deeply. Slack workflows trigger deterministic actions; Workspace Agents add reasoning. Most teams use both — workflows for routing, agents for drafting / classification.

What about Slack huddles / voice?

Not supported. The integration is text-channel + DM based. Voice, huddles, and Clip are out of scope.

How do we handle PII in support channels?

Configure PII redaction at the prompt level before the agent sends anything to the reasoning model, if your compliance posture requires it. Workspace Agents don't do this automatically — the agent will see whatever's in the channel unless configured otherwise.

Integration · Updated April 23, 2026

ChatGPT + Slack: Workspace Agents Integration (2026)

Slack is the default surface for almost every business workflow — questions, alerts, requests, customer chatter. Connecting ChatGPT Workspace Agents to Slack turns that surface into the front door for agent interactions. This page covers what the integration does, the agents it enables, and the admin setup you'll need.

What the agent reads

Channel messages (public channels, or private channels where the agent is invited)
Threaded replies, reactions, and mentions
Direct messages to the agent
File uploads within Slack (when referenced)

What the agent writes

Channel messages + threaded replies
Direct messages to users
Reactions
Canvas updates (on paid Slack plans)

Common workflows on Slack

Support Triage Agent

Watches #support or a helpdesk channel, classifies each message, drafts a first-pass reply grounded in your docs, and routes tickets. The single highest-ROI Slack agent for most teams.

Weekly Metrics Reporter

Monday morning, posts a leadership digest with KPIs, WoW comparison, and a plain-English narrative — grounded in warehouse queries.

Pipeline Digest

Posts stale deals and missing next steps to #revops weekly. Reduces Monday-morning pipeline-review meeting time.

Competitive Intel Watcher

Weekly scan of top competitors, posts a curated digest to #competitive-research.

Slack-specific gotchas

Rate limits bite chatty agents

Slack rate-limits API calls aggressively. Agents that read many messages per minute (e.g., continuous monitoring of a high-volume channel) hit ceilings fast. Mitigations: scheduled reads instead of real-time, batch replies, throttle per-agent usage.

Tenant policies block external bots by default

Many Enterprise Slack tenants disable external app posting by default. Your Slack admin has to explicitly approve the Workspace Agents app + grant channel-level permissions. Plan for that conversation.

Private channels require invitation

The agent can't read private channels unless it's explicitly added. If you want the agent in a private channel, invite it like a user.

Message threading matters

Agents posting to a busy channel should usually thread replies rather than posting in-channel, to keep signal-to-noise high. Configure at prompt level.

Questions

Need a Slack-powered agent built?

20-min intro call. I've shipped multiple agents against this exact integration — I'll tell you what's realistic for your stack.

Book a 20-min intro call Or send a note

Agents that run on Slack

Other integrations

See the full Workspace Agents connectors list →