Check a GitHub Follow Relationship on Request
Send Notis two usernames and get a GitHub follow status check in the report channel you choose.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Check if a user follows another user
Checks if a github user `username` follows `target user`; returns a 204 http status if true, 404 if not or if users are invalid.
Why this helps
Manually checking profile relationships can turn a small research task into a distracting detour.
- Request a specific follow relationship check when needed.
- Keep the result with the rest of the request context.
- Avoid manually navigating between profiles.
Setup
Build it in a few focused steps.
- 1Connect Api labz and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3Tell Notis in one instruction to check whether each submitted GitHub user follows the specified target user.
- 4Choose the notis_webhook trigger and a report channel.
- 5Test using two real GitHub usernames.
Questions about this workflow
Does the workflow follow the target user?
No. It checks whether one user follows another and does not change either account.
What does a not-found response mean?
GitHub may return not found when the relationship is false or when either username is invalid.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Api labz to GitHub. A trigger fires from one place; an action lands in another.
Api labz 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.
Api labz 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.