--- title: Connect errors inbox to third-party services source: https://docs.newrelic.com/docs/errors-inbox/error-external-services --- Bring errors inbox closer to your teams tooling and workflows by connecting it to external services such as Slack, Jira, and CodeStream. ## Connect an inbox to Slack [#slack] When an inbox is connected to Slack, new and resurfaced error groups are sent to a Slack channel moments after they occur. This enables your team to quickly identify any new errors or regressions and resolve them quickly with direct links to the stack trace. To reduce noise, notifications are not sent for [expected errors](https://docs.newrelic.com/docs/errors-inbox/errors-inbox/#expected). To connect an inbox to Slack either follow the steps below or follow along with the video: [Video](https://www.youtube.com/embed/HEbX0dgeGGw) 1. If your Slack workspace does not have the [New Relic app](https://newrelic.slack.com/apps/AP92KQJS3-new-relic?tab=more_info) installed, do that first. 2. Open one of your New Relic error inboxes, select the **Notification Settings** icon (looks like a bell) in the top right corner. 3. Toggle the Slack button to **on** if it is **off**. 4. If no workspaces are available, click the plus button to enable Slack with a one click Slack authentication. 5. Once authenticated, you will be able to select a Workspace and specific Channel to send notifications to. 6. Click **Test** to ensure messages are being sent to the right channel. ## Connect errors inbox to CodeStream To use CodeStream's Open in IDE integration with your APM stack trace errors, you should [associate repositories with your services](https://docs.newrelic.com/docs/codestream/observability/repo-association) and [associate build SHAs or release tags with errors](https://docs.newrelic.com/docs/codestream/observability/error-investigation/#buildsha). Learn more about [commit SHAs](https://git-scm.com/book/en/v2/Git-Tools-Revision-Selection) and [release tags.](https://git-scm.com/book/en/v2/Git-Basics-Tagging) Once set up, you can jump from an error group directly to the offending code in your IDE by clicking the **Open in IDE** button. ## Connect an inbox to Jira [#jira] Connect errors inbox to Jira to easily create tickets for your errors. Jira templates allow you to quickly create a ticket containing error details and links directly to the stack trace and APM for quick access and resolution. ![How to connect an inbox to Jira](https://docs.newrelic.com/images/errors-inbox_screenshot-crop_jira-button-option.webp "How connect an inbox to Jira") We store a link to the the ticket alongside the associated error group for 13 months. If the error occurs again within that period, you can easily access associated tickets. > #### ⚠️ IMPORTANT > > New Relic supports both team-managed and company-managed [Atlassian-Jira projects](https://support.atlassian.com/jira-software-cloud/docs/what-are-team-managed-and-company-managed-projects/). To connect an inbox to Jira either follow the steps below or follow along with the video: [Video](https://www.youtube.com/embed/v2frs2Pyjfw) 1. Click on the Jira integration icon on the far right side of the error group you want to connect to Jira. 2. If you don’t already have a [connection to Jira](https://docs.newrelic.com/docs/alerts-applied-intelligence/notifications/notification-integrations/#set-up-jira) set up in your account, click **Add JIRA Workspace** from the dropdown. Fill in all the fields and click **Test connection** before saving to ensure that your details are correct. 3. Next, set up a template. Templates determine what information will be sent to Jira. Find more information about specific fields [here](https://docs.newrelic.com/docs/alerts-applied-intelligence/notifications/notification-integrations/#configure-jira-message-template). Errors inbox does not currently support two-way communication with Jira, but you can select this option in case it is supported in the future. 4. Once you have a template, click **Send test notification** to preview what the ticket looks like in Jira. If the preview looks good, click **Update message** to save the template. Note that a test notification will create a Jira ticket in your Jira workspace. 5. Now your team can create Jira tickets by clicking the Jira integration icon on the far right side of the error group and selecting a template. Jira settings are associated with the account that owns the error group or entity. If you are using the cross-account errors inbox, you will need to set up a Jira connection multiple times. ## Template variables for Jira integration [#template-variable] Template variables that can be used in the Jira integration template: - errorGroup.id - errorGroup.accountId - errorGroup.sourceEventType - errorGroup.name - errorGroup.message - errorGroup.state - errorGroup.link - errorGroup.firstSeen - errorGroup.lastSeen - errorGroup.count - entity.id - entity.name - entity.link ## Remove a Jira workspace and/or template [#remove-workspace] Here's how to remove a workspace or template: 1. Go to **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Alerts > Destinations**. 2. On the right side of the screen, select **Destinations**. 3. Search for your Jira destination, and at the right side of that row, select the **...** icon, and then click **Delete destination**. ![How to delete a workspace or template](https://docs.newrelic.com/images/errors-inbox_screenshot-crop_delete-source.webp "How to delete a workspace or template")