Apply team repository permissions after decisions
Turn a clear team decision into the exact GitHub access change it calls for.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Add or update team repository permissions
Sets or updates a team's permission level for a repository within an organization; the team must be a member of the organization.
Why this helps
Permission decisions sit in meeting notes while the repository keeps its old access model.
- Reduces permission drift
- Makes decisions operational
- Cuts repeated admin work
- Improves team clarity
Setup
Build it in a few focused steps.
- 1Connect Calendarhero and GitHub to Notis once through the portal.
- 2Create the automation in the portal or ask Notis to create it conversationally.
- 3Use this instruction: When a Calendarhero team decision webhook confirms a repository access change, update that GitHub team's permission level for the named repository.
- 4Select an incoming webhook trigger, choose the run-report channel, and test with one approved decision.
Questions about this workflow
Can it set read, write, or admin?
Yes, the instruction can specify the approved permission level supported by GitHub.
What if the team is not in the organization?
GitHub will report the prerequisite issue, and Notis can surface it in the run channel.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Calendarhero to GitHub. A trigger fires from one place; an action lands in another.
Calendarhero 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.
Calendarhero 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.