GitHub PR notifications, delivered to you in Slack.

Set up Floka

1. Connect your GitHub account. Start with Connect GitHub and sign in with the account you use to write and review code.
2. Enable the repositories you work in. In setup, choose Install or request access. Select your account or organization and the repositories Floka may access. If approval is needed, share the administrator guide with an organization owner.
3. Connect your Slack identity. Choose your workspace in setup and complete Slack authorization. Your workspace may require an administrator to approve the app. Each developer connects their own identity, even when the shared app is already installed.
4. Check your first sample. Floka sends a labelled sample on your first Slack connection. Check the DM, then use Finish setup when the required checks are complete. If you continue to the dashboard early, you can finish setup later.

The sample confirms that Floka can send a message to your Slack account. Real notifications also need access to the relevant GitHub repository and an event involving you.

For administrators: the GitHub and Slack installations are shared. Installing the apps does not enroll every engineer or connect your own personal notification account. People who want DMs sign in and connect individually; their teammates do not all need to use Floka.

Review Permissions & data before approving an installation. Floka is currently free.

Which notifications you receive

Messages follow your GitHub identity and arrive in the Slack workspace you connected. Floka filters out notifications about your own actions.

For example, if Alex requests your team’s review, connected members with team review requests enabled receive a DM. If you later comment in a review thread, replies can reach you even when you are not the PR author.

Floka learns participation from GitHub activity it receives. Connecting Floka does not import a complete history of older conversations.

How messages update

When you submit a review on GitHub, Floka crosses out the request in your DM and marks it as reviewed by you. Reviewing a team request resolves your own message; it does not mark every teammate’s review as complete.

Resolving a review thread updates related comment, reply, and mention messages for that thread. Merging or closing a PR updates its outstanding messages. You can still follow their links back to GitHub.

These updates reflect activity on GitHub. You do not need to manually check messages off in Slack.

Control notification volume

Open Settings → Notifications to choose individual notification types, then select Save changes. The groups are Review requests, Activity on your PRs, Comment threads, Mentions, PR status, and Bots.

Human review requests, comments, reviews, mentions, and PR updates start enabled. Four bot categories start disabled: review requests, comments, reviews, and mentions. These apply when GitHub identifies the sender as a bot, including coding agents posting through bot accounts.

Other bot activity follows the corresponding notification setting. For example, a merge performed by a bot can still produce a PR status notification.

Use Settings → Repositories to mute repositories for your own notifications. Muting a repository does not uninstall the shared GitHub App or change another developer’s preferences.

Troubleshoot and disconnect

If a notification is missing, work through these checks:

1. In Settings → Connections, confirm the GitHub identity and Slack workspace. Refresh the connection checks after changing access.
2. Check that the GitHub App has access to the specific repository. An installation on an organization does not necessarily include every repository, and a pending request still needs approval.
3. Check that the notification type is enabled and the repository is not muted.
4. Confirm the event involves you and was performed by someone else. Check the bot settings if the sender is an automated account.
5. If the app was removed or its access revoked, reconnect it through setup. A previous sample does not prove the current connection still works.

Help includes saved setup checks and support. Sign in there to send a message about an unresolved issue.

Stop receiving notifications

Turn off the notification types in Settings and save, or mute individual repositories. To revoke the shared apps’ access, use GitHub’s installation settings and Slack’s app settings. Removing a shared installation affects other people using it.

Revoking access and deleting stored data are different actions. See what happens when you uninstall.