Protect branches during planned absences
Make coverage decisions explicit in GitHub before you step away from the calendar.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Add user access restrictions
Sets/replaces list of users allowed to push to a protected branch; usernames (e.g., `["user1"]`) must be a json array in request body (not schema parameters), an empty array `[]` removes all restrictions.
Why this helps
Planned time away creates uncertainty about who can safely push urgent changes.
- Clarifies temporary coverage
- Reduces urgent access confusion
- Supports healthier time away
- Keeps protected branches controlled
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 planned absence webhook confirms temporary coverage, set the specified protected GitHub branch user access list to the approved maintainers.
- 4Select an incoming webhook trigger, choose the run-report channel, and test with one planned absence.
Questions about this workflow
Does it remove access permanently?
The action replaces the current list, so use a matching return-to-work automation or restore the approved list afterward.
Can this run only for urgent coverage?
Yes. Require an explicit approved coverage list in the incoming event.
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.