Block a confirmed abusive GitHub user
Turn clear risk signals into a focused account protection action.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Block a user
Blocks an existing individual github user (not an organization or your own account), preventing them from interacting with your account and repositories.
Why this helps
Abusive contacts consume attention while the blocking step waits in another system.
- Shorten response time
- Keep evidence context with the action
- Avoid blocking when the payload is unclear
Setup
Build it in a few focused steps.
- 1Connect Bulk Email Checker and GitHub once in Notis.
- 2Create an automation that states the exact blocking criteria.
- 3Choose a webhook trigger for reviewed risk results.
- 4Select where action reports should go.
- 5Test with one confirmed abusive user payload.
Questions about this workflow
Will it block based only on a risky email result?
No. Your instruction should require confirmed abusive behavior in addition to verification context.
Can the action be undone?
GitHub account blocking changes access, so review the report and use GitHub controls to reverse it if needed.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Bulk Email Checker to GitHub. A trigger fires from one place; an action lands in another.
Bulk Email Checker triggers
GitHub actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Accept a repository invitation
Accepts a pending repository invitation that has been issued to the authenticated user.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
List repositories starred by the authenticated user
Deprecated: lists repositories starred by the authenticated user, including star creation timestamps; use 'list repositories starred by the authenticated user' instead.
List stargazers
Deprecated: lists users who have starred a repository; use `list stargazers` instead.
Star a repository for the authenticated user
Deprecated: stars a repository for the authenticated user; use `star a repository for the authenticated user` instead.
Add email for auth user
Adds one or more email addresses (which will be initially unverified) to the authenticated user's github account; use this to associate new emails, noting an email verified for another account will error, while an existing email for the current user is accepted.
Add app access restrictions
Replaces github app access restrictions for an existing protected branch; requires a json array of app slugs in the request body, where apps must be installed and have 'contents' write permissions.
Add a repository collaborator
Adds a github user as a repository collaborator, or updates their permission if already a collaborator; `permission` applies to organization-owned repositories (personal ones default to 'push' and ignore this field), and an invitation may be created or permissions updated directly.
Add a repository to an app installation
Adds a repository to a github app installation, granting the app access; requires authenticated user to have admin rights for the repository and access to the installation.
Connect any two apps with Notis in the middle.
Bulk Email Checker and GitHub, or any other combination from 1,000+ 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.