gitlab-org--gitlab-foss/doc/user/project/integrations/slack_slash_commands.md

# Slack slash commands **(CORE ONLY)**

> Introduced in GitLab 8.15.

Slack slash commands allow you to control GitLab and view content right inside
Slack, without having to leave it. This requires configurations in both Slack and GitLab.

GitLab can also send events (e.g., `issue created`) to Slack as notifications.
This is the separately configured [Slack Notifications Service](slack.md).

NOTE: **Note:**
For GitLab.com, use the [Slack app](gitlab_slack_application.md) instead.

## Configuration

1. Slack slash commands are scoped to a project. Navigate to the [Integrations page](overview.md#accessing-integrations) in your project's settings, i.e. **Project > Settings > Integrations**.
1. Select the **Slack slash commands** integration to configure it. This page contains required information to complete the configuration in Slack. Leave this browser tab open.
1. Open a new browser tab and sign in to your Slack team. [Start a new Slash Commands integration](https://my.slack.com/services/new/slash-commands).
1. Enter a trigger term. We suggest you use the project name. Click **Add Slash Command Integration**.
1. Complete the rest of the fields in the Slack configuration page using information from the GitLab browser tab. In particular, the URL needs to be copied and pasted. Click **Save Integration** to complete the configuration in Slack.
1. While still on the Slack configuration page, copy the **token**. Go back to the GitLab browser tab and paste in the **token**.
1. Ensure that the **Active** toggle is enabled and click **Save changes** to complete the configuration in GitLab.

![Slack setup instructions](img/slack_setup.png)

## Usage

You can now use the [Slack slash commands](../../../integration/slash_commands.md).
Changing badges to use parentheses not brackets Previously, we used brackets to denote the tier badges, but this made Kramdown, the docs site Markdown renderer, show many warnings when building the site. This is now fixed by using parentheses instead of square brackets. This was caused by [PREMIUM] looking like a link to Kramdown, which couldn't find a URL there. See: - https://gitlab.com/gitlab-com/gitlab-docs/merge_requests/484 - https://gitlab.com/gitlab-org/gitlab-ce/issues/63800 2019-07-08 04:50:38 -04:00			`# Slack slash commands (CORE ONLY)`
Move project services to new location under Integrations 2017-02-03 13:41:35 -05:00
Bring Slack app docs to CE and add tiers 2019-04-23 23:16:53 -04:00			`> Introduced in GitLab 8.15.`
Move project services to new location under Integrations 2017-02-03 13:41:35 -05:00
Bring Slack app docs to CE and add tiers 2019-04-23 23:16:53 -04:00			`Slack slash commands allow you to control GitLab and view content right inside`
			`Slack, without having to leave it. This requires configurations in both Slack and GitLab.`
Move project services to new location under Integrations 2017-02-03 13:41:35 -05:00
Bring Slack app docs to CE and add tiers 2019-04-23 23:16:53 -04:00			GitLab can also send events (e.g., `issue created`) to Slack as notifications.
			`This is the separately configured [Slack Notifications Service](slack.md).`

			`NOTE: Note:`
			`For GitLab.com, use the [Slack app](gitlab_slack_application.md) instead.`
Move project services to new location under Integrations 2017-02-03 13:41:35 -05:00
			`## Configuration`

Add latest changes from gitlab-org/gitlab@master 2020-03-30 17:08:01 -04:00			`1. Slack slash commands are scoped to a project. Navigate to the [Integrations page](overview.md#accessing-integrations) in your project's settings, i.e. Project > Settings > Integrations.`
			`1. Select the Slack slash commands integration to configure it. This page contains required information to complete the configuration in Slack. Leave this browser tab open.`
Improve Slack docs 2017-04-28 05:47:59 -04:00			`1. Open a new browser tab and sign in to your Slack team. [Start a new Slash Commands integration](https://my.slack.com/services/new/slash-commands).`
			`1. Enter a trigger term. We suggest you use the project name. Click Add Slash Command Integration.`
			`1. Complete the rest of the fields in the Slack configuration page using information from the GitLab browser tab. In particular, the URL needs to be copied and pasted. Click Save Integration to complete the configuration in Slack.`
			`1. While still on the Slack configuration page, copy the token. Go back to the GitLab browser tab and paste in the token.`
Add latest changes from gitlab-org/gitlab@master 2020-04-15 08:09:18 -04:00			`1. Ensure that the Active toggle is enabled and click Save changes to complete the configuration in GitLab.`
Move project services to new location under Integrations 2017-02-03 13:41:35 -05:00
Add info about the new location of Integrations [ci skip] 2017-02-07 16:20:36 -05:00			`![Slack setup instructions](img/slack_setup.png)`
Move project services to new location under Integrations 2017-02-03 13:41:35 -05:00
Improve Slack docs 2017-04-28 05:47:59 -04:00			`## Usage`

Rename "Slash commands" to "Quick actions" Fix https://gitlab.com/gitlab-org/gitlab-ce/issues/27070 Deprecate "chat commands" in favor of "slash commands" We looked for things like: - `slash commmand` - `slash_command` - `slash-command` - `SlashCommand` 2017-05-31 01:50:53 -04:00			`You can now use the [Slack slash commands](../../../integration/slash_commands.md).`