Dirty web chat bot
But this project was all about quick and dirty, so you aren't going to find any in-depth discussions of that here, but what you will find is: if-statements.
The first thing that I wanted the bot to do is actually reply to a response with the list of commands that it supported, so before actually creating those commands, I wanted to create a collection of all of my supported messages and templates that I built the following to separate them out in a method to simply return that response to the user for any unrecognized response by creating another method that will handle formatting that string into something consumable by the bot and then returning it: Now if we go tell the bot "Hi!
NET, and a few other technologies, so depending on your preferences, you can follow the tutorial of your choice. NET guy, this post will cover that side more heavily, but I'd assume that the Node approach is just as simple.
To get your environment ready, you'll need the following installed: Once you've done that, you should see the available option to create a new Bot Application within Visual Studio: The generated project template should work very similar to an MVC / Web API style project with a single controller to handle messages and a few other areas.
", or really anything, it will respond as expected: The next step will be to actually start interacting with our Firebase database and pulling some data in.
To do this, we will do two things: class to handle making our requests.
Since I'll be hosting this in Azure, I'll store my database endpoint as an environmental variable, but you could easily use a hard-coded string for example purposes.
In order to avoid any Skynet-style issues, we need to properly register the Bot with the Microsoft Bot Framework, so that they can monitor it and ensure it doesn't take over the world.
Now that I have my data, let's jump back to the bot and start up a conversation.
As I mentioned earlier, there are a lot of really, really powerful things that you can do with regards to intent and text analysis to figure out what the user is to say.
Now my entire reasoning for this bot surrounds an event that my friends and I have been doing for a few years now that we call "Third Thursday".
Third Thursday is a monthly gathering, as you might expect on the third Thursday of each month and it works as follows: Fairly simple right?