Mark technical screening progress on GitHub issues
Keep a hiring issue's status visible where the engineering team already tracks the work.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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
Screening progress can sit in Ashby while the related GitHub hiring issue looks untouched, forcing people to reconcile two places.
- Keep the GitHub hiring issue aligned with a supplied screening milestone.
- Let Notis interpret the incoming update and apply the relevant label.
- Labels that do not yet exist can be created by the GitHub action.
Setup
Build it in a few focused steps.
- 1Connect Ashby and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a clear name.
- 3Tell Notis to apply the supplied screening-stage label to the related GitHub issue when the Ashby update arrives.
- 4Pick the webhook trigger and choose where run reports should go.
- 5Test with one real screening update and verify the repository, issue, and label.
Questions about this workflow
What starts the workflow?
A Notis webhook starts it when an HTTP request carries the Ashby screening update. Ashby has no trigger events listed here.
How does Notis know which issue to update?
The webhook request or instruction must provide enough information to identify the GitHub repository and issue.
Can the label be new?
Yes. The GitHub action adds labels to an issue, and labels that do not already exist are created.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Ashby to GitHub. A trigger fires from one place; an action lands in another.
Ashby 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.
Ashby 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.