Free n8n workflow templates for tennis data

Live score alerts to Telegram

Plan

Free plan

Runs

Every 20 minutes

Sends to

Telegram

Uses

72 requests a day, plus a few for each match awaiting its result

Get a Telegram message when a player you follow goes on court and at the end of each set. When the match ends, the message has the final score. The workflow polls the live list every 20 minutes and compares it with the last run. A score you already have is never sent twice. Club organisers and coaches can follow a few players this way without watching a scores page.

HTTP Request version (JSON), Live score alerts to TelegramCommunity node version (JSON), Live score alerts to Telegram

Full-size screenshots: HTTP Request version, community node version.

How to set it up

1. Create the API key credential described above and select it on every node that calls Live Tennis API.
2. Create a Telegram bot with @BotFather and add a Telegram credential with its token.
3. In Config, set followedPlayerIds and telegramChatId.
4. Activate the workflow. It only remembers the last run while it is active, not in manual test runs.

Daily order of play to Discord

Plan

Free plan

Runs

Every morning at 7

Sends to

Discord

Uses

about four requests a day

Post one Discord message each morning with the matches your players have in the next 24 hours, with start times in your own time zone. It matches players on id where the schedule has one and on surname where it has only a name. That way qualifying matches still show up. A fan server or a fantasy league can share one schedule like this.

HTTP Request version (JSON), Daily order of play to DiscordCommunity node version (JSON), Daily order of play to Discord

Full-size screenshots: HTTP Request version, community node version.

How to set it up

1. Create the API key credential described above and select it on every node that calls Live Tennis API.
2. Create a webhook in your Discord server (Server settings, Integrations, Webhooks) and add a Discord Webhook credential with its URL.
3. In Config, set followedPlayerIds, followedNames and timezone.
4. Run it once to check the message, then activate it.

Weekly ranking changes by email

Plan

Free plan

Runs

Every Monday at 9

Sends to

Email (SMTP)

Uses

one request per player each week

Every Monday, get a short email on how the players you follow moved in the ranking. It shows places gained or lost and points won or dropped, biggest moves first. Players who entered or left the ranking are named too. If you track a short list of players, you get the week in one email instead of looking each one up.

HTTP Request version (JSON), Weekly ranking changes by emailCommunity node version (JSON), Weekly ranking changes by email

Full-size screenshots: HTTP Request version, community node version.

How to set it up

1. Create the API key credential described above and select it on every node that calls Live Tennis API.
2. Add an SMTP credential for the sending address.
3. In Config, set followedPlayerIds, emailTo and emailFrom.
4. Activate it. The first run records a baseline, and changes show from the second week.

Finished matches to Google Sheets

Plan

BASIC plan or above

Runs

Every day at 6 UTC

Sends to

Google Sheets

Uses

three to eight requests a day

Keep a Google Sheet of every finished match: date, tour, level, tournament, round, surface, players, winner, set scores and outcome. Each morning the workflow asks for the completed matches that changed since its last run, so a late result or a corrected one still arrives. It adds or updates one row per match, keyed on match_id, so a repeat never makes a duplicate. It suits a model's training log or a results newsletter.

HTTP Request version (JSON), Finished matches to Google SheetsCommunity node version (JSON), Finished matches to Google Sheets

Full-size screenshots: HTTP Request version, community node version.

How to set it up

1. Create the API key credential described above and select it on every node that calls Live Tennis API.
2. Add a Google Sheets OAuth2 credential.
3. Create a tab named Results whose first row is the column list below.
4. In Config, set spreadsheetId. Leave tour empty for every tour, or set atp, wta, challenger or itf.
5. Run it once, check the rows, then activate it.

The first row of the Results tab:

match_id, date, tour, level, tournament, round, surface, draw, player1, player2, winner, score, outcome, result_version, updated_at

Break-point alerts to Slack

Plan

ULTRA plan

Runs

A signed webhook from Live Tennis API

Sends to

Slack

Uses

one request for every break-point event on any live match

Post to a Slack channel the moment a break point comes up in a match of a player you follow. A second message says whether the game ended in a hold or a break. Live Tennis API sends each event as a signed webhook, so nothing polls. The workflow checks the HMAC signature and the timestamp before it reads the match. It suits a trading desk or a live blog that reacts to the points that swing a match.

HTTP Request version (JSON), Break-point alerts to SlackCommunity node version (JSON), Break-point alerts to Slack

Full-size screenshots: HTTP Request version, community node version.

How to set it up

1. Create the API key credential described above and select it on every node that calls Live Tennis API.
2. Check that the API sends the X-LTAPI-Signature-V1 header. The workflow verifies only that header, so before that release every delivery stops at the check.
3. Create a Crypto credential with any temporary HMAC secret and select it on Sign the time and the raw body. n8n will not activate the workflow without it.
4. Add a Slack credential, then set followedPlayerIds and slackChannel in Config.
5. Activate the workflow and copy the webhook node's production URL into Webhook URL.
6. Run the bottom branch once. Replace the temporary secret in the Crypto credential with the signing secret from its output.