Integrate the Slack API.Caddi writes and runs the integration for you.
Slack has a public web API. Self-serve for any developer who creates a Slack app; the app must be installed to a workspace to get tokens.
- 99%of agent runs complete successfully
- ~45 minon average to build your first agent
- 1M+back-office tasks completed
The connection is a project before it does anything.
Before the first record moves: an app registration, credentials, token refresh, and somewhere to host and monitor the code. Per-method, per-workspace tiers run from Tier 1 (1+/min) to Tier 4 (100+/min); since May 29, 2025, new commercial apps not approved for the Marketplace are capped at 1 request/min and 15 objects per call on conversations.history and conversations.replies.
Register an app, store Slack credentials, refresh tokens and code around the rate limits.
Connect your Slack account once. Caddi holds the connection.
The job doesn't stop at Slack.
An intake, a filing or a client update also runs through email, documents and the other systems your team works in. The Slack API only reaches Slack.
Each extra system is another API, another set of credentials, another integration to own.
One automation runs across every tool the job touches, each through its API.
Someone has to own the code.
API versions change, fields get added and your process moves.
A developer patches and redeploys the integration each time.
The person who does the work updates it by showing or describing the change. Every automation is reviewed before it runs in production, and every run is logged.
What the Slack API gives you
- Type
- Web API (JSON)
- Authentication
- OAuth 2.0 (bot and user bearer tokens)
- Who can get access
- Self-serve for any developer who creates a Slack app; the app must be installed to a workspace to get tokens.
- What it covers
- 200+ methods covering messages, conversations/channels, users, files, reactions, and workspace info.
- Limits
- Per-method, per-workspace tiers run from Tier 1 (1+/min) to Tier 4 (100+/min); since May 29, 2025, new commercial apps not approved for the Marketplace are capped at 1 request/min and 15 objects per call on conversations.history and conversations.replies.
Official docs: docs.slack.dev. Checked September 2026. Vendors change access terms, so confirm with Slack before you build.
When to build the Slack integration in-house
When you have engineers and the integration is your product, or you need one narrow sync between two systems and someone to own it. When the goal is getting Slack work off someone's desk, the build is the slow part, and Caddi does it for you.
What teams usually want the Slack API for
Client Document Batch Uploads
Caddi batch-uploads client documents to the correct matters, applies the right metadata and disclosures, and shares eligible files with clients — with a Slack notification when each batch is done.
Approval flow
Caddi posts an approval request to the right Slack channel, captures the response, and writes the decision back to the source system.
Critical-event notify
When a high-priority event lands in email or the CRM, Caddi posts to the relevant Slack channel with full context.
Daily ops digest
Each morning, Caddi posts the day's open work — overdue tasks, missing docs, aging invoices — to the right Slack channels.
Everything Caddi does with Slack.
Slack API questions
Does Slack have an API?
Yes. Slack has a public web API, authenticated with OAuth 2.0 (bot and user bearer tokens). The official documentation is at https://docs.slack.dev/apis/web-api/.
How do I get access to the Slack API?
Self-serve for any developer who creates a Slack app; the app must be installed to a workspace to get tokens.
Does the Slack API have rate limits?
Per-method, per-workspace tiers run from Tier 1 (1+/min) to Tier 4 (100+/min); since May 29, 2025, new commercial apps not approved for the Marketplace are capped at 1 request/min and 15 objects per call on conversations.history and conversations.replies.
Can I connect Slack to my other tools without writing code against its API?
Yes. With Caddi you show the Slack task once, the way you'd train a new hire, and Caddi builds it as verified code that runs across Slack and the other tools the job touches. Steps that need a person's judgment are handed to Copilot or Claude, and Caddi monitors those too.
Do I need a developer to automate Slack with Caddi?
No. There is no integration code for you to write or maintain. Every automation Caddi builds for Slack is reviewed before it runs in production, and every run is logged.