Act on verified abuse without repeating the investigation
After Botpress captures evidence and your required human approval, Notis blocks the specified user from the GitHub organization and reports the action.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Block a user from an organization
Blocks an existing github user from an existing organization, preventing their contributions, collaboration, and forking of the organization's repositories.
Why this helps
Serious abuse cases demand focused action, but repeating usernames, evidence checks, and organization navigation increases stress and the chance of delay.
- Executes a verified moderation decision promptly
- Keeps human approval as an explicit condition
- Prevents further organization contributions, collaboration, and forking by the blocked user
Setup
Build it in a few focused steps.
- 1Connect the moderation Botpress workspace and GitHub organization to Notis.
- 2Write an automation prompt requiring a verified abuse verdict and named human approval before blocking the specified GitHub user.
- 3Use an incoming webhook trigger and choose a private channel for action reports.
- 4Test the full flow with a safe test account and a controlled organization.
Questions about this workflow
Should this run without human review?
For a consequential access action, require explicit human approval in the Botpress flow and repeat that condition in the Notis automation prompt.
What does an organization block do?
It prevents the specified GitHub user from contributing to, collaborating with, or forking repositories in the organization.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Botpress to GitHub. A trigger fires from one place; an action lands in another.
Botpress 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.
Botpress 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.