Start every new branch with returning-production context
A branch kickoff can bring the baseline data needed for focused planning.
Trigger
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Action
Returning Production by Team
Tool to fetch Bill Connelly–style returning production splits by team and season. Use when evaluating returning offense, defense, and overall production for teams in a given season.
Why this helps
New initiatives begin with scattered assumptions and no shared starting point.
- Improves project kickoff context
- Reduces repeated baseline research
- Makes early decisions more grounded
Setup
Build it in a few focused steps.
- 1Connect GitHub and College football data to Notis once.
- 2Create the automation in the portal or ask Notis to set it up in plain language.
- 3Use this instruction: When a new GitHub branch is created, retrieve returning production metrics for the relevant college football teams and season, then summarize the baseline.
- 4Pick the new branch trigger, choose a channel for run reports, and test with one branch.
Questions about this workflow
Can the branch name identify the team?
Yes. Notis can use the branch name when the instruction tells it to infer context from it.
Can it include offense and defense separately?
Yes. Ask for the split you need.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to College football data. A trigger fires from one place; an action lands in another.
GitHub triggers
College football data actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Advanced Box Score
Tool to retrieve advanced box score metrics for a single college football game. Use after selecting a specific game to access team- and player-level advanced analytics.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Advanced Game Stats
Tool to retrieve advanced team metrics at the game level. Use when detailed offensive and defensive metrics (success rates, explosiveness, havoc) are needed.
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.
Advanced Season Stats by Team
Tool to retrieve advanced season metrics aggregated by team and season. Use after selecting season and team filters.
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.
Betting Lines
Tool to fetch betting lines and totals by game and provider. Use when you need current or historical betting line data filtered by specific criteria.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Composite Team Talent
Tool to fetch composite team talent rankings by season. Use when you need 247Sports team talent composites for specified seasons.
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.
Conference Memberships History
Tool to retrieve historical conference memberships for teams, including years active and division. Use when you need to trace a team's conference history over time.
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.
Divisions by Conference
Tool to list FBS/FCS conference divisions with active years and metadata. Use after specifying an optional season year to filter active divisions.
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 Drive Data
Tool to retrieve drive-level data and results. Use when analyzing detailed drives for specified games after filtering by season, team, or week.
Connect any two apps with Notis in the middle.
GitHub and College football data, 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 College football data.