Details
-
Improvement
-
Resolution: Fixed
-
Major
-
None
-
None
-
None
Description
When adding a contact for alerting, the webhook API doesn't work for Zoom.
Can you guys create a separate transport mechanism for this?
It works similar to Slack, except that it has the authorization token in a header instead of in the URL.
Example:
curl 'https://inbots.zoom.us/incoming/hook/e7aCgmWEZNvrwHxoFWEM1OEZ?format=fields' -X POST -H 'Authorization: BLl5_Mz4vNp677GvwxCSC-MM' -H 'Content-Type: application/json' -d '{"foo":"bar","baz":"qux"}'
Documentation for the richt text messages is here: https://marketplace.zoom.us/docs/guides/chatbots/customizing-messages/
Attachments
Activity
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: In Progress [ 3 ] | New: Resolved [ 5 ] |
| Comment |
[ _*General questions and device support can be discussed in [our Discord channel, click here to join|https://discord.gg/GjpNXKWm8W].*_ ---- Please make and attach additional information about the device: * full snmp dump from device: {noformat} snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -ObentxU <hostname> .1 > myagent.snmpwalk snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalk {noformat} _If device not support SNMP version 2c, replace -v2c with -v1._ * If you have problems with discovery or poller processes, please do and attach these debugs: {noformat} ./discovery.php -d -h <device> ./poller.php -d -h <device> {noformat} * additionally attach device and/or vendor specific MIB files ---- {color:#505F79}_This comment is added automatically._{color} ] |
| Status | Original: Pending Response [ 10000 ] | New: In Progress [ 3 ] |
| Assignee | Original: Adam Armstrong [ adama ] | New: Mike Stupalov [ landy ] |
| Status | Original: Open [ 1 ] | New: Pending Response [ 10000 ] |