Updated Notify_flock (markdown)

master
Chris Caron 2019-05-20 00:31:42 -04:00
parent 4cdc4ba35e
commit 20cf0b05ea
1 changed files with 2 additions and 2 deletions

@ -43,10 +43,10 @@ Valid syntaxes with an *application / bot* are:
| channel | No | Channels must be prefixed with a hash tag **#** or **g:**. They must represent the encoded id of the channel name (not the human readable reference) You can specify as many channels as you want by delimiting each of them by a forward slash (/) in the url.
| user | No | Users must be prefixed with an at symbol **@** or **u:**! They must represent the encoded id of the user name (not the human readable reference) You can specify as many users as you want by delimiting each of them by a forward slash (/) in the url.
| botname | No | Identify the name of the bot that should issue the message. If one isn't specified then the default is to just use your account (associated with the *incoming-webhook*).
| image | No | Associate an image with the message. By default this is enabled.
#### Example
Send a flock notification to our channel #nuxref (which is identified
as g:abcd1234efgh):
Send a flock notification to our channel #nuxref (which is identified as `g:abcd1234efgh`):
```bash
# Assuming our {token} is 134b8gh0-eba0-4fa9-ab9c-257ced0e8221
# our channel nuxref is represented as g:abcd1234efgh