Our Slack integration installs a chat bot called Keybot into your workspace to communicate with you when important events occur - e.g. a pull request is ready to be merged - or to remind you of certain tasks - e.g. morning digest.

It is also possible to ask questions to Keybot to quickly get an overview of the status of pull requests and issues. For example asking "Which PRs are ready to be merged" will prompt Keybot to return the list of pull requests which are mergeable, have a green build and have been approved.

Keybot is a bot....so he might not understand everything yet! But be assured that he is a quick learner!

> What data do we collect?

Our Slack integration fetches the following entities: 

  • Users: we fetch the IDs and timezones of users having access to your Slack workspace. We do not fetch personal data such as names and email addresses.

> What messages do we send?

Users can expect to receive the following automated messages from Keybot:

>> Welcome message

When you connect Slack to Keypup for the first time, users in your workspace will receive a welcome message prompting them to link their Slack account to their Keypup account.

This step is required for us to match Slack users to Keypup users. Slack users that do not have an account on Keypup can simply ignore this message, they will not receive any other message from Keybot.

>> Morning digest

Keypup users on Slack receive a morning digest every day at 9:05am with the top priorities of their Priority inbox.

>> Merge recommendations

When pull requests are mergeable, have a green build and have been approved, Keybot will send a notification to project maintainers and propose to merge them.

Notifications are grouped and sent at most every two hours. Also you won't receive suggestions twice for the same pull request. You're busy so we take very seriously to keep our messaging as light as possible.

> Asking questions to Keybot

You can ask questions to Keybot to get an update on pull requests and issues.

Here are a few examples of questions you may ask:

  • How many PRs can be merged?

  • Which PRs can be merged?

  • How many issues are open?

  • How many PRs have been merged last week?

  • Which PRs are ready to be reviewed?

  • ...and more!

Did this answer your question?