--- title: Autopilot Slack integration source: https://docs.newrelic.com/docs/agentic-ai/autopilot/connect-to-slack --- When an alert triggers, you often jump between Slack, where your team is already talking, and the New Relic UI to investigate. That context switching slows your response. Connect Autopilot to Slack so your team can investigate right in the thread and receive the same outputs from Autopilot in your Slack workflows. Mention the New Relic app (for example, `@New Relic`) with a question, and it replies using your New Relic permissions. ## What you can do [#what-you-can-do] In any channel where you've invited the app, mention it (for example, `@New Relic`). Autopilot can: - **Triage alerts**: Find out why an alert triggered, what's affected, and what correlates. - **Check entity health**: Get the current status of any monitored service. - **Analyze changes**: Find out whether a recent deployment caused a regression. - **Run multi-turn investigations**: Ask follow-up questions in the same thread to dig deeper. - **Retrieve investigation status, summary, and key details**: Retrieve status and summary information in addition to details, such as severity, root cause, resolution, detection, and the assigned incident commander. Autopilot replies in the same thread and accesses only the data your New Relic permissions allow. ## Prerequisites [#prerequisites] Before you begin, make sure you have: - **A configured Autopilot**: An active agent with accounts and permissions set up. Refer to [Set up Autopilot](https://docs.newrelic.com/docs/agentic-ai/autopilot/setup). - **Slack admin access**: Admin permissions in your Slack workspace to approve the New Relic app. - **Workflow FCM**: To invoke Autopilot from Slack, you must have Workflow FCM enabled in addition to Autopilot FCM. - **Permission to create a user API key**: To use Autopilot in Slack, your role must allow creating user API keys for your Workflow Automation accounts. ## Set up the Slack connection [#setup] ### Connect your Slack workspace (admin) [#connect-slack] An [Organization manager](https://docs.newrelic.com/docs/accounts/accounts-billing/new-relic-one-user-management/user-management-concepts/#role-scopes) connects the workspace during Autopilot configuration: 1. Go to **[one.newrelic.com](https://one.newrelic.com)**. 2. In the upper right, select **Ask AI**, then select the **Configure** tab (gear icon). 3. Under **Agents**, select your Autopilot. 4. In the **Slack (optional)** section, click **Connect**. 5. On the Slack authorization screen: 1. Select the workspace you want to connect. 2. Review the requested default permissions and click **Allow**. 6. Verify that a green **Connected** badge appears. 7. Click **Update agent**. > #### ⚠️ IMPORTANT > > The workspace connection allows users to link their Slack identity so that the Autopilot can respond in the workspace. The Autopilot will only respond in the [Slack workspace](https://slack.com/help/categories/200122103-Workspace-administration) it is connected to. > #### 💡 TIP > > To stop Autopilot from responding in the workspace, from this page you can disconnect the workspace at any time. ### Invite the New Relic app to a channel [#invite-to-channel] Any workspace member can invite the New Relic app to a channel. In the channel, mention the New Relic app (for example, `@New Relic`). If the app isn't already there, Slack prompts you to add it. You can also add it from the integration tab of the Slack channel. ### Link your identity (first time only) [#link-identity] If you are mentioning the New Relic app in a thread for the first time before your identity is linked, you get a private message prompting you to connect your New Relic account. Click **Connect** and log in with your New Relic credentials to link your identity. The **Connect** and **Authenticate** links expire after 10 minutes. If a link expires, mention the New Relic app again. > #### ⚠️ IMPORTANT > > This is a one-time step per workspace. After you link your identity, you can mention the New Relic app in any channel of that workspace without needing to connect again. ## Use Autopilot in Slack [#use-in-slack] After setup, use Autopilot from any channel where you've invited the app, or from the app's Home tab. ### Check your connection from the Home tab [#home-tab] To open its Home tab and check your connection status, in your Slack sidebar, click the New Relic app: - **Not connected**: A welcome screen with a **Connect to New Relic** button to link your account. - **Connection expired**: A prompt with an **Authenticate** button to re-authenticate. - **Error**: A "Something went wrong" message with recovery steps. When you're connected, the Home tab also shows your currently linked New Relic organization, a **Switch orgs** option, and a **Disconnect** option. ### Ask a question [#ask-a-question] Mention the New Relic app (for example, `@New Relic`) with your question in any thread: ``` @New Relic why is checkout-service alerting? @New Relic what deployed on payment-gateway in the last hour? @New Relic investigate this alert ``` ### Investigate alerts in context [#investigate-in-context] When New Relic posts an alert notification to a channel, reply in that thread. Autopilot reads the notification to identify the entity and issue, so you don't need to name them. ### Ask follow-up questions [#follow-up-questions] Continue in the same thread. Autopilot reads earlier messages to keep context: ``` @New Relic what's causing this? [Autopilot replies with a root cause analysis] @New Relic what was the deployment before that? [Autopilot replies with more context] ``` ### Switch New Relic organizations [#switch-orgs] If you have access to multiple New Relic organizations, switch to the one your Slack identity uses without disconnecting: 1. Open the New Relic app's Home tab in Slack. 2. Click **Switch orgs**. 3. On the New Relic login page, sign in with the account for the organization you want. After you authenticate, the Home tab shows the newly linked organization, and future mentions in this workspace query it. > #### ⚠️ IMPORTANT > > Your Slack identity links to only one New Relic organization at a time per workspace. Switching replaces the previous New Relic organization mapping. ### Pause your access to Autopilot [#pause-access] If you want to stop your own direct, interactive access to Autopilot without disconnecting the whole workspace: 1. In your Slack sidebar, click the New Relic app to open its Home tab. 2. Click **Disconnect**. Your interactive access to Autopilot stops immediately. You still receive notifications in the workspace, including automated updates from Autopilot. If you want to remove the integration for the entire organization instead, refer to [Remove the Slack integration](#remove-integration). **How Autopilot uses Slack data** When you mention the New Relic app, it reads the thread that it is mentioned in for up to 48 hours of history in order to understand the thread's context. > #### ⚠️ CAUTION > > Autopilot reads every message in the thread where it's invoked. Don't share passwords, API keys, tokens, credentials, or other sensitive information in those threads. If credentials were shared, mention the New Relic app in a new thread instead so that information is not used. Autopilot does the following: - Reads messages in the thread where it's mentioned. - Extracts alert and entity details from New Relic notification URLs in the thread. - Responds using New Relic insights based on your New Relic permissions. - Posts responses visible to all channel members. > #### ⚠️ IMPORTANT > > Responses are visible to everyone in the channel, including people without New Relic access. Autopilot queries data with your permissions, but its replies are public to the channel. ### Data isolation [#data-isolation] Each request from Slack is isolated to the following: - **Credentials per request**: Each invocation of Autopilot uses the invoking user's token. - **No credential storage**: Credentials pass through request headers only. They aren't stored or persisted. - **Thread specific**: Requests are scoped to the thread where the Autopilot is invoked. - **No persistent Slack data**: Autopilot holds thread messages temporarily in memory for a single request only. **NR Connect: Identity linking and authentication** NR Connect is the authentication bridge that maps your Slack user ID to your New Relic account. Before Autopilot responds, NR Connect verifies that your Slack user ID is linked to a New Relic account (user mapping) and that your authentication session is active (valid token). ### How validation works [#how-validation-works] Each time you mention the New Relic app, the system checks: 1. **Workspace authorization**: Whether an admin has connected this workspace to a New Relic organization. 2. **User mapping**: Whether your Slack user ID is linked to a New Relic account. 3. **Token validation**: Whether your authentication session is active and unexpired. If all checks pass, Autopilot processes your request and replies in the thread. If mapping or token fails, you get a private message with a **Connect** button. Sign in, then mention the New Relic app again. For specific errors, refer to [Troubleshoot Autopilot Slack connection issues](https://docs.newrelic.com/docs/agentic-ai/sre-agent/troubleshoot). ### Authentication checks by request origin [#slack-vs-ui] Requests from Slack originate outside the New Relic UI, so the system verifies both your identity mapping and your token. From within the New Relic UI, the system trusts your active web session and checks only the mapping. | Origin | Checks performed | On failure | | ---------------------------------------- | ------------------------------- | ------------------------------------------------------------------------------- | | From Slack (**@New Relic** mention) | User mapping and token validity | Ephemeral error with a **Connect** button that redirects to the New Relic login | | From the New Relic UI (**Ask AI** panel) | User mapping only | UI error: "Account not connected" | **Current limitations** - **Text responses only**: Charts, images, and interactive buttons aren't available or supported. - **Thread-scoped context**: Autopilot reads only the thread where it's mentioned, not the full Slack channel. - **No action execution**: Autopilot investigates and recommends but doesn't run remediation actions, such as rollbacks or restarts. - **No external incident data**: Autopilot doesn't access ServiceNow, PagerDuty, or other external incident data. - **Slack only**: Microsoft Teams isn't supported yet. ## Remove the Slack integration [#remove-integration] > #### ⚠️ IMPORTANT > > Uninstalling the New Relic app from your Slack workspace removes it entirely. It stops Autopilot notifications along with all other Slack-based alert notifications for your organization. If you only want to pause your own access instead, refer to [Pause your access to Autopilot](#pause-access). A Slack workspace administrator can fully remove the New Relic integration using Slack's standard app removal flow. Refer to [Slack's documentation on removing apps](https://slack.com/help/articles/360003125231). After uninstall, New Relic automatically marks the corresponding Slack destination as **UNINSTALLED** and sets it to inactive. You don't need to manually delete it. ## Next steps [#next-steps] [Set up Autopilot](https://docs.newrelic.com/docs/agentic-ai/autopilot/setup) Configure prerequisites, permissions, and alert integration before connecting Slack. [Use Autopilot](https://docs.newrelic.com/docs/agentic-ai/autopilot/use-autopilot) Learn usage tips and best practices for incident analysis and investigation. [Autopilot overview](https://docs.newrelic.com/docs/agentic-ai/autopilot/overview) Learn more about Autopilot's capabilities and billing. [Troubleshoot Autopilot Slack connection issues](https://docs.newrelic.com/docs/agentic-ai/sre-agent/troubleshoot) Find fixes for common Slack connection and authentication errors.