Keep absence-related engineering follow-ups visible
Give recurring absence checks a clear home in GitHub, so the team can spot and track work that needs attention.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Add labels to an issue
Adds labels (provided in the request body) to a repository issue; labels that do not already exist are created.
Why this helps
Absence changes can leave related engineering work buried in chat or forgotten during handoffs.
- Review absence updates on a predictable schedule.
- Label relevant existing issues for easier scanning.
- Reduce manual reminders across HR and engineering.
Setup
Build it in a few focused steps.
- 1Connect Breathe HR and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation.
- 3Tell Notis to review recent absence updates and add an agreed label to matching existing GitHub issues, using supplied issue references or context.
- 4Choose a recurring schedule as the trigger and select where run reports should go.
- 5Test with one real absence update and confirm the correct issue receives the label.
Questions about this workflow
Does this create a new GitHub issue for each absence?
No. This workflow adds labels to relevant existing issues. Supply the issue reference or matching context in the instruction.
Can it determine which engineering task relates to an absence by itself?
Only when the returned Breathe HR data or your instruction provides enough context to match the work. Add the relevant issue references or matching guidance.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Breathe HR to GitHub. A trigger fires from one place; an action lands in another.
Breathe HR 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.
Breathe HR 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.