Thomas Scola

Founder / CEO

The Bluefly.io Collective specializes in helping businesses enhance, manage, and migrate their digital platforms to Drupal, offering expert-led and Acquia-certified migrations from any version of Drupal, along with innovative AI solutions—all while maintaining a personalized, client-centric approach. Led by Thomas Scola (@flux423), co-lead of the Maine Drupal User Group since 2007, the Bluefly.io team brings a wealth of Drupal and Acquia expertise to every project. With Thomas’ seven years of experience at Acquia as a subject matter expert (SME) across several key products, including Acquia Cloud, Code Studio, ACSF, and Site Studio, Bluefly.io is uniquely positioned to deliver high-quality solutions tailored to the needs of organizations using Acquia and Drupal platforms. At Bluefly.io, we collaborate closely with businesses to ensure their digital platforms thrive. Whether upgrading from Drupal 7 using Acquia’s AMA, migrating from platforms like WordPress or Adobe Experience Manager, or embarking on a full-scale Drupal Experience Platform (DRXP®) replatforming, we provide expert services that align with the vision and technology of Acquia’s ecosystem. Our focus is on optimizing digital experiences, helping organizations fully leverage the power of Drupal to achieve their goals—without the high overhead associated with larger agencies. Bluefly.io’s DRXP® (Drupal Experience Platform) is a full-service approach to transforming and optimizing digital experiences with Drupal at the core. We specialize in guiding businesses from strategy through implementation, ensuring scalable, flexible, and engaging digital environments that drive growth and success. On a personal note, Thomas calls Maine home, where he lives with his wife, daughter, golden retriever Charlie, and two Maine Coon cats. His eldest daughter works at Acquia as a Customer Success Engineer, and they talk daily. Outside of work, Thomas enjoys fly fishing for salmon and trout across New England, and snowboarding with family and friends during the winter months.

How to set up Slack notifications with Code Studio

Last updated June 10, 2022
2 minute read

Goal

Configuring Slack notifications with Acquia Code Studio

Prerequisites

Access to Code Studio Maintainer role (More on Gitlab Roles)
Slack administrative access to create incoming webhooks

Overview

Today’s DEVops workflow can consist of a number of different tools from code review to visual regression testing. Having an internal communication strategy has become an important part of the process, especially when it comes to notification. Knowing who to inform for what tasks can be a challenge. Acquia Code Studio has notification tools for integrating everything from Jira, Drone, Datadog to Slack, sending notifications and syncing your data to help bridge the gap between some of these tools.

As Slack has become a major player in the team communication space it is positioning itself to be a tool for teams to build their communication strategy around it. Code Studio has a simple integration into Slack that allows your team to customize the push notifications for sending information about the actions in the table below. Each action can be pushed to a separate slack channel or notify individual people. You also can control the branches for which notifications are to be sent and the labels or behaviors to be notified.

Triggers for Slack notifications

The following triggers are available for Slack notifications:

Trigger name	Trigger event
Push	A push to the repository.
Issue	An issue is created, updated, or closed.
Confidential issue	A confidential issue is created, updated, or closed.
Merge request	A merge request is created, updated, or merged.
Note	A comment is added.
Confidential note	A confidential note is added.
Tag push	A new tag is pushed to the repository.
Pipeline	A pipeline status changed.
Wiki page	A wiki page is created or updated.
Deployment	A deployment starts or finishes.
Alert	A new, unique alert is recorded.
Vulnerability	A new, unique vulnerability is recorded.

Below we will show you how to enable some simple notifications from Code Studio to Slack in 3 easy steps.

Add Slack notifications integration
Configure Slack Webhooks
Complete Code Studio Notification Settings
Test your new notifications

Add Slack notifications integration
1. On the top bar, select Menu > Projects and find your project.
2. On the left sidebar, select
  
  Settings > Integrations
  
  .
3. There are a number of integrations you can add, but let's focus on Slack notifications to send notifications about project events to Slack.
Image
Configure Slack Webhooks
1. Next, open a new browser tab and sign in to your Slack team and start a new Incoming WebHooks configuration.
2. Identify the Slack channel where notifications should be sent to by default. Select Add Incoming WebHooks integration to add the configuration.
3. Copy the Webhook URL to use later when you configure GitLab.
Image

* Please note, this is a legacy custom integration - an outdated way for teams to integrate with Slack but find this to be the easiest way to connect Code Studio to Slack at this time. We recommend checking out their replacement: Slack apps and come back later for an update to this article.
Complete Code Studio Notification Settings.
1. On the left sidebar, go back to Settings > Integrations.
2. Select Slack notifications.
3. In the Enable integration section, select the Active checkbox.
4. In the Trigger section, select the checkboxes for each type of GitLab event to send to Slack as a notification. For a full list, see Triggers for Slack notifications. By default, messages are sent to the channel you configured during Slack configuration.
Optional. To send messages to a different channel, multiple channels, or as a direct message:
- To send messages to channels, enter the Slack channel names, separated by commas.
- To send direct messages, use the Member ID found in the user's Slack profile.
- NOTE: Usernames and private channels are not supported.
1. In Webhook, enter the webhook URL you copied in the Slack configuration step.
2. Optional. In Username, enter the username of the Slack bot that sends the notifications.
3. Select the Notify only broken pipelines checkbox to notify only on failures.
4. In the Branches for which notifications are to be sent dropdown, select which types of branches to send notifications for.
5. Leave the Labels to be notified field blank to get all notifications, or add labels that the issue or merge request must have to trigger a notification.
6. Select Test settings to verify your information, and then select Save changes.
Review new Slack Notification

After completing the prior step, you should start to see new notifications in Slack. All you have to do now is test.

Below is an example of an incoming Webhook creating a notification in slack when a new branch is merged has failed.

Image