Close the loop on GitHub access requests
Send the access handoff to Notis and get a direct collaborator status check for the person and repository named in the conversation.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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
Access requests create repeated follow-up when nobody checks whether a person already has repository access.
- Confirm collaborator status from a conversation handoff
- Reduce duplicate access requests
- Keep the result visible in a report channel
Setup
Build it in a few focused steps.
- 1Connect Botbaba and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3Tell Notis to check whether the user and repository identified in the submitted access conversation are collaborators and summarize the result.
- 4Choose the webhook trigger and select where run reports should go.
- 5Test with one real access handoff.
Questions about this workflow
Does the check add access when missing?
No. It only checks collaborator status.
How does GitHub indicate that access exists?
A 204 response means the user is a collaborator; a 404 means they are not or the user or repository cannot be found.
Why use this after a chat?
It closes the loop on access discussions with a status check before creating another request.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Botbaba to GitHub. A trigger fires from one place; an action lands in another.
Botbaba 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.
Botbaba 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.