Keep interview briefs aligned with product documentation
When the README changes, your candidate story and interview context can stay current too.
Trigger
GitHub Repository README Changed
Triggers when the README file in a specific repository directory changes. Monitors the README in a configurable directory and branch/tag/commit. The payload includes the current README metadata (filename, path, SHA, size, URLs), the previous and current git blob SHAs, and a list of which tracked fields changed.
Action
Update Job
Tool to update an existing interview job. use when you need to modify job details after creation.
Why this helps
Documentation evolves but interview briefs often remain based on older product positioning.
- Keep candidate-facing context consistent.
- Reduce manual review of documentation changes.
- Align interviews with the latest product direction.
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 conversationally.
- 3Describe the outcome: update the relevant Async interview job when the repository README changes, summarizing the documentation change that affects role or product context.
- 4Pick the GitHub README changed trigger and choose the channel for run reports.
- 5Test with one README update.
Questions about this workflow
Can the update focus on product positioning?
Yes. Tell Notis to focus on the sections or implications relevant to the interview job.
Does this require copying the README manually?
No. Notis uses the trigger context and your 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.