Find bet types for your odds research view
Create a view for odds research and let Notis find the available pre-match bet types.
Trigger
View Created
Triggers when a new Notion view is created. Fires workspace-wide. The payload includes `data.view_type` (`table`, `board`, `gallery`, `calendar`, `list`, `timeline`, `gantt`) and `data.parent` pointing at the view's tree parent (typically the teamspace), so customers can filter downstream.
Action
Get Odds Bets
Tool to get all available pre-match bet types. use when filtering by bet id or searching bet names before fetching odds.
Why this helps
Searching for the right bet type adds friction before a useful odds query can begin.
- Find available bet types before running an odds query.
- Avoid repeatedly searching for bet names and identifiers.
- Keep research setup close to the Notion view that organizes it.
Setup
Build it in a few focused steps.
- 1Connect Notion and Api sports to Notis once in the portal.
- 2Create an automation in the portal or ask Notis to find available pre-match bet types when an odds research view is created.
- 3Describe in one plain-language instruction which bet names or search terms matter to your research.
- 4Pick the Notion View Created trigger, choose a report channel, and test by creating a real research view.
Questions about this workflow
What does this action discover?
Api sports Get Odds Bets returns available pre-match bet types and can filter by bet ID or search names.
Does this fetch odds values?
No. It discovers bet types to help you filter a separate odds lookup.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Api sports. A trigger fires from one place; an action lands in another.
Notion 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.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
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.
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.
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 Comment
Triggers when a new comment is added to a specified Notion block or page.
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.
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.
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.
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.
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.
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 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.
Notion 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.