Codica logo
Get a free quote

Building a Time Tracking Slack Bot with Vue.js and Ruby on Rails

Chatbots are viewed as self-serving tools helping users to get answers to their inquiries.

Today, these bots are utilized for a variety of purposes. Apart from obvious cases - sales and support inquiries, sometimes chatbots are used by companies’ internal issues and solve organizational issues.

In our case, we use a time-tracking chatbot which allows monitoring the development workflow and evaluating each company member performance. Today we’re going to show you how we created this bot (we call it ‘Timebot’) and what benefits it brings to our company’s workflow.

The challenge

Time tracking is a part of everyday life in any software development project, for both internal and external purposes. For example, we need to send reports to our clients, to monitor the team workload and redistribute the tasks accordingly.

With the company’s growth, the scope of our projects became more extensive, and all of them became pretty diverse. Thus, monitoring the development workflow and evaluating each company member performance became an important issue for us. So we started looking for options to automate reporting and simplify the time tracking process.

At Codica, we utilize Slack for corporate communication to discuss all project issues. And the Slack App provides an opportunity to create different bots which help to automate everyday routine. Naturally, we had an idea to create a Slack bot for time tracking.

Additionally, one of the leading grounds to build a time-tracking tool using Slack is that web solutions are rather time-consuming. We were interested in creating a more effective and optimized way of time-tracking.

When we made the decision to create our Slack bot for time tracking, we proceeded to gather requirements. The solution was not supposed to work for time tracking only, so we had to define all the issues it would help us solve.

The solution


At the beginning of the bot development, we were looking to cover the following needs:

  • Simplify the tracking process for the team
  • Automate reporting system for customers
  • Provide the opportunity to clearly evaluate the overall workload
  • Record each company’s employee contribution to the projects

After initial discussions, we arrived at the idea that the following features list would help us with the above requirements:

  • Time tracking would allow tracking the number of hours spent on a particular task or project.

  • Transparent reporting system would allow gathering and getting particular information for a specific period from the timesheets and provide the customers with timely and accurate reports.

  • Bundling with Trello would simplify the process of time tracking. We have chosen the Trello system because we utilize it for internal task management and tracking. We would be able to insert a particular Trello ticket for time tracking or messaging.

  • Administration panel would give an opportunity to monitor the company employees’ timesheets, current projects they work on, absence days etc. Also, it would simplify tracking the overall performance.


1. Defining the technology stack

After considering the required functionality, we turned to technical implementation. For development purposes, we have created two applications:

As for the technology stack, we have chosen the following tools for Slack bot:

  • Rails 5
  • Ruby 2.4
  • PostgreSQL

And these technologies were used for Admin panel development:

  • Vue
  • Vue-router
  • Vuex
  • Vue-element-admin (admin panel template)
  • JWT (JSON Web Token)

The main reason to use such technologies as Vue.js and Rails is that we like them and utilize in our development process.

2. Bot creation and integration

Initially, we have created a bot at Slack API following the setup instructions. You set your workspace, define Bot’s name, profile picture and get a special API token.

For the purposes of API management for our chatbot, we have utilized Slack Ruby Client to use the special interface.

Thus, we have added the Slack API token to the .env file (create it if you don’t have one) the following way:

1Slack.configure do |config| 2 config.token = ENV['SLACK_API_TOKEN'] 3End 4

This way we have integrated Slack API and now we can configure the bot.

3. Creating the list of commands

When the Slack Bot was ready for configuration, we have turned to create the available commands. All of them were created through if..else conditional statements. Here are some commands from the list:

helpprint help.
projectsprint all available projects.
find project SEARCH_QUERYfind specific project.
/logtimelog time via interective dialogue.
update(OPTIONAL) DAY.MONTH.YEAR PROJECT_NAME HOURS:MINUTES COMMENTcreate an entry for the specific date.
add project PROJECT_NAMEadd new project.
show day/show week/show monthget a report for this day/week/month.
show absence/show absence last yeardisplay absences.

Each user is assigned a special ID to be defined by the bot. When a user enters a command, the bot checks whether it’s a valid command. If ‘true’, the bot returns the following data for this particular user by making a request to the database. If ‘false’, the bot returns ‘I don’t understand you’.

First of all, we’ve created the Event Handler:

1class EventHandler 2 include Message::Conditions 3 include Message::Logger 4 5 attr_reader :client, :data, :sender, :messages, :public_channels 6 7 def initialize(client, data, messages, public_channels) 8 @client = client 9 @data = data 10 @public_channels = public_channels 11 @sender = 12 @messages = messages 13 end 14 15 def handle_message 16 return if message_is_not_processable 17 user = User.find_by(uid: data.user) 18 log_incoming_message(user, data.text) 19 if message_is_enter_time 20, data.text, messages) 21 elsif message_is_specify_project 22, data.text, messages) 23 elsif message_is_request_for_help 24 25 elsif message_is_remove_entry 26, data.text) 27 elsif message_is_show_reports 28, data.text) 29 elsif message_is_enter_time_for_day 30, data.text) 31 elsif message_is_request_for_project 32 33... 34 else 35, messages) 36 end 37 end 38End 39

Then, we’ve created Classes for every bot’s command, for example:

1class AddProject < BaseService 2 include ServiceHelper 3 4 attr_reader :user, :text 5 6 def initialize(user, text) 7 @user = user 8 @text = text 9 super() 10 end 11 12 def call 13 project_name = text.match(Message::Conditions::ADD_PROJECT_REGEXP)[1] 14 project = find_project_by_name(project_name) 15 16 if project 17 sender.send_message(user, "Project with name #{} already exists.") 18 return 19 end 20 21 if project_name.length < Project::MINIMUM_PROJECT_NAME_LENGTH 22 text = "Project name is too short - must be at least #{Project::MINIMUM_PROJECT_NAME_LENGTH} characters." 23 sender.send_message(user, text) 24 return 25 end 26 27 project = Project.create!(name: project_name) 28 sender.send_message(user, "Project with name #{} is created.") 29 end 30end 31

It’s possible to add new commands anytime.

Examples of our Timebot workflow

Time tracking allows tracking the number of hours spent on a particular project and monitoring a development workflow as a whole. The information will reflect on each member’s timesheet, which can be later viewed and edited.

To log time, you need to enter the project name, time spent for a particular task, and add comments to specify the task details.

Logging time with TimeBot in Slack | Codica

Absences allow tracking employee’s vacation, illnesses, and other reasons for absence on a particular day.

Tracking absence with TimeBot in Slack | Codica

Reports are convenient to get particular data and gather it for further statistics creation and analysis.

Getting a report on the time logged with TimeBot in Slack | Codica

Projects are implemented to allow the users to monitor, add, and utilize the project for time logging.

List of projects available with TimeBot in Slack | Codica

Administration panel

Along with the Slack bot, we have developed an Administration panel. It gives an opportunity to monitor the company members’ timesheets, current projects they work on, absence days, etc.

It is the internal part of our time tracking tool and is particularly valuable for project managers. It fully reflects the overall performance statistics on individuals, teams, and projects at any chosen period.

In the Dashboard, we have a visual display of our data. The graphs contain the number of hours spent by a user, position, for a specific project. Moreover, the Dashboard allows getting information about the projects particular users are working on.

Dashboard in TimeBot admin part | Codica

Also, here is our Time logs section which allows monitoring, viewing, editing, and deleting the data of logged time.

Dashboard in TimeBot admin part - timelogs | Codica

The results

We have developed a time-tracking tool in Slack, which fully meets our requirements and needs. The main benefits of Timebot creation are easier monitoring of the development workflow and evaluating each company member performance.

Here is the full list of benefits and features that our Timebot brings:

  • Tracking of time worked on a specific project
  • Tracking absences (vacation, sick leave)
  • Notifications with meeting time that pops up in 10 minutes before the meeting, discussion
  • Performance and velocity of the internal company processes
  • Analysis of time tracked depending on the position like front-end and back-end developer, QA, PM that sufficiently helps project managers in estimating
  • The accuracy of reports and statistics that we provide to the customers

To conclude, we have shown you how to create a SlackBot for time tracking, and hope that this guide will be interesting for you and your business. We would add that chatbots are handy and powerful tools for different tasks you may create.

Rate this article!
Rate this article | CodicaRate this article | CodicaRate this article | CodicaRate this article | CodicaRate this article | CodicaRate this article | CodicaRate this article | CodicaRate this article | CodicaRate this article | CodicaRate this article | Codica
(0 ratings, average: 0 out of 5)

There are no comments yet

Leave a comment:

Related posts

Codica Listed Amongst Top Ukrainian Web Developers in 2019
Codica Way
Codica Listed Amongst Top Ukrainian Web Developers in 2019
Pros & Cons of Using Ruby on Rails for Web Development | Codica
Pros & Cons of Using Ruby on Rails for Web Development
Choosing React or Vue for Your Startup in 2024 | Codica
React vs Vue: Tech Comparison and Use Cases for 2024

Want to receive more content like this?

Nobody likes popups, so we waited until now to recommend our newsletter, a curated periodical featuring thoughts, opinions, and tools for building a better digital world.

Don’t wait and suscribe now!

Latest posts

How to Build a Minimum Viable Product: Features, Steps & Costs | Codica
How to Build a Minimum Viable Product in 2024: The Ultimate Guide for Startup Founders
The Best 30+ Tools for MVP Development | Codica
30+ Tools for Creating MVP for Startups from Scratch in 2024
The Most Common Minimum Viable Product Mistakes | Codica
12 Most Dangerous MVP Development Mistakes and How to Avoid Them