Handle repository access requests in GitHub
Send an access request to Notis with the repository and GitHub user. Notis can add them as a collaborator.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
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.
Why this helps
Repository access requests can sit in a chat or inbox while someone still needs to make the GitHub change.
- Move access requests into the GitHub collaboration flow.
- Add a collaborator or update their permission when already present.
- Reduce manual follow-up on routine repository access.
Setup
Build it in a few focused steps.
- 1Connect Botsonic and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name it.
- 3Describe in one instruction how to identify the repository and user in an access request and add that user as a collaborator.
- 4Pick the webhook trigger and choose where run reports go.
- 5Test with one real access request and review the report.
Questions about this workflow
Does this always set a permission level?
The action applies the permission field for organization-owned repositories. Personal repositories default to push and ignore that field.
Can it update an existing collaborator?
Yes. The action adds the user or updates their permission if they are already a collaborator.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Botsonic to GitHub. A trigger fires from one place; an action lands in another.
Botsonic 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.
Botsonic 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.