Slack Bots

Where

Dashboard sidebar → Settings → Connectors → Slack Bots.

What it does

A Slack bot is a Slack App of your own that represents one employee. Once connected, your team sends a direct message to that app in Slack, and the employee answers there.

One app per employee. The employee appears in Slack under its own name and its own avatar, not under a shared "Geta.Team" identity. Add a second bot for a second employee.

This is not Slack Impersonation. A bot posts as itself. Impersonation sends messages as a real connected Slack user. They are two separate connectors, configured separately.

The row shows how many bots are connected (0 connected until you add one). Expanding it gives you the How to Create a Slack Bot button, which repeats these instructions inside the product, and the Add New Slack Bot form:

Before you start

You need a Slack workspace where you are allowed to install apps. On many workspaces this means being an admin, or having an admin approve the app once it is created.

Keep the Geta.Team Connectors panel open in a second tab: you will come back to it at step 6, and the event URL you need at step 3 is displayed there.

Create the bot, step by step

1. Create a Slack App

1. Go to api.slack.com/apps.
2. Click Create New App.
3. Choose From scratch.
4. Enter an App Name. Name it after the employee, for example Brooke - Geta.Team, because this is what your team will see in Slack.
5. Select your workspace and click Create App.

2. Add Bot Token Scopes

1. Go to OAuth & Permissions in the left sidebar.
2. Scroll to Scopes → Bot Token Scopes.
3. Add these seven scopes:

chat:write
files:read
files:write
im:history
im:read
im:write
users:read

chat:write lets the employee answer, the im: scopes let it receive direct messages, and the files: scopes let it send and read attachments.

3. Enable Event Subscriptions

This is what makes the bot receive direct messages. Without it, the bot can only speak when spoken to through the platform.

1. Go to Event Subscriptions.
2. Toggle Enable Events to On.
3. Set the Request URL to your instance's Slack events endpoint:

https://YOUR-INSTANCE/api/slack-events

4. Wait for Slack to verify the URL.
5. Under Subscribe to bot events, add message.im.
6. Click Save Changes.

4. Enable App Home

Required for direct messages.

1. Go to App Home in the left sidebar.
2. In the Show Tabs section, enable the Messages Tab.
3. Check Allow users to send Slash commands and messages from the messages tab.

Skip this and your team will see "Sending messages to this app has been disabled" when they try to write to the bot.

5. Install the app and collect the credentials

1. Go back to OAuth & Permissions.
2. Click Install to Workspace and authorize the app.
3. Copy the Bot User OAuth Token. It starts with xoxb-.
4. Go to Basic Information and copy the Signing Secret.

6. Add the bot in Geta.Team

1. Back in Settings → Connectors → Slack Bots, click + Add Bot.
2. Enter the Bot Name, usually the employee's name.
3. Paste the Bot Token and the Signing Secret.
4. Click Add Bot.
5. Assign the bot to an employee. A bot that is not assigned belongs to nobody and answers nobody.

7. Customise the bot's appearance (optional)

1. In Slack, go to Basic Information → Display Information.
2. Set the App name, the Short description and the Long description.
3. Upload an App icon. Use the employee's avatar, so the person in Slack sees the face they see in the platform.
4. Click Save Changes.

8. Keep the bot always online (optional)

1. Go to App Home.
2. Check Always Show My Bot as Online.

The bot then shows as online 24/7 in Slack, so nobody wonders whether it is listening.

Troubleshooting

"Sending messages to this app has been disabled." Step 4 was skipped. Enable the Messages Tab in App Home and allow users to send messages from it.

The bot never answers a direct message. Check step 3: Enable Events must be on, the Request URL must be verified by Slack, and message.im must be listed under Subscribe to bot events. A Request URL that points to another instance verifies fine and delivers nothing.

Slack rejects the token when you click Add Bot. The token must be the Bot User OAuth Token, starting with xoxb-. A token starting with xoxp- is a user token and belongs to Slack Impersonation, not here.

You added a scope and the bot stopped working. Slack does not apply new scopes to an already installed app. Go back to OAuth & Permissions and click Install to Workspace again, then use the new token.

The right employee does not answer. The bot exists but is assigned to another employee, or to none. Check the assignment in the connector row.

What breaks

The Slack app belongs to your Slack workspace, not to Geta.Team. If someone deletes it there, or if the token is revoked, the employee goes silent with no warning on the platform side. Re-issue the token and update the bot.