Slack
45 operations9 webhooks
Team messaging platform for channels, direct messages, files, and workplace collaboration.
Supported operations
- Conversations Get TeamsRead-only
Get all the workspaces a given channel is connected to
- Conversations SearchRead-only
Search for channels on an Enterprise organization
- Conversations Set TeamsWrite
Set the workspaces in an Enterprise grid org that connect to a channel
- List TeamsRead-only
List all teams on an Enterprise organization
Supported triggers
- Challenge
Slack URL verification challenge — respond to confirm the webhook endpoint
FAQ
Install corsair and @corsair-dev/slack, add the Slack plugin, and connect a workspace with OAuth or an API key. Then call methods like corsair.slack.api.messages.post() from your app. Corsair stores tokens, verifies webhooks, and keeps each tenant on their own workspace.
Yes. Slack needs a bot token or OAuth with scopes that match what you automate. Use chat:write to post and channels:read to list channels. Create a Slack app, add the scopes, then paste credentials into Corsair or connect through managed OAuth in Hub.
Yes. One Corsair client can hit Slack, GitHub, Notion, Stripe, and the rest. Post when an issue opens, push a Notion update to a channel, ping the team after a payment. Same tenant context across plugins, plain TypeScript.
Incident alerts, onboarding pings, standup summaries, approval bots, agents that read channel history before replying. Teams also wire Slack webhooks for new messages, files, or channel changes into other systems.
The SDK is open source. Self-host and you pay Corsair nothing for the integration layer. Hub bills for hosted auth and execution, not per Slack API call. Hub has a generous free tier. For hobby projects you can probably run the whole thing on free. Paid plans start to matter with more tenants or heavier traffic.
We maintain @corsair-dev/slack in the open repo. When Slack ships API changes, upgrade the package. Your call sites stay typed. You should not need to rewrite the integration layer each time.
No. Corsair does not read your Slack messages or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store Slack data on your behalf.