We've been using Slack to communicate with each other for the first couple weeks of the class. Now it is time to build our very own Slackbot to add a fun interactive component to the chat room. A Slackbot is an integration into slack that can either respond to specific phrases that are mentioned in Slack or they can post things from outside of slack into a channel or private conversation. There are now entire startups built on top of Slackbots. For example, people have built Slackbots that let you hail an Uber from them or schedule meetings with different members of your team (where it searches your Google Calendar). One of the most popular Slackbot's lets people post random gifs based on phrases into a channel from Giphy.

For our first project, we are going to keep things simple. We will build a Slackbot on top of the popular Github bot called Hubot. Hubot is a robot that was created by GitHub, that automates their company chat. Hubot can deploy their site, be a source of fun comments and also can automate a lot of their daily tasks. It is powerful, but it is also built in a way that we can build whatever we want on top of it.

Hubot scripts are generally written in CoffeeScript, which is a JavaScript scripting language. They also take vanilla JavaScript, which is what we will be using. Your bot can respond to whatever you like, but should do at least 3 different things.

Note to instructors: In order for students to deploy their Slackbots, you'll need to configure Hubot integrations and generate API tokens for your students to use. Click here to configure a new Hubot. Once your Hubot has been configured, edit that configuration in order to access its API token. Slack starts refusing connections when more than around 5 users attempt to use the same API token simultaneously, so you will likely need to set up multiple Hubots and provide multiple API tokens, in order for all of your students to run their bots in the Slackroom at the same time. For this project, students should use the Hubots and tokens that they used during the in-class Slackbot lab and no more than 2-3 students should use the same Hubot/API token. Your Slack organization will allow you to configure up to 10 Hubot integrations, so you should have enough integrations for a class of 30 or fewer students.

Hubot has a few basic functions:

Respond

Using the Respond command, will search through a series of text that you give it and if it sees the text in the Slack channel, this function will execute. You can then use the Send command to post a message to the channel.

Send

Send lets you send a message to the Slack channel. We usually use this hand-in-hand with respond. For example, when someone says something (i.e. 'Hi') on the channel, we respond by sending "Howdy". Of course, it will only send or respond based on the commands and words you teach it (by adding it to your code).

Reply

Reply lets you reply to a certain user or to the person who sent the original message. This includes the @ in front of the user's name so they get alerted.

Random

Hubot also has a random script which is pretty nifty so we don't need to write custom JavaScript for that. It will return a random result based on what you give it. Check out the starter code for some examples.

Your app must:

• Have a message post to Slack based on user input
• Do at least 3 different things.
• One of the commands must utilize the list of people in the class to send a direct message or reply.
• Leverage Hubot
• Use at least 1 conditional to change the outcome of a Slackbot.

• Leverage a for loop to iterate over a collection
• Introduce a random component
• Include an image in the response in addition to text

• A working Slackbot, built by you, that can be run in the class Slack room.
• A new git repository hosted on Github, where codebase is maintained.
• A readme.md file with explanations of what your bot does, what commands it responds to, the approach taken, installation instructions, unsolved problems, etc.

• Review existing Slackbots and Hubots for inspiration.
• Begin by writing down what your different commands will be and expected outcomes before writing any code.
• Write pseudocode before writing any code.
• Get Hubot working out of the box before writing any custom code.
• Test small pieces of functionality frequently to make sure everything is working.
• Use tools such as Stack Overflow, Google and documentation resources to solve problems.

Ask your bot whether we have class today or not. Use JavaScript to check today's date and then respond back with whether we have class or not.

Use an array to store a number of your favorite quotes. When you ping your bot, have it return a random quote from your list.

Key Resources

• Hubot Scripting
• Hubot adapter for Slack
• Slack API Documentation

Examples

• Hubot Ship It
• Slackbot Community
• Hubot scripts

Advanced Reading

• Great in-depth tutorial on writing a Slackbot
• Hubot scripts explained
• Create your own chatbot with Hubot & Coffeescript
• Getting Started with Slackbots

Students will create a new repository on GitHub called "my-first-slackbot" and push their code to this new repository when they are ready to submit.

The instructional team will grade each technical requirement and provide a numeric grade on a scale.

• Technical Requirements: Did you deliver a project that met all the technical requirements? Given what the class has covered so far, did you build something that was reasonably complex?

• Creativity: Did you added a personal spin or creative element into your project submission? Did you deliver something of value to the end user (not just a hello world response)?

• Code Quality: Did you follow code style guidance and best practices covered in class, such as spacing, modularity, and semantic naming? Did you comment your code as your instructors have in class?

• Total: Your instructors will give you a total score on your project between:

  Score	Expectations
  0	Does not meet expectations.
  1	Meets expectactions, good job!
  2	Exceeds expectations, you wonderful creature, you!

This will serve as a helpful overall gauge of whether you met the project goals, but the more important scores are the individual ones above, which can help you identify where to focus your efforts for the next project!