Chat SDK now supports Slack Enterprise Grid

Vercel has updated its Chat SDK’s Slack adapter to support Slack Enterprise Grid, allowing bots installed at the organization level to function across all workspaces within an enterprise. The adapter now stores installations by enterprise ID, ensuring tokens are resolved correctly for incoming events, slash commands, and interactive payloads. This change aligns token resolution methods for both HTTP webhooks and Socket Mode, maintaining consistent behavior regardless of the communication method used.

The update introduces tenant-scoped caching for user profiles and mentions, preventing data from one workspace from resolving in another. API calls made with an organization-wide token automatically include the event’s team_id, a requirement for workspace-scoped Slack methods. Events are routed based on the installation identity in the envelope’s authorizations field, ensuring accurate handling for Slack Connect shared channels.

To improve reliability, the adapter deduplicates retried event deliveries for 24 hours, addressing Slack’s Delayed Events redeliveries. Outgoing mentions now accept W-prefixed Grid user IDs in addition to the standard U-prefixed IDs, expanding compatibility for enterprise environments. Single-workspace installations remain unaffected and continue to operate as before.

Developers can now access updated documentation for the Slack adapter to begin implementing organization-wide bot installations. The changes simplify deployment for large enterprises while maintaining backward compatibility for existing single-workspace setups.