Keep track of stars on research-linked repositories
Use one scheduled run to refresh company context and check star status for repositories you supply.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Check if repo starred by auth user
Use to determine if the authenticated user has starred a specific github repository, which is confirmed by an http 204 status (resulting in an empty dictionary in the response data); the action fails (e.g., http 404) if the repository is not starred or does not exist.
Why this helps
It is easy to forget whether you have saved a repository tied to a company you are researching.
- Check a known repository's star status without opening GitHub.
- Pair repository tracking with an existing company research routine.
- Get the result in a scheduled run report.
Setup
Build it in a few focused steps.
- 1Connect Bigdata.com MCP and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3Tell Notis which companies to research and provide the corresponding GitHub repository names to check.
- 4Choose a recurring schedule and select where run reports should go.
- 5Test with one real company and repository.
Questions about this workflow
Can Bigdata.com identify the right GitHub repository automatically?
Do not assume it can. Supply the repository names or another reliable company-to-repository reference in your instruction.
Will this workflow star a repository if it is not starred?
No. It checks whether the authenticated user has starred the specified repository and reports the result.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Bigdata.com MCP to GitHub. A trigger fires from one place; an action lands in another.
Bigdata.com MCP 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.
Bigdata.com MCP 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.