canonical: https://jentic.com/apis/slack.com

# Slack APIs

Slack is a team communication platform whose APIs let agents post messages, manage channels and conversations, upload files, search message history, and administer workspaces. The portfolio spans the full Slack Web API with 169 messaging and administration endpoints, plus a dedicated AI message search operation. Together these cover programmatic notification delivery, channel lifecycle management, file distribution, and conversation retrieval across a Slack workspace.

## For AI agents

An agent can post and format messages, create and configure channels, invite and manage members, upload and share files, add reactions, and administer workspace settings through Slack's 169-endpoint Web API, and it can run AI-driven message search across a workspace through the Slack AI Plugin.

## Scope

Use for: Posting and searching Slack messages, managing channels and membership, sharing files, and administering a Slack workspace programmatically

Not supported:
- video calls
- project management
- email delivery
- customer-facing CRM messaging
- cross-channel SMS

## APIs

| API | Category | Endpoints | Description |
| --- | --- | --- | --- |
| Slack Web API | communications | 169 | Post messages, manage channels, query conversations, and administer Slack workspaces. |
| Slack AI Plugin | communications | 1 | Programmatically ai_alpha_search_messages. |

## Which API to use

| Need | API | Why |
| --- | --- | --- |
| Post messages, manage channels, upload files, or administer a workspace | main | The Slack Web API covers 169 endpoints for messaging, channel lifecycle, file sharing, reactions, and workspace administration. |
| Run AI-driven search across workspace messages | openai | The Slack AI Plugin exposes a dedicated ai.alpha.search.messages operation for intent-style message retrieval. |
| Find messages by keyword, sender, or date modifiers | main | The Web API search.messages endpoint supports Slack search modifiers like from, in, and before for precise keyword queries. |

## Cross-API use cases

### Search then notify in a workspace

An agent runs AI message search to surface conversations about a topic, then posts a summary or alert back into the relevant channel. This pairs the Slack AI Plugin search operation with the Web API message posting endpoints to close the loop from retrieval to action.

Example prompt: Use ai.alpha.search.messages to find messages mentioning 'outage' in the last day, then post a summarized alert to channel C0123456 via chat.postMessage

### Knowledge retrieval with follow-up sharing

An agent searches workspace messages for relevant discussion, retrieves matching threads, and uploads a compiled document back to a channel with a comment. This combines AI-driven and keyword search with the Web API file upload flow.

Example prompt: Search messages for a project topic with the AI Plugin, fetch matching thread history via conversations.history, then upload a summary file to the project channel with files.getUploadURLExternal and files.completeUploadExternal

## Why Jentic

- **Setup:** Wiring Slack by hand means running the OAuth 2.0 authorization code flow, requesting the right scopes, and refreshing tokens before you can post messages or search conversations. With Jentic you install Jentic One once, add the Slack APIs from the Jentic directory, store credentials once, and your agent calls them.
- **Permission scoping:** Slack passes the channel in the request body rather than in the path, so you limit the agent to the operations it needs, such as posting a message or searching history. Operations like creating channels, inviting users, or workspace administration are not available unless you add them to the allowed set.
- **Credential handling:** Your Slack OAuth token is stored once, encrypted, by your own Jentic One instance and injected at execution time; the AI Plugin operation needs no standing credential. Secrets never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'post a message to a channel' or 'search Slack messages', and Jentic returns the matching Slack operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related vendors

- **Twilio** — Reaches users across SMS, WhatsApp, and chat from one API when messaging must extend beyond Slack workspace members.
- **Zoom** — Adds programmatic video meetings and recordings that complement Slack's text and file collaboration.
- **Asana** — Provides structured task management that pairs with Slack for turning conversations into tracked work.
- **HubSpot** — Handles customer-facing conversations tied to CRM records when messaging is external rather than internal team chat.

## FAQ

### Which Slack API should an agent use for a given task?

Use the Slack Web API for anything involving posting messages, managing channels and membership, uploading files, adding reactions, or administering a workspace. Use the Slack AI Plugin when you specifically want AI-driven search across workspace messages. Many workflows combine the two: search with the AI Plugin, then act with the Web API.

### Do the two Slack APIs share the same authentication?

No. The Slack Web API uses OAuth 2.0 with granular scopes and bot or user tokens, while the Slack AI Plugin operation requires no standing credential. Because they differ, you configure and scope each API independently rather than reusing one credential across both.

### Can an agent both find and act on Slack messages?

Yes. The Slack AI Plugin provides message search, and the Slack Web API provides posting, threading, reactions, and file sharing. An agent can search for relevant conversations first and then post a reply, share a file, or notify a channel using the Web API endpoints.

### How much of a Slack workspace can these APIs manage?

The Slack Web API alone covers 169 endpoints spanning messaging, channel creation and archiving, membership, files, reactions, user groups, and workspace-level administration such as apps, emoji, and teams. The AI Plugin adds intent-style message search on top of that.

### Can an agent be limited to only certain Slack operations?

Yes. Slack's OAuth scope model authorizes operations independently, and you can restrict an agent to just the operations it needs, such as posting messages or reading history, without granting channel creation or user invitation. The AI Plugin similarly exposes only its single search operation.

### What communication tasks are outside these APIs?

These APIs cover internal Slack workspace messaging and search. They do not handle video conferencing, structured project or task management, transactional email, or customer-facing messaging tied to CRM records. For those, pair Slack with a dedicated video, task, email, or CRM API.