Restore clear ownership after an absence
Use a scheduled check to act on return and coverage details, so the right person is attached to the work that needs attention.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Add assignees to an issue
Adds or removes assignees for a github issue; changes are silently ignored if the authenticated user lacks push access to the repository.
Why this helps
Temporary coverage can persist after someone returns, leaving issue ownership unclear.
- Review return context alongside current issue ownership.
- Update issue assignees using explicit coverage instructions.
- Make handoffs easier to review in the team's existing tracker.
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 supplied return and coverage details and update assignees on the named GitHub issue.
- 4Choose a recurring schedule as the trigger and select where run reports should go.
- 5Test with one real return example and confirm the intended assignee is updated.
Questions about this workflow
Will it know who should own the work after a return?
The intended assignee must be stated in your instruction or included in available context. The action does not infer a coverage policy.
Can one review update more than one issue?
You can instruct Notis to handle multiple supplied issue references, provided each issue and intended assignee are clear.
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.