Slack Integration

Push updates about your queue status to Slack to keep your team informed.

Trunk Merge Queue integrates with Slack to send real-time notifications about queue activity and pull request state changes to a designated channel or directly to you as personal notifications.

After you have Merge Queue set up and running in your repository, you can configure Slack notifications to receive alerts for various queue events.

Channel Notifications

Send merge queue updates to a shared team Slack channel to keep everyone informed about queue activity.

Enable Merge Queue Notifications

After you have Merge set up and running in your repository, you can set up your integration with Slack under Merge Queue tab > repository > Settings > Connect with Slack.

1. Navigate to Settings > Repositories > [your repository] > Merge Queue
2. Find the Connect with Slack setting and click Connect to install the Trunk Slack application
3. Authorize the app to post to your desired channel
4. You’ll be redirected back to your settings page once authorization is complete

Configuring Channel Notification Preferences

After connecting to a Slack channel, you can customize which notifications you want to receive. By default, all Merge Queue notifications are enabled.

You can toggle individual notification types on or off. See Available Notification Topics below for descriptions of each notification type.

Tip: Want to receive these notifications as personal DMs instead of in a shared channel? Check out our Personal Slack Notifications setup guide.

Personal Slack Notifications

Get direct messages in Slack about your PRs in the merge queue, keeping you informed without adding noise to team channels.

Personal Slack notifications allow you to receive personalized Slack DMs when your PRs are queued, start testing, pass tests, get merged, or encounter issues. This keeps you up-to-date on the progress of your code through the merge queue without needing to check the web UI or monitor shared channels.

Setting up Personal Notifications

To receive personal Slack notifications, you’ll need to connect both your GitHub and Slack accounts to Trunk and configure your notification preferences.

Note: If your organization isn’t already using merge queue Slack notifications to a shared channel, a Slack workspace admin may need to approve the Trunk Slack app before you can connect your personal account. See Enable Merge Queue Notifications for details on setting up the initial Slack integration.

Steps to Enable Personal Notifications

1. Navigate to User Settings

   • Go to User Settings > Notifications in the Trunk web app
   • These settings are specific to you, so you can customize them however you prefer

2. Connect GitHub Account

   • Click Connect GitHub to begin the OAuth flow
   • This verifies that you own your GitHub account and allows Trunk to link your PRs to your user profile

3. Connect Slack Account

   • Click Connect to Slack to authorize the Trunk Slack app to send you direct messages

   Important: If your organization hasn’t already installed the Trunk Slack app for channel notifications, a Slack workspace admin may need to approve the app before you can receive personal notifications.

4. Configure Notification Preferences

   • Enable the specific notifications you want to receive via Slack DM
   • See Available Personal Notification Topics below for descriptions of each notification type

5. Manage Connections

   • You can disconnect your GitHub or Slack accounts at any time by clicking the respective Disconnect buttons in User Settings

Tip: Want to receive these same notifications in a shared Slack channel instead? Check out our team Channel Slack Notifications setup guide.

Slack App Home Dashboard

The Trunk Slack app’s Home tab provides a personal merge queue dashboard directly in Slack. Open the Trunk app in Slack and click the Home tab to see an overview of your merge queue activity.

What you’ll see

The Home tab displays the following sections:

• Account connection status — Shows whether your Trunk and GitHub accounts are linked. If GitHub is not connected, a warning explains that most notifications require it, with a button to start the GitHub OAuth flow.
• Not Ready PRs — PRs you’ve submitted to the queue that are waiting for prerequisites (e.g., passing required checks, no merge conflicts) before entering active testing. Grouped by queue.
• PRs in Queue — Your PRs that are currently pending, testing, or have passed tests, with status indicators. Grouped by queue.
• Recently Merged PRs — Up to 5 of your most recently merged PRs with merge dates. Grouped by queue.
• Failed PRs — Your PRs that failed in the queue. Grouped by queue.
• Notification Preferences — Toggle buttons for each notification topic. You can enable or disable individual notifications directly from Slack without visiting the web UI.

Each PR entry shows the PR title, number, a link to the Trunk dashboard, and a link to the GitHub PR. All data is scoped to your PRs via your linked GitHub account.

Linking your account

1. Open the Trunk app in Slack and go to the Home tab
2. Click Link Account to connect your Trunk account
3. Click Connect GitHub to link your GitHub account (required for PR tracking and most notifications)

Managing notification preferences

You can toggle notification topics on or off directly from the Home tab — no need to visit the Trunk web UI. Changes take effect immediately. The available topics are the same as those listed in Available Notification Topics.

Use the Refresh button at the top of the Home tab to update the view with the latest queue data.

Frequently Asked Questions

Available Notification Topics

Both channel and personal Slack notifications use the same notification topics. You can customize which events trigger notifications based on your preferences.

Notification	Description
Merge is updated	The merge queue’s configuration was changed. This covers anything that changes how the queue acts, including: pausing or draining the queue, changing its mode, changing testing concurrency, and so on.
Pull request is submitted for merging	A pull request has been submitted to the queue
Pull request is admitted to the queue and is waiting to be tested	A pull request has been admitted to the queue and will begin testing as soon as it can
Pull request is testing	Trunk merge has begun testing a pull request
Pull request has passed tests	Testing has passed on a pull request. The PR will be merged when it reached the top of the queue
Pull request is merged	A pull request submitted to the queue has successfully been merged into its target branch
Pull request fails	Testing failed on a pull request and it was removed from the queue or Trunk failed to merge the PR into its target branch
Pull request is canceled	A pull request has been canceled, either manually or due to it reaching a configured testing timeout
Pull request failed and is waiting for PRs in front of it to finish testing	A pull request failed testing, but the pull request is currently waiting before being kicked. This can happen for one of two reasons: 1. The pull request is not at the head of the queue, so it is waiting to determine if it is the source of the failure or if a PR it depends on is 2. Pending Failure Depth is enabled and the PR is waiting for other PRs below it to finish testing