From 8ebdc5eeb0c2d2a7779594ff05951be3b373a899 Mon Sep 17 00:00:00 2001 From: Chris Caron Date: Sat, 10 Aug 2019 15:39:46 -0400 Subject: [PATCH] Updated Notify_slack (markdown) --- Notify_slack.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Notify_slack.md b/Notify_slack.md index 9831698..1bc9773 100644 --- a/Notify_slack.md +++ b/Notify_slack.md @@ -14,10 +14,10 @@ First off, Slack notifications require an *incoming-webhook* it can connect to. * You must **Activate** the **Incoming Webhook** _Feature_ if not already. * On this same configuration screen, you can create a webhook and assign it to a channel/user. -Regardless of what option you choose (above), both will result in giving you a webhook URL that looks something like this: +Regardless of what option you choose (above), both will result in giving you a webhook URL that looks something like this:
```https://hooks.slack.com/services/T1JJ3T3L2/A1BRTD4JD/TIiajkdnlazkcOXrIdevi7F``` -Apprise supports this URL _as-is_ (_as of v0.7.7_), you no longer need to parse the URL any further. However there is slightly less overhead (internally) if you do. +**Note:** Apprise supports this URL _as-is_ (_as of v0.7.7_); you no longer need to parse the URL any further. However there is slightly less overhead (internally) if you do. This URL effectively equates to: ```https://hooks.slack.com/services/{tokenA}/{tokenB}/{tokenC}```