mirror of
https://github.com/caronc/apprise.git
synced 2025-06-24 19:51:21 +02:00
Updated Notify_flock (markdown)
parent
bcd2f078e4
commit
5c57ef8805
@ -7,7 +7,7 @@
|
||||
### Account Setup
|
||||
Flock has a lot of similarities to Slack. Flock notifications require an *incoming-webhook* or a *app/bot* it can connect to.
|
||||
|
||||
## Incoming ebhook
|
||||
## Incoming Webhook
|
||||
|
||||
You can generate an Incoming webhook from [here](https://dev.flock.com/webhooks](https://dev.flock.com/webhooks). Just follow the wizard to pre-determine the channel(s) you want your message to broadcast to. When you've completed this process you will receive a URL that looks something like this:
|
||||
```https://api.flock.com/hooks/sendMessage/134b8gh0-eba0-4fa9-ab9c-257ced0e8221```
|
||||
@ -15,6 +15,8 @@ You can generate an Incoming webhook from [here](https://dev.flock.com/webhooks]
|
||||
This effectively equates to:
|
||||
```https://api.flock.com/hooks/sendMessage/{token}```
|
||||
|
||||
**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.
|
||||
|
||||
In this example the token is `134b8gh0-eba0-4fa9-ab9c-257ced0e8221`
|
||||
|
||||
## Bot
|
||||
@ -22,6 +24,7 @@ Bots are a bit more difficult and presume that you followed their instructions o
|
||||
|
||||
### Syntax
|
||||
Valid syntaxes with an *incoming webhook* are:
|
||||
* `https://api.flock.com/hooks/sendMessage/{token}`
|
||||
* flock://**{token}**/
|
||||
* flock://**{botname}**@**{token}**/
|
||||
|
||||
|
Loading…
x
Reference in New Issue
Block a user