Make waiting interview follow-up visible
A scheduled review can flag existing GitHub candidate issues when the interview status shows the next step is waiting.
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
Candidate follow-up is easy to miss when status checks depend on someone remembering to review them.
- Review waiting interviews on a predictable cadence.
- Make follow-up issues easier to spot in GitHub.
- Reduce reliance on memory for routine checks.
Setup
Build it in a few focused steps.
- 1Connect Async interview and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name it.
- 3Describe which interview statuses count as waiting and how to find and label their existing GitHub issues.
- 4Pick a recurring schedule and choose where run reports go.
- 5Test with one real waiting interview and its existing issue.
Questions about this workflow
Can Notis know how long an interview has been waiting?
Only if Async interview returns the needed timing information or you provide a baseline in the instruction.
Will it create a follow-up issue?
No. It labels an existing issue that your instruction tells Notis how to identify.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Async interview to GitHub. A trigger fires from one place; an action lands in another.
Async interview 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.
Async interview 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.