Move approved repository access requests into GitHub
Give Notis the person, repository, and approval context from intake, with a clear instruction for the access change to make.
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
Access requests can stall between approval and the GitHub update that lets someone get started.
- Move an approved request from intake to repository access.
- Use approval context you provide to guide the change.
- Report on the GitHub update.
Setup
Build it in a few focused steps.
- 1Connect Celigo and GitHub once in the Notis portal.
- 2Create an automation in Automations, then New Automation, and give it a name.
- 3Describe how the request and approval context should add or update a collaborator in one instruction.
- 4Choose a webhook trigger and where run reports should go.
- 5Test with one real example and confirm the report.
Questions about this workflow
Can Notis decide whether the request is approved?
Only if the approval signal is available in the request or other context provided to Notis. State how to interpret that signal in the instruction.
Will a permission choice be honored on my personal repository?
The permission field applies to organization-owned repositories. Personal repositories default to push and ignore the permission field.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Celigo to GitHub. A trigger fires from one place; an action lands in another.
Celigo 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.
Celigo 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.