You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Service Hooks let you run tasks on other services when events happen in your project in Azure DevOps.
17
+
You can use service hooks to run tasks on other services when events happen in your Azure DevOps project.
18
18
19
-
For example, you can create a card in Trello when a work item gets created or send a push notification to your team's mobile devices when a build fails. You can also use service hooks in custom apps and services as a more efficient way to drive activities when events happen in your projects.
19
+
For example, you can create a card in Trello when a work item gets created. Or you can send a push notification to your team's mobile devices when a build fails. You can also use service hooks in custom apps and services as a more efficient way to drive activities when events happen in your projects.
20
20
21
21
## How do service hooks work?
22
22
23
23
Service hook **publishers** define a set of *events* that you can subscribe to.
24
-
**Subscriptions** listen for these *events* and define **actions** to take based on the event.
24
+
**Subscriptions** listen for these events and define **actions** to take based on events.
25
25
26
26
Subscriptions also target **consumers**, which are external services that can run their own actions
27
27
when events occur.
@@ -31,7 +31,7 @@ when events occur.
31
31
::: moniker range=" azure-devops"
32
32
33
33
> [!NOTE]
34
-
> Service hooks require allowing IP ranges for inbound connection to service endpoints. The service endpoint is the set of properties provided to a service hook. For more information, see [Allowed address lists and network connections, IP addresses and range restrictions](../organizations/security/allow-list-ip-url.md#range-restrictions).
34
+
> To use service hooks, you must allow specific IP address ranges for inbound connections to service endpoints. A service endpoint is a set of properties provided to a service hook. For more information, see [IP addresses and range restrictions](../organizations/security/allow-list-ip-url.md#range-restrictions).
35
35
36
36
::: moniker-end
37
37
@@ -88,7 +88,13 @@ The following services are available as the target of service hooks. For more in
88
88
89
89
## Create a subscription
90
90
91
-
When you integrate one of these services with Azure DevOps, you must create a subscription. In many cases, you need to do some configuration in the other service, too. For specific details, check out the information for the service that you're interested in.
91
+
To integrate one of these services with Azure DevOps, you create a service hooks subscription. In that subscription, you specify:
92
+
93
+
- The target service to integrate.
94
+
- The event to trigger on.
95
+
- An action to run on the target service.
96
+
97
+
To create a subscription, take the following steps. In many cases, you also need to configure the target service. For detailed information, see the documentation for the service that you want to integrate.
92
98
93
99
::: moniker range="<=azure-devops"
94
100
@@ -165,7 +171,7 @@ A: Yes. You can revoke authorizations from your profile.
165
171
166
172
### Q: Why can't we set up service hooks for HipChat anymore?
167
173
168
-
A: Atlassian officially dropped support for HipChat. For more information, see [the announcement](https://www.atlassian.com/partnerships/slack/faq#faq-3ccc5a61-711b-4ef2-9ca2-3a34b2ec143b).
174
+
A: Atlassian officially dropped support for HipChat. For more information, see [Atlassian Frequently Asked Questions](https://www.atlassian.com/partnerships/slack/faq#faq-3ccc5a61-711b-4ef2-9ca2-3a34b2ec143b).
0 commit comments