Verify personal GitHub safety actions
A recurring check keeps protective actions from fading into the background.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Check if a user is blocked by the authenticated user
Checks if the specified github user is blocked by the authenticated user; a 204 no content response indicates the user is blocked, while a 404 not found indicates they are not.
Why this helps
Once a user is blocked, it is easy to assume the setting remains correct without checking.
- Confirms protective settings remain active
- Reduces memory-dependent security follow-up
- Reports only the accounts needing review
Setup
Build it in a few focused steps.
- 1Connect Wachete and GitHub to Notis once through the portal.
- 2Create an automation in the portal or ask Notis to create it in plain language.
- 3Use this instruction: Each month, check whether the specified users remain blocked by my GitHub account and report any mismatch.
- 4Pick a recurring schedule, choose the channel for run reports, and test with one real user.
Questions about this workflow
Does this change block settings?
No. It checks the current status and reports exceptions.
Can the list change over time?
Yes. Update the instruction or provide an approved Wachete alert with the current list.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Wachete to GitHub. A trigger fires from one place; an action lands in another.
Wachete 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.
Wachete 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.