Keep security hiring context visible when secrets are detected
A secret alert can change the urgency of the expertise your team needs.
Trigger
New Secret Scanning Alert Detected
Triggers when a new secret scanning alert is detected in a GitHub repository. Monitors open secret scanning alerts and fires an event for each newly detected alert. Supports filtering by secret type (e.g., personal access tokens, AWS keys) and by token validity status (active, inactive, unknown). The payload includes the alert number, secret type, validity status, resolution state, timestamps, URLs, and flags for push protection bypass, public exposure, and multi-repo detection.
Action
Update Job
Tool to update an existing interview job. use when you need to modify job details after creation.
Why this helps
Security incidents demand immediate attention, while hiring plans remain disconnected from the response.
- Make security priorities visible in hiring workflows.
- Reduce missed follow-up after sensitive alerts.
- Support faster alignment between engineering and hiring.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Async interview to Notis once through the portal.
- 2Create the automation in the portal or ask Notis to set it up conversationally.
- 3Describe the outcome: update the relevant Async interview job when a new GitHub secret scanning alert is detected, including urgency and security follow-up context.
- 4Pick the GitHub new secret scanning alert trigger and choose a reporting channel.
- 5Test with one alert using a safe test scenario.
Questions about this workflow
Can sensitive alert details be minimized?
Yes. Tell Notis to include only the context needed for hiring follow-up.
Can this update a security role's interview job?
Yes. Identify the relevant job in the plain-language instruction.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Async interview. A trigger fires from one place; an action lands in another.
GitHub triggers
Async interview actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Delete Job
Tool to delete an interview job. use when you need to permanently remove a job after reviewing responses.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
List Jobs
Tool to retrieve a list of all interview jobs. use when you need to display or manage existing jobs.
New Workflow Artifact Created
Triggers when a new workflow artifact is created in a GitHub repository. Monitors for newly created GitHub Actions workflow artifacts. Optionally filters by artifact name to restrict monitoring to specific artifacts.
Update Job
Tool to update an existing interview job. use when you need to modify job details after creation.
Branch Changed
Triggers when a GitHub branch changes. Monitors a specific branch for: - New commits pushed (head commit SHA changes) - Protection status toggled (branch becomes protected or unprotected) - Protection settings changed, including: required status checks and their enforcement level, admin enforcement, required pull request reviews (dismiss stale reviews, code owner reviews, approving review count, last push approval), required linear history, force push allowance, deletion allowance, conversation resolution, branch locking, and fork syncing.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Check Run Status / Conclusion Changed
Triggers when a specific GitHub check run changes its status or conclusion. Monitors a single check run for changes to: status (queued, in_progress, completed, etc.), conclusion (success, failure, neutral, cancelled, skipped, timed_out, action_required), started_at, and completed_at.
Check Suite Status / Conclusion Changed
Triggers when a GitHub check suite changes its status or conclusion for a given ref. Monitors all check suites associated with a git reference (branch, tag, or commit SHA) for changes to status (queued, in_progress, completed, etc.) and conclusion (success, failure, neutral, cancelled, skipped, timed_out, action_required, startup_failure, stale). Optionally filters by GitHub App ID.
New Code Scanning Alert Created
Triggers when a new code scanning alert is created in a repository. Fires an event for each newly created code scanning alert detected in the configured repository. Alerts can be filtered by Git reference, scanning tool, state, and severity. The payload includes the alert number, rule details, tool information, state, severity, and the location of the most recent instance.
Connect any two apps with Notis in the middle.
GitHub and Async interview, 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 Async interview.