Outgoing Webhooks
I want Discord to be able to contact my web server for a response when someone interacts with a "bot". This allows my to not run an always connected process for my bot, but just use a simple website / aws lambda function.
Slack has both older "outgoing webhooks" and new slash commands for Slack apps. In both cases these allow a system to interact with users without running a bot process. Instead when the user variously mentions a bot, talks to a bot, or types a certain slash command, then that user's message is HTTP posted to a certain url, and then the server can reply with a message back from the bot.
For example, in my particular use case, I have a traditional discord webhook setup on a channel that notifies us of customer actions in our system.
For example:
My current system webhook to Discord:
"Ronald Weasley has purchased Monster Book of Monsters. #5567"
What I want is for a customer service person watching the channel to be able to type:
"@storebot cancel #5567"
Which would be POSTed to my url, and I would reply to that with a:
"Ronald Weasley's order has been canceled"
I'm aware that I could run my own traditional bot, but I really don't want to run and manage another process. I just want my own site and HTTP posts only.
-
I would also prefer this function/feature.
Slack and Telegram both have these kinds of integrations, and I can run Lambda functions on AWS for free instead of managing a server/container somewhere.
3 -
Dont get
-2 -
Dont get
-3 -
I would also prefer being able to run bots this way.
0 -
This would be a life saver! It is a must feature!
0 -
Same, this would be very useful for a number of services, Zapier/IFTTT, etc.
0 -
+1 to this for sure! This would help me a ton as I don't expect messages around the clock to trigger my bot. Using something like AWS Lambda I could save cost quite a bit not having an always running process listening to Discord's websocket API.
To expand on the suggestion, it would be great being able to select which types of events go to a given webhook (similar to selecting one or multiple permissions in an application for OAuth2). This way I could theoretically have one AWS Lambda function handle one or multiple events.
4 -
+1 This would make life so much better! Would remove the hassle of trying to ensure connection to all servers. Also would allow me to keep costs down and offer something for my users probably completely free!
Absolute must have.1 -
No lie, this would honestly make the world a better place, we can stop running idle listeners and save the world ;D <3
Please this would be so easy, you could even have this be client side, but I would prefer clients not reaching directly out to my webhooks with credentials :PI have a small school club and we're spending ~$14-28/m on heroku to run a staging and production environment that could be ran on a free tier on GCP or AWS. I know heroku is an extreme case, but it's also a reality.
There's no reason to have idle bots when we could have outgoing webhooks.
5 -
+1 on this feature, it would be great to have this as idle bots, in my opinion, are wasted computing real estate (especially when they're infrequently invoked)
0 -
+1 to integrate with Zork.
0 -
Would love this functionality to integrate with Azure LogicApps
0 -
A very important feature. Serverless applications are coming more and more. Services such as AWS Lambda provide a low-cost or even free platform. Other services like Mattermost or Slack have such a feature.
Please :-)
0 -
Holding off creating a bot until this is implemented.
2 -
Wow, crazy that we still don't have any way of doing push notifications like this. Without outbound notifications, Lambda is pretty much a non-starter.
0 -
I second what everyone is saying here. I was planning to port a Slack app I wrote over to Discord, but I'll hold off. MS Teams looks like it supports user-submitted commands though.
0 -
I second (48th) this. Allowing an outgoing webhook will allow developers to host their webhooks on just about any cloud platform that hosts REST APIs. This will reduce the cost for developers.
Forcing users to run a long running process is a rather lame way of doing this
1 -
I would also really like this! This is one of the top things Slack offers that Discord does not.
0 -
Outgoing webhooks are supported for slash commands: https://discord.com/developers/docs/interactions/slash-commands
2 -
@advaith
This is a very wonderful first step, and fulfills many of the use cases here. However, I would love to see coverage for all, or at least major events (MESSAGE_*, VOICE_STATE_UPDATE) through the new outgoing webhook interface.0 -
Hi any news on this feature request? Thanks!
0 -
Use case of outgoing webhooks for bot interactions (described in the initial post) has become fully supported:
I've filed a separate post explicitly requesting outgoing webhooks FOR GATEWAY EVENTS:
0
Please sign in to leave a comment.
Comments
22 comments