Slack

Connecting Slack lets agents post messages, read channel history, list channels, and manage files and reactions.

Create a Slack app

Create the app

Go to api.slack.com/apps → Create New App → From scratch. Name it and pick the workspace to develop in.

Add the redirect URL

Under OAuth & Permissions → Redirect URLs, add your callback:

https://api.yourdomain.com/connect/state

This exact value goes in SLACK_REDIRECT_URI. Slack requires HTTPS — for local development use a tunnel such as ngrok rather than localhost.

Copy credentials

From Basic Information → App Credentials, copy the Client ID and Client Secret.

Configure GoConva

SLACK_CLIENT_ID=your-client-id
SLACK_CLIENT_SECRET=your-client-secret
SLACK_REDIRECT_URI=https://api.yourdomain.com/connect/state

Restart the API after editing .env.

Scopes requested

GoConva requests these bot scopes. You do not add them manually — they are sent with the authorization request — but your Slack app must not restrict them.

Area	Scopes
Channels	`channels:read`, `channels:write`, `channels:history`, `channels:manage`
Private channels	`groups:read`, `groups:write`, `groups:history`
Messaging	`chat:write`, `chat:write.public`
Files	`files:read`, `files:write`
Reactions	`reactions:read`, `reactions:write`
Stars	`stars:read`, `stars:write`
Users	`users:read`, `users.profile:read`, `users.profile:write`
User groups	`usergroups:read`, `usergroups:write`
Search	`search:read`
Direct messages	`im:history`, `im:read`, `im:write`
Group DMs	`mpim:history`, `mpim:read`, `mpim:write`

This is a broad set — it includes reading message history across public and private channels. Review it against your organization’s data policy before authorizing, and connect from an account whose access matches what the workspace should collectively have.

Connect

In your workspace, go to Settings → Integrations, find Slack, and click Connect. Slack shows its consent screen listing the permissions above; on approval you land back in GoConva with the connection ready.

Verify

Use the Test action on the Slack connection. To confirm channel access, add a Slack step to a workflow — the channel picker lists what the connection can reach.

Troubleshooting

Symptom	Fix
`bad_redirect_uri`	`SLACK_REDIRECT_URI` and the Slack app’s Redirect URL differ. They must match exactly, including trailing slash.
Bot posts fail in a channel	The bot must be invited to private channels. `chat:write.public` covers public ones only.
`missing_scope`	The app was authorized before a scope was added. Reconnect to re-consent.
`invalid_client_id`	Credentials came from a different Slack app, or the app was deleted.

Slack apps distributed beyond your own workspace need Public Distribution enabled and Slack’s review. For internal use, a single-workspace app is enough.

Getting started

Integrations

Open source

Create a Slack app

Configure GoConva

Scopes requested

Connect

Verify

Troubleshooting

​Create a Slack app

​Configure GoConva

​Scopes requested

​Connect

​Verify

​Troubleshooting

Create a Slack app

Configure GoConva

Scopes requested

Connect

Verify

Troubleshooting