Restore GitHub access when employees return
Make the access review after an extended absence a clear, trackable step in the return-to-work process.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
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
Employees returning from leave may find that access needs have changed or that repository access was removed without a restoration task.
- Adds a deliberate access review to return planning
- Uses policy rules to determine which repositories apply
- Reports collaborator additions for confirmation
Setup
Build it in a few focused steps.
- 1Connect BambooHR and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name it.
- 3Describe which BambooHR return records qualify, which repositories apply, and the collaborator access level.
- 4Pick a recurring schedule, choose where run reports go, and save the automation.
- 5Test with one real return record and confirm the access change.
Questions about this workflow
Does this restore every permission the employee had before leave?
Only if you provide the needed repository and permission rules. BambooHR may not include a history of GitHub access.
Can the workflow wait until the employee's return date?
Use the scheduled trigger and tell Notis which return date qualifies for the check.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Bamboohr to GitHub. A trigger fires from one place; an action lands in another.
Bamboohr 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.
Bamboohr 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.