Bring match statistics into PR follow-up
When pull request activity points to a football match, let Notis find the fixture and fetch its available statistics.
Trigger
Pull Request Event
Triggered when a pull request is opened, closed, or synchronized.
Action
Get fixture statistics
Tool to get statistics for a fixture. use when you need detailed match stats (shots, fouls, possession, cards, passes, etc.), optionally filtered by team, statistic type, or including halftime data.
Why this helps
Match data mentioned alongside code work can take several searches to verify and compare.
- Retrieve fixture statistics from relevant PR context
- Avoid a separate manual match data search
- Keep match analysis close to the code discussion
Setup
Build it in a few focused steps.
- 1Connect GitHub and Api Sports once in the Notis portal.
- 2Create an automation and describe how PR context should identify a fixture and its statistics.
- 3Pick the Pull Request Event trigger.
- 4Choose where run reports should go.
- 5Test with one real pull request event that includes a match reference.
Questions about this workflow
Which statistics can be retrieved?
Api Sports can return fixture statistics such as shots, fouls, possession, cards, and passes, depending on the fixture data available.
What if the pull request has no match reference?
The instruction should ask Notis to report that it lacks enough information to identify a fixture rather than guess.
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.