← All N8N workflows
Data & databasesAirtableHTTP RequestMergeSchedule Trigger

Automating Betting Data Retrieval with TheOddsAPI and Airtable

Configured with Airtable, HTTP Request, Schedule Trigger. Review the connections and setup before adapting this template.

Workflow preview
TriggerMorning Trigger To PullData At 7:00amSchedule TriggerTriggerEvening Trigger To PullData At 11:00pmSchedule TriggerWeb / APIRetrieve Data OfUpcoming Sport Events…HTTP RequestData storeCreate Records OfUpcoming Events For The…AirtableWeb / APIRetrieve Sport ResultsData At The End Of The…HTTP RequestTransformCombine Sport ResultsWith Upcoming Events…MergeData storeUpdate Table RecordsWith Scores And Results…Airtable

Node categories in this workflow

  • Trigger
  • Web / API
  • Data store
  • Transform

Icons describe general node roles, inferred from node types. Inspect the parameters for the configured action.

Drag to pan; use + and − to zoom. Reconstructed from the exported node positions; nothing runs here. Dashed lines represent non-main connections. Full node names and notes appear below.

How it works

The exported workflow contains the following configured nodes. Their connections are shown above; inspect the JSON for the complete logic, expressions, and external actions.

Workflow node names, types, and operations
NodeCategoryTypeOperation
Morning Trigger To Pull Data At 7:00amTriggerSchedule TriggerSee node parameters
Evening Trigger To Pull Data At 11:00pmTriggerSchedule TriggerSee node parameters
Retrieve Data Of Upcoming Sport Events For The DayWeb / APIHTTP RequestSee node parameters
Create Records Of Upcoming Events For The DayData storeAirtablecreate
Retrieve Sport Results Data At The End Of The DayWeb / APIHTTP RequestSee node parameters
Combine Sport Results With Upcoming Events Records By Matching IDTransformMergeSee node parameters
Update Table Records With Scores And Results For Sport EventsData storeAirtableupdate

Setup

  1. Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
  2. Connect your own credentials through n8n’s credential store. Replace REPLACE_WITH_* values with your resource identifiers.
  3. Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
  4. Run with synthetic data and harmless destinations. Enable triggers only after checking the actual outputs.

Requirements

An n8n instance with the listed node types and compatible versions. Service-connected workflows may require accounts, credentials, or paid APIs.

Credential types declared in the source

  • airtableTokenApi
  • httpHeaderAuth

Workflow notes

Sticky Note

The following triggers start the workflow at the Start of the day and the End of the day. Times can be adjusted to user's preference.

Sticky Note1

Once activated, HTTP Requests pulls the upcoming data for the sport of the user's choosing. The following is set for Ice Hockey. More documentation can be found within the link below:

https://the-odds-api.com/liveapi/guides/v4/#get-events

If you would like to add more data such as the sport books or odds, you can find documentation within the documentation below:

https://the-odds-api.com/liveapi/guides/v4/#get-odds

Once the data is pulled, the records are created within the Airtable.

Sticky Note2

At the end of the day, the Schedule Trigger will activate a HTTP request for the scores of the events. This is set for Ice Hockey but can be adjusted for the user's preference.

After the data is pulled, it will merge the data with upcoming events to combine the results matching the id.

The Airtable is then updated with the result records. This can be adjusted to pull in sports odds or the different sports book data.

Automating Betting Data Retrieval with TheOddsAPI and Airtable

Automating Betting Data Retrieval with TheOddsAPI and Airtable

Purpose and structure

This folder contains the Automating Betting Data Retrieval with TheOddsAPI and Airtable workflow. Its executable nodes use airtable, httpRequest, merge, scheduleTrigger. The table and connection map below are derived from the JSON, not an inferred guarantee of behavior.

Setup

Import inactive. Configure your own credentials and replace REPLACE_WITH_* values. Review external destinations and Code nodes before running.

Entry points

Morning Trigger To Pull Data At 7:00am, Evening Trigger To Pull Data At 11:00pm

Verification

Sanitized source candidate; not runtime-tested. This overview is generated from node metadata. Read the folder README for the connection map, credential types, and license.

Attribution

https://github.com/Zie619/n8n-workflows/blob/94007c1445d9258a7da116646b79473e7c7c3282/workflows/Http/1111_HTTP_Schedule_Automation_Webhook.json MIT; preserve source notices.

More in Data & databases