Why does Mattermost not support Incoming Webhooks with GET?
The problem is that Pingdom alerts with an HTTP GET. Slack has no problem with HTTP GET but in Mattermost not.
Is there a chance that Mattermost will in the future work with HTTP GET? At the moment is this problem the only Reason because our whole team doesn’t switch from Slack to Mattermost.
We’d like to make our incoming webhooks more compatible with Slack if possible, but I’m having trouble getting their incoming webhooks to work with a GET request using cURL. Are you able to send me an example where this is done?
We haven’t been able to find any Slack documentation on how they handle different parameters with a GET request, so we aren’t planning on implementing them at this time. If you’d like to open a feature request to add support for them, you can do so here.
Can you not use the Mattermost API to make GET requests to post messages this way? I’m not entirely sure what your specific usage would be, and how much flexibility/accessibility to modifications of code, as far as the application your using, but I’m interested to learn more about the application you’re trying to use Mattermost with, and hopefully be able to help you get it figured out!
Guys is this a joke? I’ve been breaking my ass off to call everyone into MatterMost and you don’t support even simple webhooks? How do you even plan to overtake slack with such poor functionality. There’s the whole universe in here but this basic thing is not working? Heavily disappointing.
webhooks are working, but you need to use HTTP POST method as opposed to the GET method requested here. Personally I do think that using the GET method for sending messages should be discouraged and maybe Mattermost thinks the same.
Is there a specific reason why you would need to send webhooks using HTTP GET?
@agriesser my only use-case is a pingdom webhook, I can’t make it work with a mattermost. It just doesn’t work. I’ve actually thought to drop pingdom as we’re using cloudflare health checks too, but it appears those doesn’t even have a support for a webhook. Ofcourse there’s always a workaround to write cloudflare worker, or azure function to handle this situation… but I’d like to stick to pingdom if possible.
I just signed up for a 30 day trial and pingdom and the webhook is not slack compatible, here’s the POST payload of one example request:
"long_description": "This is a test message triggered by a user in My Pingdom",
Slack does not support these messages out of the box either, you will have to install the Pingdom App for slack to support this specific format and as far as I can tell there is no Pingdom App for Mattermost at the moment. If Pingdom would use the standard slack webhooks, Mattermost would also support them.
it does uses POST method, and I can’t do anything about it…? You either need to collaborate with them to fix it, or start supporting POST methods. Pingdom is the most popular service to attach to slack. Kind of basics of chatOPS approach. So either you support them, or they support you. I can’t do anything about this as a user right…?
I don’t understand this question, sorry. Pingdom does not allow you to modify the format of the POST message it sends to the webhook receiver, so while the method is OK for Mattermost, the format is not. Pingdom has its own syntax for the alerts it sends via webhooks and in order to understand this syntax, the receiver needs to know the format and neither Slack nor Mattermost do. For Slack, someone (not sure if Slack or Pingdom, but most likely Pingdom) created a plugin that needs to be installed on the receiver side in order to understand the format sent by Pingdom.
As explained above, I think you’re mixing up technical terms here. There’s a feature request wish in the Mattermost user voice forums with regards to supporting Pingdom Webhooks. If you’d like to see this feature implemented, you can vote for the feature wish there:
Please note that Mattemorst is open source and community driven, so if this feature is important for you, you could as well just write your own plugin and release it so it works for others. If you’re a paying customer, please get in touch with your CSM to raise your personal need for this integration.
I tried to verify this statement, but failed to do so - can you share links or statistics that prove this assumption?