# Slack Integration Add your Chipp AI to Slack and let team members interact with it directly in channels and DMs. --- Deploy your Chipp AI to Slack so team members can interact with your AI assistant directly in Slack channels and direct messages. ## How It Works Once connected, your AI becomes a Slack bot that: - **Responds to mentions**: `@YourBot how do I reset my password?` - **Uses threads**: Replies in threads to keep channels organized - **Maintains context**: Remembers conversation history within each thread - **Works everywhere**: Public channels, private channels, and DMs ## Key Features | Feature | Description | |---------|-------------| | **Threaded Conversations** | Every response goes in a thread, keeping channels clean | | **Multi-user Support** | Multiple team members can participate in the same thread | | **Context Retention** | Your AI remembers what was discussed earlier in each thread | | **Direct Messages** | Chat privately with the bot in DMs | ## Setting Up Slack Integration The Slack integration requires creating your own Slack app. Chipp provides a pre-configured manifest to make this easy. **1.** Open Slack Configuration in Chipp Go to your Chipp app and open **Launch > Share**. Select the **Deploy** tab and click the **Slack** card. Once the bot is connected, the card shows a green **Connected** badge, and it stays after you refresh the page or reopen the agent. **2.** Create a Slack App 1. Go to [api.slack.com/apps](https://api.slack.com/apps) in a new tab 2. Click **Create New App** 3. Select **From manifest** 4. Choose your Slack workspace **3.** Copy the Manifest from Chipp In the Chipp dialog, you'll see a JSON manifest section. Click **Copy** to copy the entire manifest to your clipboard. This manifest is pre-configured with: - Your app's name and branding - Required bot permissions - Event subscriptions - Webhook URLs pointing to Chipp **4.** Paste and Create the App 1. In Slack's app creation flow, select **JSON** format 2. Delete any existing content and paste your copied manifest 3. Click **Next**, then **Create** 4. In your new Slack app, go to **Settings > Manage Distribution**. Under **Remove Hard Coded Information**, tick all checkboxes, then click **Activate Public Distribution**. Confirm you see the green "Distribution is active" banner. This step is required, or the install fails. In the Chipp dialog, click **I've created my app**. **5.** Get Your App Credentials After creating the app, go to **Basic Information** under **Settings** in the left sidebar. You'll need three values: - **Client ID**: Found in "App Credentials" section - **Client Secret**: Click "Show" to reveal it - **Signing Secret**: Found below the Client Secret **6.** Enter Credentials in Chipp Back in the Chipp dialog, enter all three credentials: - **Client ID**: The app's Client ID - **Client Secret**: The app's Client Secret - **Signing Secret**: The app's Signing Secret The dialog also shows a **Redirect URL**. Make sure it is listed in your Slack app under **OAuth & Permissions > Redirect URLs**. Click **Save & Continue**. **7.** Install to Slack After saving credentials, tick the box confirming you activated public distribution, then click **Install to Slack**. A Slack authorization popup opens: select your workspace and approve the bot permissions. > **Warning:** Only Slack workspace admins can install apps. If you're not an admin, ask your Slack administrator to complete the installation. **8.** Invite to Channels After installation, invite the bot to channels where you want to use it: ``` /invite @YourBotName ``` Replace `YourBotName` with your Chipp app's name. ## Using the Slack Bot ### Basic Usage Mention the bot followed by your question: ``` @YourBot How do I process a return? ``` The bot replies in a thread so the main channel stays clean. ### Following Up Continue the conversation in the same thread - the bot remembers context: ``` @YourBot How do I process a return? └── Bot: To process a return, go to Orders > Returns and... └── You: What if the customer doesn't have a receipt? └── Bot: Without a receipt, you can still process... ``` ### Multiple Users Team members can jump into threads. The bot considers all messages: ``` @YourBot Draft a response to this customer complaint └── Bot: Here's a draft response... └── Alice: Make it more empathetic └── Bob: And mention our 30-day guarantee └── Bot: Here's the revised version incorporating both suggestions... ``` ### Direct Messages DM the bot for private conversations: 1. Find the bot in your Apps or search for it 2. Send a direct message 3. No need to @mention in DMs ## Best Practices ### Channel Organization - **Create dedicated channels** for AI assistance (e.g., #ask-ai, #sales-bot) - **Use private channels** for sensitive topics - **Set channel topics** explaining what the bot can help with ### Prompt Engineering for Slack Optimize your system prompt for team use: ``` You are a helpful assistant for the Acme Corp team in Slack. When responding: - Keep answers concise (Slack conversations should be quick) - Use bullet points for lists - If you need more context, ask clarifying questions - For sensitive topics, suggest moving to a private channel ``` ### Thread Management - **One topic per thread**: Start a new message for different questions - **Don't resurrect old threads**: Context has limits; start fresh for new topics - **Use reactions**: Thumbs up or check to indicate resolved questions ## Managing Your Integration ### Editing Credentials If you need to update your Slack app credentials before you install, click **Edit Credentials** on the install step of the dialog. After the bot is connected, the dialog has no credential editor. To change credentials: 1. Go to **Launch > Share** > **Deploy** and click the **Slack** card 2. Click **Disconnect Slack**, then **Yes, Disconnect** 3. Run the setup again with the new values ### Reinstalling If you need to reinstall to a different workspace or fix permission issues, disconnect as above, then run the setup again and click **Install to Slack**. ## Troubleshooting ### Bot Not Responding 1. Make sure the bot is invited to the channel (`/invite @YourBotName`) 2. Check that you're @mentioning the bot correctly 3. Verify your Chipp app is active and published ### "I don't have permission" Error The bot needs to be installed by a workspace admin. Contact your Slack administrator to install the app. ### Bot Responding Slowly 1. Check your AI model - faster models respond quicker 2. Complex queries with custom actions take longer 3. High workspace usage can cause brief delays ### Installation Failed 1. Verify all three credentials are entered correctly 2. Make sure the Slack app was created with the correct manifest 3. Check that your Slack app is not restricted by workspace policies ## Security & Permissions ### What the Bot Can Access - Messages where it's mentioned - Messages in threads it's participating in - DMs sent directly to the bot - History, threads, and shared files in the channel it is messaged in (through its Slack knowledge tools) - Every channel it has been invited to, if you turn on **Read every channel the bot is in** in the Slack dialog. Anyone who can talk to the agent can then read content from those channels. ### What the Bot Cannot Access - Messages in channels where it's not invited - Private messages between other users ### Settings After Connecting Once connected, the Slack dialog also lets you: - Turn on **Auto-Engage** ("Jump into conversations automatically"), so the bot can reply in its channels without an @mention - Choose which channels the bot replies in, and add private channels by ID - Set **Approval Mentions**: up to 10 email addresses of people the Slack approval card @mentions when the agent proposes a ticket for approval ### Data Handling - Conversations are processed through Chipp's secure infrastructure - Messages are not stored beyond what's needed for context - You can view conversation logs in your Chipp dashboard under **Chats** ## Using with MCP You can manage Slack deployments programmatically using the Chipp MCP Server. ### Available Tools | Tool | Description | |------|-------------| | `list_slack_deployments` | List all Slack workspace connections | | `get_slack_deployment` | Get details about a specific deployment | | `disconnect_slack_deployment` | Remove a Slack connection | ### Example Prompts ``` "Show me all Slack deployments for my support bot" "Which Slack workspaces is my app connected to?" "Disconnect the Slack deployment for my test workspace" ``` ### Workflow: Deployment Overview ``` You: Show me all Slack deployments for my apps AI: [Calls list_slack_deployments] App: Support Bot (ID 123) - Slack Workspace: "Acme Corp" - Status: Connected - Channels: #support, #sales, #general - Last activity: 2 hours ago App: FAQ Bot (ID 456) - No Slack deployments configured ``` > **Note:** MCP server access requires a Studio plan or higher. See the [MCP Setup Guide](/docs/guides/mcp/setup) to get started.