Connect Slack

Connect Slack to send AI-generated reports, analysis, and alerts straight to your team's Slack channels. This connection only sends messages and never reads your conversations.

Your company's Slack workspace creates and owns this app. You don't install a shared app published by Neuro. For details, see App ownership and responsibilities below.

What you need

An account that can create apps in your Slack workspace — you don't need to be an admin, but depending on your organization's settings, installing the app may require admin approval.
Permission to add connections in your Neuro workspace

First, check whether it's already installed

Someone else on your team may have already installed the Pango Neuro app. Neuro can't tell whether the app already exists in Slack, so check these three things before you create a new one. It saves you from creating a duplicate and going through approval again.

If it's already connected to another Neuro workspace — it appears under Use an existing Slack connection at the top of the connection window. Just select it and you're done. Note that this list only shows workspaces you have access to. If you were invited to specific workspaces as an external member, or your colleague belongs to a different organization, you won't see the connection even if that colleague has already set it up.
If you created the app before — you'll find it through the Check for an existing app link in the connection window (or at api.slack.com/apps). Don't create a new one. Just copy the token from that app's OAuth & Permissions page and skip to Step 2.
If a colleague created it — it won't appear in your app list. Slack only lists apps you created or were added to as a collaborator. Ask that colleague to connect it in Neuro themselves, or to add you under Collaborators on the Slack app page.

Don't send tokens over chat or email. A bot token is an access key in itself. To share a colleague's app, it's safer to be added as a Collaborator and copy the token from your own screen than to have it passed to you.

You can check whether it's actually installed in your workspace in the Manage → Installed apps list in the Slack Marketplace. However, you can't get a token from that screen. Only the app's owner and collaborators can see the token.

Keep it to one app. Sending still works if you create several Pango Neuro apps in the same Slack workspace, but your channels will show multiple bots with the same name, and you'll have to repeat admin approval and permission reviews for each app. It also gets harder to track which app's token is used where.

Step 1 — Create a Slack app

In your Neuro workspace, click the Data sources → Slack card.
Once you've done the checks above, click Create Slack app in the connection window. The Slack app creation screen opens in a new tab with the app name and the three required permissions already filled in. (Check for an existing app next to it takes you to the list of apps you've created.)
Further down the same screen, under Workspace, pick the Slack workspace to install the app in and click Next. (Next only becomes active once you've picked one.)

The Slack app creation screen with the three permissions and workspace selection filled in

On the next screen (Review your app), review the permissions and click Create and Install. If a permission screen appears, allow it. This one step both creates the app and installs it in your workspace.

Don't change the prefilled values. Changing the permission list can make sending fail or give the app broader permissions than intended. If you change the prefilled settings, the resulting app's permission scope is your workspace's responsibility.

Step 2 — Copy the bot token

Open OAuth & Permissions from the left menu of the app page.
Under OAuth Tokens, copy the Bot User OAuth Token using Copy. It's a string that starts with xoxb-.

OAuth & Permissions — Bot User OAuth Token

Further down the same screen, under Bot Token Scopes, you can confirm the three permissions are still in place.

Bot Token Scopes — the three permissions this app has

Treat this token like a password. Don't paste it into chats, issue trackers, or documents. If it leaks, anyone who has it can post messages to your workspace's public channels as the bot. If you suspect a leak, reissue the token (Reinstall) from the Slack app page.

Step 3 — Connect to Neuro

Paste the copied token into the Bot User OAuth Token field in the connection window and click Connect.
Before saving, Neuro checks directly with Slack that the token is valid and has all three permissions. Only tokens that pass are encrypted and saved, and once saved, they're never shown on screen again.

The Slack connection window on Neuro's Data sources page — check existing apps · create an app · enter the token

To add the same Slack workspace to another Neuro workspace, you don't need to create a new app. Just select it under Use an existing Slack connection at the top of the connection window.

(Optional) Upload an app icon

Slack app settings can't add the icon automatically. Download the image with Download app icon in the connection window, then upload it under Basic Information → Display Information → App Icon on the Slack app page to change the bot icon shown in your channels.

Permissions requested

chat:write — Send messages.
chat:write.public — Post to public channels even if the bot hasn't been invited. This saves you from inviting the bot to every channel.
channels:read — View the list of public channels (names and IDs), not their conversations. It's used to match a loosely named channel, like “the marketing room,” to the actual channel.

We don't request permission to read messages. The app has no access to conversation history, DMs, files, or the member list. All it can do is list public channels and send messages.

App ownership and responsibilities

Neuro doesn't publish a shared app on the Slack Marketplace. Instead, your company creates the app in its own workspace, and Neuro uses that app's bot token only to send messages. That keeps granting, revoking, and auditing permissions entirely under your control.

App ownership — Your company's Slack workspace. You manage the app's name, icon, permissions, and deletion.
Permission scope — The three listed above. An app created with modified prefilled settings may have different permissions, and that scope is your workspace's responsibility.
Token storage — Neuro encrypts the token and keeps it for that workspace only. Once saved, it's never shown again anywhere.
Message content — Written by the AI agent based on your instructions. Because sent messages can't be undone, there's an approval step before anything goes out.
Revoking access — Deleting the app on Slack's app management page revokes access immediately. Disconnecting Slack on Neuro's Data sources page also deletes the saved token.
Auditing — Messages the bot sends stay in your Slack, so you can see what went out and when.

If your organization requires admin approval

If your organization requires workspace admin approval to install apps, click Copy approval request in the connection window and paste the text as-is into your approval request. It lists the three permissions requested and states that the app doesn't read conversations, which speeds up security review.

Examples

Once you're connected, just ask in plain language in chat. You don't need the exact channel name; differences in #, spacing, and capitalization are matched for you.

“Summarize this week's ad performance and send it to the #marketing channel.”
“List the campaigns whose conversions dropped sharply from yesterday and let the ops channel know.”
Combine it with scheduled tasks to post a report to your channel automatically every morning.

If more than one channel could match, it asks before sending. For example, if “ops” matches both #ops-team and #ad-ops, it confirms which channel you mean before sending.

Troubleshooting

It says “This token doesn't have the required permissions”

The permission list in your app settings is not the same as the permissions actually granted to the token. If you add permissions without reinstalling, the token keeps its old permissions. Reinstall via OAuth & Permissions → Reinstall to Workspace, then paste the newly issued token again. If you have more than one app, also make sure it's the Pango Neuro app's token.

It says “This isn't a bot token”

You pasted a user token (xoxp-). This connection only sends messages as the bot, so it needs a Bot User OAuth Token (xoxb-).

It says it couldn't find the channel

Channel lookup only covers public channels (excluding archived ones). To post to a private channel, invite the bot by running /invite @Pango Neuro in that channel, then include the channel ID (C…) in your request. To find the channel ID in Slack, right-click the channel name and look at the bottom of the channel details.

Not sure which Slack it will post to

If one Neuro workspace has more than one Slack connection, it asks you instead of picking one on its own. This keeps alerts from going to the wrong workspace.

I want to disconnect

Disconnecting Slack on Neuro's Data sources page deletes the saved token. To remove the app itself, delete it on Slack's app management page. All permissions are revoked as soon as you delete it.

If you run into problems connecting or using it, email pango_plat@pango-gy.com. We'll reply within 1–2 business days.