Keep a GitHub follow relationship check on your schedule
Ask Notis to revisit a relevant GitHub relationship periodically and report the status in your chosen channel.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
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
Small recurring checks tend to be forgotten when they live in memory instead of a routine.
- Turn an occasional lookup into a repeatable check.
- Receive a concise status report without reopening GitHub.
- Keep the check tied to a schedule that fits your process.
Setup
Build it in a few focused steps.
- 1Connect GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3Tell Notis the GitHub username and target user to check and how to report the result.
- 4Choose a recurring schedule and select where run reports should go.
- 5Test with one real pair of users and confirm the status report.
Questions about this workflow
Does the action modify who follows whom?
No. It only checks whether the specified user follows another user.
What if one username is invalid?
The action returns a 404 if the relationship is false or the users are invalid.
Can I check more than one pair?
You can describe multiple pairs in the instruction, but provide the usernames for each relationship you want Notis to check.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Alchemy to GitHub. A trigger fires from one place; an action lands in another.
Alchemy 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.
Alchemy 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.