> For the complete documentation index, see [llms.txt](https://help.pump.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.pump.co/integrations/slack.md). # Slack ## Slack Integration Connect Pumpbot to Slack so your team can interact with spend data directly from Slack. Ask questions in plain English, use slash commands for common workflows, and receive cloud insights in the channels you already use. **Setup time:** \~3–5 minutes *** ### Overview Pumpbot brings your cloud data directly into Slack, allowing your team to ask questions about cloud spend without leaving your workspace. Ask Pumpbot about: * Total cloud spend * Service-level spend breakdowns * Infrastructure Reccomendations * Cost anomalies * Free-form questions about your cloud environment > **Note:** Pumpbot is separate from Slack notifications for budgets and alerts. Connecting Slack for alerts does **not** enable Pumpbot, and connecting Pumpbot does **not** configure alert notifications. *** ### Prerequisites Before connecting Pumpbot, you'll need: * A Pump account with Organization Admin permissions * Permission to install apps in your Slack workspace (or a Slack administrator who can approve the installation) * Browser pop-ups enabled for Pump (required for OAuth authentication) *** ### Setup Instructions 1. Navigate to **Organization Settings → Pumpbot** in Pump. **Direct link:** 2. Click **Connect**. 3. Authorize Pumpbot in the Slack OAuth window. 4. In Slack, invite Pumpbot to each channel where you'd like to use it: ``` /invite @pump ``` 5. Return to Pump and, under **Add a Channel**, select each Slack channel and click **Add**. Pumpbot only responds in channels that have been added and marked as active. ***
### Permissions Pump Requests | Permission | Why Pump Needs It | | --------------------------------------- | ----------------------------------------------------------------------------- | | **Send messages** | Respond to your questions and share cloud spend and anomaly insights in Slack | | **Upload files** | Attach spend charts and visualizations when available | | **View public & private channels** | Display channels Pumpbot has joined so they can be enabled in Pump | | **View messages in channels & threads** | Understand thread context for follow-up questions | | **Receive @mentions** | Respond when Pumpbot is mentioned in a Slack channel | | **Slash commands** | Enable `/pumpbot` commands and related workflows | *** ### Features #### Ask Questions in Plain English Pumpbot lets your team query cloud spend data directly from Slack. Simply ask questions such as: * "Why did AWS spend increase yesterday?" * "Which services had anomalies this week?" * "What are some infrastructure recommendations to reduce my costs?" * "What's our total cloud spend this month?" Pumpbot understands follow-up questions, allowing you to drill deeper into your cloud data without switching applications. *** #### Use Slash Commands Pumpbot supports slash commands for common cloud management workflows. Use commands such as: * `/pumpbot` * Spend * Service * Anomaly * Glossary Commands support common reporting periods like **7d**, **30d**, and **MTD**. *** #### Organization Glossary Teach Pumpbot your company's internal terminology by defining a glossary. Once a term is added, Pumpbot remembers its meaning and automatically applies it to future conversations, making responses more accurate and tailored to your organization. *** #### Threaded Conversations Continue conversations naturally inside Slack threads. Pumpbot remembers the context of previous questions, allowing your team to ask follow-up questions without repeating information. Some responses also include charts and visualizations to help explain trends. *** ### What You Can Do Pumpbot supports a wide range of cloud operations directly from Slack, including: * Ask cloud cost questions in natural language * Understand infrasutr * View total spend and service-level breakdowns * Investigate cloud cost anomalies * Receive charts and visualizations when available * Continue conversations with follow-up questions in Slack threads * Use slash commands for common workflows * Customize Pumpbot with your organization's glossary *** ### Security & Access Pump uses Slack only to send and receive messages and upload files. Your cloud cost and infrastructure data always comes from your Pump account—not from Slack. OAuth tokens are encrypted at rest. To disconnect Pumpbot: 1. Navigate to **Organization Settings → Pumpbot**. 2. Click **Disconnect**. You can also uninstall the Pump app directly from your Slack workspace settings at any time. *** ### Supported Workflows The Slack integration supports: * Asking cloud questions in natural language * Multi-turn conversations with follow-up questions * Slash commands for common workflows * Organization glossary customization * Threaded Slack conversations * Secure Slack workspace authentication * Sharing charts and cloud insights directly in Slack *** ### FAQ #### My Slack channel doesn't appear in Pump. Invite Pumpbot into the channel first using: ``` /invite @pump ``` Then refresh the channel list in Pump. #### The connection seems stuck. Some Slack workspaces require administrator approval before new apps can be installed. Ask your Slack administrator to approve Pumpbot, then return to Pump and click **Connect** again. #### I already connected Slack for alerts. Why doesn't Pumpbot work? Slack Alerts and Pumpbot are separate integrations. To use Pumpbot, connect it under **Organization Settings → Pumpbot** and add the channels where you'd like it to respond. *** --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://help.pump.co/integrations/slack.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.