Create a service hook for Azure DevOps with Slack
TFS 2017
Post messages to Slack in response to events in your Azure DevOps organization, such as completed builds, code changes, pull requests, releases, work items changes, and more.
Create a custom app in Slack
Refer to the Slack documentation, Sending messages using Incoming Webhooks to understand the process of using Web Hooks to push information to a Slack channel.
Create a new Slack app
Activate incoming Web Hook and add a new Web Hook to the desired workspace
Select the channel for which Web Hook must be created
Copy the Web Hook URL and go to Azure DevOps.
Create a service hook subscription in your organization
Go to your project Service Hooks page:
https://dev.azure.com/{orgName}/{project_name}/_apps/hub/ms.vss-servicehooks-web.manageServiceHooks-project
Select Create Subscription.
Choose the types of events you want to appear in your Slack channel.
You can filter each of the triggers in specific ways. For example, the pull request created trigger can be filtered on the repository in which the pull request occurs, the target branch it applies to, and the team members that are required or invited to review the request.
Paste the Web Hook URL from the Slack integration that you created and select Finish.
![Action dialog box with the Web Hook URL]./media/slack/action.png)
Now, when the event you configured occurs in your project, a notification appears in your team's Slack channel.
Q & A
Q: Why don't I have the pull request events as an option when I configure my trigger?
A: Pull requests are only available with projects that use Git. If your project uses TFVC, pull event triggers aren't available, and your code event is called "Code checked in" instead of "Code pushed".
Q: How can I get multiple events to show up in my Slack channel?
A: Create a new subscription for each type of event you want. For example, if you want to see build failures and new work items in your Slack channel, create two additional subscriptions.