Check repository collaborator status after an access change request
Keep access follow-up grounded in the requested user and repository with a direct collaborator status check in Notis.
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 changes across connected services are easy to lose track of when each system has its own separate review step.
- Check the relevant GitHub collaborator relationship.
- Keep the access request context in the report.
- Avoid switching contexts to verify a single status.
Setup
Build it in a few focused steps.
- 1Connect BunnyCDN and GitHub once in Notis.
- 2Create an automation in Automations, New Automation, and give it a name and prompt.
- 3Tell Notis to check collaborator status for the GitHub username and repository named in the BunnyCDN access change request.
- 4Choose the webhook trigger and where run reports should go.
- 5Test with one real request and verify the account and repository checked.
Questions about this workflow
Does a collaborator check confirm access to BunnyCDN too?
No. It checks GitHub repository collaborator status only.
Can this grant or revoke GitHub access?
No. The listed action checks status and does not change collaborator access.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Bunnycdn to GitHub. A trigger fires from one place; an action lands in another.
Bunnycdn 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.
Bunnycdn 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.