Check availability as PR review plans change
When a reviewer is added or removed from a football-related PR, make a player availability follow-up easy to keep in view.
Trigger
GitHub Pull Request Reviewers Changed
Triggers when the list of requested reviewers (users or teams) for a pull request changes — for example when a reviewer is added, removed, or re-requested. The payload includes the full current reviewer list (users and teams with details), which reviewers were added, which were removed, and the previous reviewer list for reference.
Action
Get Injuries
Tool to get injured or suspended players. use when you need a list of sidelined players filtered by league, season, fixture, team, player, date, ids, or timezone.
Why this helps
A change in review plans can distract from a related player availability question that still needs an answer.
- Connect reviewer changes to relevant availability research
- Check injury and suspension records from PR context
- Keep sports follow-up visible during review changes
Setup
Build it in a few focused steps.
- 1Connect GitHub and Api Sports once in the Notis portal.
- 2Create an automation and describe how pull request context should guide the availability check.
- 3Pick the GitHub Pull Request Reviewers Changed trigger.
- 4Choose where run reports should go.
- 5Test with one real reviewer change on a football-related PR.
Questions about this workflow
Does the reviewer list identify the players?
No. Use football context in the PR to identify a player, team, or fixture. Reviewer changes alone do not establish player availability.
What can the availability check include?
The Get Injuries action can retrieve injured or suspended players using filters such as league, season, fixture, team, player, or date.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Api sports. A trigger fires from one place; an action lands in another.
GitHub triggers
Api sports actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Coaches
Tool to fetch coaches and their career history. use when you need coach info by id, team filter, or name search.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Countries
Tool to fetch available countries for league queries. use when filtering by name, code, or search string before retrieving leagues.
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.
Get Fixtures
Tool to retrieve football fixtures/matches. use when filtering fixtures by id, date, league, season, team, or date ranges to get upcoming or past matches.
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.
Get fixtures events
Tool to get events (goals, cards, substitutions, var, etc.) from a fixture. use when you need detailed event data after confirming the fixture id.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Get Head-to-Head Fixtures
Tool to get head-to-head fixtures between two teams. use after determining team ids to compare their direct match history.
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.
Get Fixture Lineups
Tool to retrieve starting xi and substitutes for a fixture. use after confirming fixture id; optionally filter by team, player, or section (startxi/substitutes). lineups appear ~20-40 minutes before kickoff for supported competitions.
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.
Get fixtures players
Tool to get player statistics from a fixture. use when you need detailed per-player stats for a specific match. optionally filter by team.
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.
Get Fixtures Rounds
Tool to get the rounds for a league or cup. use after confirming league and season to retrieve available round identifiers (optionally with dates) for filtering fixtures.
Connect any two apps with Notis in the middle.
GitHub and Api sports, 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 Api sports.