forked from aspnet/WebHooks
-
Notifications
You must be signed in to change notification settings - Fork 0
/
index.html
40 lines (37 loc) · 1.46 KB
/
index.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
<!DOCTYPE html>
<html>
<head>
<title>Microsoft ASP.NET WebHooks Slack Receiver</title>
<meta charset="utf-8" />
</head>
<body>
<h1>Microsoft ASP.NET WebHooks Slack Receiver</h1>
<p>This sample illustrates how to wire up a Slack WebHooks receiver which can be used for both
Slack Outgoing WebHooks as well as Slash Commands. A sample WebHook URI is:</p>
<pre>https://<host>/api/webhooks/incoming/slack/{id}</pre>
<p>
Note that for security reasons the URI <b>MUST</b> be <b>https</b>.
</p>
<p>
Set the <b>MS_WebHookReceiverSecret_Slack</b> application setting to the Slack 'token' parameter, optionally using IDs
to differentiate between multiple WebHooks, for example '<c>secret0, id1=secret1, id2=secret2</c>'.
</p>
<p>
In this example we use id 'trigger' for an outgoing WebHook and id 'slash' for a slash command. This means that you
should register the following URIs with Slack:
</p>
<pre>
https://<host>/api/webhooks/incoming/slack/trigger
https://<host>/api/webhooks/incoming/slack/slash</pre>
<p>
and then configure the application setting as follows
</p>
<pre>
<add key="MS_WebHookReceiverSecret_Slack" value="trigger=<token>, slash=<token>" />
</pre>
<p>
Please see <a href="https://api.slack.com/outgoing-webhooks">Slack WebHooks</a>
for more information.
</p>
</body>
</html>