Check GitHub access against Bika requests
See whether requested collaborators have access without checking each repository by hand.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Check if a user is a repository collaborator
Checks if a user is a collaborator on a specified github repository, returning a 204 status if they are, or a 404 status if they are not or if the repository/user does not exist.
Why this helps
It is easy to lose track of whether a GitHub access request was completed after it leaves the Bika queue.
- Checks the collaborator status for specified users and repositories.
- Helps identify requests that may still need attention.
- Summarizes results in the selected report channel.
Setup
Build it in a few focused steps.
- 1Connect Bika.ai and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, or tell Notis from any channel.
- 3Ask Notis to check whether each user and repository in the supplied Bika access records has collaborator status.
- 4Choose the schedule trigger and select where run reports should go.
- 5Test with one real record for a known collaborator and one for a user without access.
Questions about this workflow
Does a not-found response prove the person is not a collaborator?
A 404 can mean the user or repository does not exist, as well as indicating no collaborator status. Have Notis report uncertainty rather than treating every 404 as definitive.
Does this grant access?
No. This action checks collaborator status; it does not add collaborators.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Bika.ai to GitHub. A trigger fires from one place; an action lands in another.
Bika.ai 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.
Bika.ai 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.