gitlab-org--gitlab-foss/doc/integration/slack.md

# Slack integration

## On Slack

To enable Slack integration you must create an Incoming WebHooks integration on Slack;

1.  [Sign in to Slack](https://slack.com/signin)

1.  Select **Configure Integrations** from the dropdown next to your team name.

1.  Select the **All Services** tab

1.  Click **Add** next to Incoming Webhooks

1.  Pick Incoming WebHooks

1.  Choose the channel name you want to send notifications to

1.  Click **Add Incoming WebHooks Integration**
    - Optional step; You can change bot's name and avatar by clicking modifying the bot name or avatar under **Integration Settings**.

1. Copy the **Webhook URL**, we'll need this later for GitLab.


## On GitLab

After Slack is ready we need to setup GitLab. Here are the steps to achieve this.

1.  Sign in to GitLab

1.  Pick the repository you want.

1.  Navigate to Settings -> Services -> Slack

1. Pick the triggers you want to activate

1.  Fill in your Slack details
    - Webhook: Paste the Webhook URL from the step above
    - Username: Fill this in if you want to change the username of the bot
    - Channel: Fill this in if you want to change the channel where the messages will be posted
    - Mark it as active
    
1. Save your settings

Have fun :)

*P.S. You can set "branch,pushed,Compare changes" as highlight words on your Slack profile settings, so that you can be aware of new commits when somebody pushes them.*
Update docs to markdown style guide. 2014-04-24 18:48:22 -04:00			`# Slack integration`
Slack documentation added 2014-04-13 20:26:48 -04:00
Update docs to markdown style guide. 2014-04-24 18:48:22 -04:00			`## On Slack`
Slack documentation added 2014-04-13 20:26:48 -04:00
			`To enable Slack integration you must create an Incoming WebHooks integration on Slack;`

update slack-notifier to 1.0.0, use raw webhook_url per slack recommendation per changes with slack, they’re now using “static” web hook urls that describe the team & service with IDs that don’t change if the team or service name change. their recommendation is to use the raw webhook_url instead of building it out of components to allow more flexibility this should also prevent issues cropping up with mistakes in how the urls are parsed 2014-10-23 14:47:28 -04:00			`1. [Sign in to Slack](https://slack.com/signin)`

			`1. Select Configure Integrations from the dropdown next to your team name.`

			`1. Select the All Services tab`

			`1. Click Add next to Incoming Webhooks`

Update docs to markdown style guide. 2014-04-24 18:48:22 -04:00			`1. Pick Incoming WebHooks`
Slack documentation added 2014-04-13 20:26:48 -04:00
update slack-notifier to 1.0.0, use raw webhook_url per slack recommendation per changes with slack, they’re now using “static” web hook urls that describe the team & service with IDs that don’t change if the team or service name change. their recommendation is to use the raw webhook_url instead of building it out of components to allow more flexibility this should also prevent issues cropping up with mistakes in how the urls are parsed 2014-10-23 14:47:28 -04:00			`1. Choose the channel name you want to send notifications to`

Updated the Slack documentation 2015-04-21 13:25:37 -04:00			`1. Click Add Incoming WebHooks Integration`
update slack-notifier to 1.0.0, use raw webhook_url per slack recommendation per changes with slack, they’re now using “static” web hook urls that describe the team & service with IDs that don’t change if the team or service name change. their recommendation is to use the raw webhook_url instead of building it out of components to allow more flexibility this should also prevent issues cropping up with mistakes in how the urls are parsed 2014-10-23 14:47:28 -04:00			`- Optional step; You can change bot's name and avatar by clicking modifying the bot name or avatar under Integration Settings.`

			`1. Copy the Webhook URL, we'll need this later for GitLab.`

Slack documentation added 2014-04-13 20:26:48 -04:00
Update docs to markdown style guide. 2014-04-24 18:48:22 -04:00			`## On GitLab`
Slack documentation added 2014-04-13 20:26:48 -04:00
			`After Slack is ready we need to setup GitLab. Here are the steps to achieve this.`

Update docs to markdown style guide. 2014-04-24 18:48:22 -04:00			`1. Sign in to GitLab`

			`1. Pick the repository you want.`

			`1. Navigate to Settings -> Services -> Slack`

Updated the Slack documentation 2015-04-21 13:25:37 -04:00			`1. Pick the triggers you want to activate`
Slack documentation added 2014-04-13 20:26:48 -04:00
Updated the Slack documentation 2015-04-21 13:25:37 -04:00			`1. Fill in your Slack details`
			`- Webhook: Paste the Webhook URL from the step above`
			`- Username: Fill this in if you want to change the username of the bot`
			`- Channel: Fill this in if you want to change the channel where the messages will be posted`
update slack-notifier to 1.0.0, use raw webhook_url per slack recommendation per changes with slack, they’re now using “static” web hook urls that describe the team & service with IDs that don’t change if the team or service name change. their recommendation is to use the raw webhook_url instead of building it out of components to allow more flexibility this should also prevent issues cropping up with mistakes in how the urls are parsed 2014-10-23 14:47:28 -04:00			`- Mark it as active`
Updated the Slack documentation 2015-04-21 13:25:37 -04:00
			`1. Save your settings`
Slack documentation added 2014-04-13 20:26:48 -04:00
			`Have fun :)`

Update docs to markdown style guide. 2014-04-24 18:48:22 -04:00			`P.S. You can set "branch,pushed,Compare changes" as highlight words on your Slack profile settings, so that you can be aware of new commits when somebody pushes them.`