Skip to content
Notis

Act on Community Issues Instantly

When moderation requires blocking a GitHub user, remove a reaction in Slack to trigger it—no context-switching to GitHub.

Trigger

Message Reaction Removed

Triggers when a reaction is removed from a message.

Action

Block a user

Block a user from interacting with your account and repositories.

Why this helps

A user becomes problematic on GitHub. Blocking them means opening GitHub, finding their profile, and going through the block flow. If you're managing community in Slack, this interrupts your moderation workflow.

  • Moderate your GitHub community from Slack without context-switching
  • Block problematic users immediately when you identify them
  • Moderation workflow stays in one place—Slack

Setup

Build it in a few focused steps.

  • 1Connect Slack and GitHub to Notis.
  • 2Create an automation: 'When I remove a specific emoji reaction (e.g., a thumbs-down) from a Slack message mentioning a GitHub username, block that user from my GitHub organization.'
  • 3Specify which emoji removal should trigger blocking and how Notis identifies the GitHub username.
  • 4Choose a Notis channel for confirmation logs.
  • 5Test with a test user to ensure blocking works correctly.

Questions about this workflow

Can I undo this if I block someone by mistake?

Yes. GitHub's blocking is reversible. You can ask Notis to unblock someone by sending a message or using a different emoji reaction.

Does this block them from all my repos?

No, it blocks them from the GitHub organization. They can't contribute, see private repos, or interact with org members.

What if the Slack message doesn't clearly mention a GitHub username?

Notis will ask you to confirm the GitHub username before blocking—it won't block the wrong person.

When this happens · Trigger

Triggers when a reaction is removed from a message.

Do this · Action

Block a user from interacting with your account and repositories.

Supported Triggers and Actions

Notis builds workflows that link Slack to GitHub. A trigger fires from one place; an action lands in another.

Slack triggers

GitHub actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

Accept a repository invitation

Accept a pending repository invitation.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

Abort Repository Migration

Aborts a queued or ongoing repository migration.

ActionInstant

New Channel Created Trigger

Triggers when a new channel is created.

TriggerInstant

Add email for auth user

Add email addresses to your account.

ActionInstant

Channel Message Received

Triggers when a message is posted in a channel, excluding direct messages.

TriggerInstant

Add app access restrictions

Allow apps to push to a protected branch.

ActionInstant

Direct Message Received

Triggers when a new direct message, including a thread reply, is sent to a user.

TriggerInstant

Add a repository collaborator

Add a user as a repository collaborator or update their access.

ActionInstant

Message Reaction Added

Triggers when a reaction is added to a message.

TriggerInstant

Add field to user project

Adds a custom field to a user-owned project.

ActionInstant

Message Reaction Removed

Triggers when a reaction is removed from a message.

TriggerInstant

Add a repository to an app installation

Grant an app access to a repository.

ActionInstant

New Bot Message Received Trigger

Triggers when a bot posts a new message in a channel.

TriggerInstant

Add item to user project

Adds an issue or pull request to a user-owned project.

ActionInstant

Connect any two apps with Notis in the middle.

Slack and GitHub, or any other combination from 1,600+ integrations.

When this happens · Trigger

Do this · Action

Save your first hour today.

7-day trial of any paid plan, with $20 of usage included.
No card. Works with personal or business GitHub.