Start team planning with returning-production data
Create a team planning page and let Notis look up how much production returns for the season.
Trigger
Page Created
Triggers when a new Notion page is created. Customer optionally scopes with at most one of: - data_source_id: new row in this data source - parent_page_id: new sub-page under this page (immediate parent only) With neither set, fires for any new page in the workspace the integration has access to. Notion sends ~60s aggregation latency on most 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
Roster continuity research can be easy to skip when planning starts with a blank page.
- Put returning production near planning notes.
- Reduce lookup effort at the start of a review.
- Keep season context visible for future follow-up.
Setup
Build it in a few focused steps.
- 1Connect both integrations to Notis once.
- 2Create an automation with a plain-language instruction to retrieve returning production for a new team plan.
- 3Select Page Created and scope the trigger to the team-planning data source if desired.
- 4Choose a run-report channel and test with a real plan page.
Questions about this workflow
Which production splits are available?
The action fetches returning offense, defense, and overall production by team and season.
What should the page include?
Include enough team and season context for Notis to identify the relevant lookup.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to College football data. A trigger fires from one place; an action lands in another.
Notion 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.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Advanced Season Stats by Team
Tool to retrieve advanced season metrics aggregated by team and season. Use after selecting season and team filters.
Comment Created
Triggers when a new comment is created in Notion. Optional `page_id` filter scopes to comments on a specific page. When omitted, fires for any new comment in the workspace the integration has access to. Requires the 'Read comments' capability on the Notion integration. If a connection was authorized before that capability was enabled, the user must re-authorize the connection for comment events to flow.
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 Comment
Triggers when a new comment is added to a specified Notion block or page.
Composite Team Talent
Tool to fetch composite team talent rankings by season. Use when you need 247Sports team talent composites for specified seasons.
Database Created
Triggers when a new Notion database (the container) is created. A database is the post-2025-09-03 container that holds one or more data sources. This trigger fires for the container's creation event (`database.created`), distinct from `NOTION_DATASOURCE_CREATED` which fires when a new data source is added to an existing database. Most customers calling Notion's `POST /v1/databases` (the legacy API) or creating a database via the Notion UI will see this event. Adding a new data source to an existing database fires `data_source.created` instead — use `NOTION_DATASOURCE_CREATED` for that. Notion's payload puts `entity.type: "block"` (the container is a `child_database` block in the content tree) and `entity.id` is the database id.
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.
Data Source Created
Triggers when a new Notion data source is created. Fires workspace-wide. The payload's `data.parent` carries the data source's tree parent (typically the teamspace) for downstream filtering. A single template-based database creation can fire multiple `data_source.created` events at once — one per data source the template instantiates.
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.
Data Source Schema Updated
Triggers when a Notion data source's schema is updated. Fires on column add / remove / rename. Payload includes `data.updated_properties: [{id, name, action}]` so consumers can discriminate the kind of change downstream. Optional `data_source_id` filter scopes to schema changes on a single data source. When omitted, fires for any schema change in the workspace the integration has access to. Note: adding a column also fires `page.properties_updated` once per existing row in the data source. Customers wanting a single structural-change signal should use this trigger.
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.
Notion 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.