GitHub activity where your team already talks

Stop tab-switching to GitHub to know what is happening. The GitHub power posts issues, pull requests, pushes, and CI runs straight into Slack, each event type routed to the channel that should see it, and keeps issues in sync both ways.

Trigger: GitHub webhook
Lands in: The relay log, plus the channels you route to
Setup: 4 min
Needs: Admin on the GitHub org or repo

#ci

ViaApp4:18 PM

Deploy failed on main

viably / on_next · workflow run #2841

Triggered by: @samuel
Failed step: build
Duration: 2m 14s
Commit: 117be5f

View runFile an issue

Routed here because workflow runs are subscribed to #ci, while pull requests go to #code-review.

What this guide produces, as it appears in Slack.

Connect GitHub in three steps

Install the app, pick a default channel, then fine-tune from Slack.

Step 1Install the GitHub App

Connect your organization or repositories to Viably from the dashboard's GitHub power. The GitHub App scopes access to only the repos you select.

Step 2Set a default channel

Choose a default Slack channel for GitHub activity under the GitHub section of the Powers dashboard. Every event type falls back to it unless overridden.

Step 3Tune with /github-notify

Run /github-notify in Slack to see your current subscriptions and route individual event types to specific channels.

Route events to the right channels

/github-notify shows every event type and the channel it posts to. Send PRs to #code-review, failed builds to #ci, and issues to your triage channel, each routed independently, with a workspace default as the fallback.

Event type	What you get
Issues and comments	Opened, closed, and commented issues from your connected repositories.
Pull requests and reviews	PR activity and review submissions, so code review stays visible in Slack.
Pushes	Commits pushed to the branches you care about.
CI and deploys	Workflow results and deployments, written onto the pull request or push they ran against. A failure with nothing to land on still posts on its own.

Two-way issue sync

GitHub is more than a one-way firehose into Slack, because issues flow back the other way too.

File from Slack

Turn a Slack message into a tracked issue and, when GitHub is connected, it is created on the repo as a real GitHub issue. See the Issue Tracking guide for the full flow.

Per-repo control

Issue creation is enabled per repository, so you decide exactly which repos can be written to from Slack, and every issue picker respects that setting.

Stays in sync

Updates on the GitHub side flow back to Slack through your routed channels, keeping both surfaces consistent without manual copying.

Common questions

What teams ask before they turn this on.

How do I choose which GitHub events reach which channel?

Run the github-notify command in Slack. It lists every event type with the channel it currently posts to, and each one can be routed independently, with a workspace default catching anything you have not set explicitly.

Does this replace GitHub's own Slack app?

For most teams, yes. The difference is that Viably routes per event type to per channel and syncs issues both ways, so an issue filed from a Slack conversation becomes a real GitHub issue rather than only a notification about one.

Which events are supported?

Issues and comments, pull requests and reviews, pushes, and CI workflow runs. Each carries a link back to GitHub. A CI result is written onto the pull request or push it ran against rather than posted underneath it, so a broken build turns that card red instead of adding a second message.

Can people create GitHub issues without a GitHub account?

Yes, which is often the point. Somebody reports a bug in Slack, a teammate reacts to file it, and the issue lands in the repo with the Slack thread linked, without the reporter ever opening GitHub.

Get started

Connect your repositories from the GitHub power page. Routing and two-way issue sync are available on the free plan.

Add Viably to Slack

See it in actionGitHub integration