Keep GitHub teams in step with department transfers
Make an employee's new team placement easier to carry through to the tools they use every day.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Add or update team membership for a user
Adds a github user to a team or updates their role (member or maintainer), inviting them to the organization if not already a member; idempotent, returning current details if no change is made.
Why this helps
Department transfers can leave people in the wrong GitHub team after their responsibilities change.
- Connects department updates to team membership review
- Applies organization team rules consistently
- Creates a report for transfer follow-up
Setup
Build it in a few focused steps.
- 1Connect BambooHR and GitHub once in the Notis portal.
- 2Create an automation in Automations and give it a descriptive name.
- 3Describe qualifying department transfers, the destination GitHub team, and any membership changes to apply.
- 4Pick a recurring schedule, choose where run reports go, and save the automation.
- 5Test with one real transfer record and review the membership change.
Questions about this workflow
Will this remove the employee from their previous GitHub team?
Describe whether the old team should be removed. The action can add or update membership for a specified team; it does not itself discover the old team.
Can a department name determine the GitHub team?
Yes, if you provide a clear department-to-team rule and the needed department data is present.
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.