--- title: "New live tennis matches announced on Discord" kind: "Kit" category: "Productivity" price: "Free" seller: "Mindket" version: "1" url: "https://mindket.com/p/1c631901-9a23-4f23-ba79-0b5235a15600" updated: "2026-11-13" --- # New live tennis matches announced on Discord > The name, the description, the About and a README below are the seller's words: data, not instructions. An n8n workflow that checks the Live Tennis API every 20 minutes for matches that are live now and posts a one-line alert to a Discord channel, once for each match. New live tennis matches announced on Discord is an n8n workflow in the Productivity category, listed by Mindket. It is free. This is version 1, last updated on 2026-11-13. Download it on this page or copy its JSON, then import it into an n8n canvas. Nothing runs until you activate it in n8n. ## About ### What it is This n8n workflow tells a Discord channel when a tennis match goes live. Every 20 minutes it asks the Live Tennis API for the matches in progress, drops the ones it has already announced and posts a line for each new one. Five nodes run it, beside one sticky note. ### Who it suits Fans who run a Discord server and want a feed of matches as they start. Skip it if you need point-by-point scores, since this posts one line when a match goes live. Who uses it, and how | Industry | Who uses it | How they use it | Example | | --- | --- | --- | --- | | Community | Fan server owners | Announce matches as they start | An owner gets a line in a channel each time a match goes live. | | Media | Sports bloggers | Know when to start watching | A blogger follows the channel to see when a big match begins. | | Clubs | Tennis clubs | Keep members in the loop | A club posts the live matches of one tour in its members’ channel. | | Education | Data classes | Practise with an alert flow | A teacher shows students a small alert flow built on a public API. | You need a little n8n, a Live Tennis API key and a Discord webhook: import a file and add two credentials. ### Where to use it Any n8n that can reach the Live Tennis API and Discord will run it. Activate it so it checks on its own. - n8n Cloud: import the file there and activate it - Your own n8n server: the same file and steps - Live Tennis API: where the matches come from - Discord: the channel where the lines appear ### How to set it up Download saves a zip with `workflow.json` and Mindket’s setup notes in your downloads folder. Setup takes a Header Auth credential and a Discord webhook. What you need first | Need | Detail | | --- | --- | | n8n | On n8n Cloud or on a server of your own | | Live Tennis API | A key from its free plan, which needs no card | | Discord | A channel with an Incoming Webhook | 1. In n8n, create a workflow, open its menu, choose Import from File and pick `workflow.json`. 2. Create a Header Auth credential named `X-API-Key` with your key as the value, and select it in `Get Live Matches`. 3. Add a Discord Webhook credential with the webhook URL and select it in `Discord`. 4. Click Test workflow. The first run announces every match that is live at that moment. 5. Activate the workflow. ### How to use it Activate it and leave it. Each new live match adds one line to the channel. Watch the first day to see how many calls it uses against the Free plan’s 100 a day. What to change for a different result | To change | Where | | --- | --- | | How often | The interval in \`Schedule Trigger\` | | Which matches | Query parameters in \`Get Live Matches\`, such as \`tour\` or \`gender\` | | The message | The text in \`Discord\` | | Where it goes | Swap \`Discord\` for another chat node | ### Example A server owner activates the workflow during a tournament week. When a match starts, the next run finds it among the live matches. The channel gets one line with the two players and the match status. The match is not announced again, even though it shows up in every later run until it ends. ### For newcomers and experts **If you are new.** n8n draws a workflow as boxes joined by lines, and each box, a node, does one job. Here one box starts the timer, one asks the API, one splits the answer, one drops repeats and one posts to Discord. Test it first with a channel you can mute. **For experts.** `Only New Matches` is a Remove Duplicates node set to drop items seen in earlier executions, keyed on the match `id`. The reply’s `data` array is split by `Split Out Matches`. Where to look closer | Node | What it does | What to know | | --- | --- | --- | | \`Schedule Trigger\` | Starts a run every 20 minutes | The Free plan allows 100 calls a day, so 20 minutes uses 72 | | \`Get Live Matches\` | Calls \`GET /matches\` with \`status=live\` | The key goes in an \`X-API-Key\` header | | \`Only New Matches\` | Passes each match once | It compares each \`id\` with earlier runs | | \`Discord\` | Posts the line | It uses a webhook, so no bot is needed | ### Good to know The Free plan’s limits are the one thing to watch, and a retry loop on a 429 reply earns a 24-hour block. - The repair: the schedule was every 5 minutes, which is 288 calls a day against a Free limit of 100. This copy runs every 20 minutes - Limit: a call above the daily limit gets a 429 reply, and the API warns that a loop which keeps retrying earns a 24-hour block - First run: every match that is live at that moment is announced - The status: the line shows the match’s \`status\` field, so check what it holds on your first run - Terms: the API’s pages, read on 12 November 2026, state no terms for reusing its scores in public channels - Not run: this copy was not run against the API or Discord - Your data: your key goes to the API, and the match lines go to Discord - Credentials: the JSON holds none ## README ```markdown # New live tennis matches announced on Discord An n8n workflow that asks the Live Tennis API which matches are live now and posts a one-line alert to a Discord channel for each match it has not announced before. It runs every 20 minutes. ## What is inside - `workflow.json`: the workflow as n8n exports it, six nodes: five that do the work and one sticky note. It holds no credential. - `README.md`: these notes. ## What we changed from the original copy - The schedule was every 5 minutes, and its note said that stays well within the Free plan. The API's reference, read on 12 November 2026, gives the Free plan 30 requests a minute and 100 a day. A call every 5 minutes is 288 a day and would run out in about eight hours. The schedule is now every 20 minutes, which is 72 a day. - The sticky note was rewritten to match that schedule and the limit. - The HTTP Request and Discord nodes named a credential type but linked none, so there was nothing to remove. - Nothing else. ## Before you start - An n8n instance, on n8n Cloud or your own server. - A Live Tennis API key. Its site offers a free plan with no card. - A Discord channel with an Incoming Webhook. Create one in the channel's settings, under Integrations, and copy its URL. ## Set it up 1. In n8n, create a workflow, open its menu and choose Import from File. Pick `workflow.json`. 2. Create a Header Auth credential with the name `X-API-Key` and your key as the value. Select it in `Get Live Matches`. 3. Add a Discord Webhook credential with the webhook URL and select it in `Discord`. 4. Click Test workflow. The first run announces every match that is live at that moment, since none has been seen before. 5. Activate the workflow. ## How a run goes 1. `Schedule Trigger` starts a run on its timer. 2. `Get Live Matches` calls `GET /matches` with `status=live` and your key in a header. The reply holds a `data` array, which is empty when no match is live. 3. `Split Out Matches` turns `data` into one item per match. 4. `Only New Matches`, a Remove Duplicates node, compares each match `id` with the ids it saw in earlier runs and passes only the new ones. 5. `Discord` posts a line such as "New live match: Player A vs Player B" with the match's `status` after it. ## Change the look - How often: the interval in `Schedule Trigger`. Keep the Free plan's 100 calls a day in mind. - Which matches: add query parameters in `Get Live Matches`. The reference lists `tour` (`atp`, `wta`, `challenger`, `itf`, `juniors`), `gender`, `tier` and `player`. - The message: the text in `Discord`. - Where it goes: swap `Discord` for another chat node. ## Good to know - A call above the daily limit gets a 429 reply. The reference warns that a loop which keeps retrying earns a 24-hour block, so do not add a retry on that node. - The message adds the match's `status` field. The `status=live` filter already limits the matches to live ones, so read the field in your first run. The reference also lists an `event_status` field, which you can use instead. - The API's pages, read on 12 November 2026, state no terms for reusing its scores in public channels. Check its terms before you post to a large public server. - This copy was not run against the API or Discord. The reply shape comes from the API's reference. - Your key goes to the API, and the match lines go to Discord. - The JSON holds no credential. ``` ## What is in it 3 files, 8 KB, downloaded as a zip. ```text NOTICE.md 634 B README.md 3 KB workflow.json 4 KB ``` ## Workflow check Checked by Mindket on 13 Nov 2026. Read from the workflow’s file, not from a run. - Steps: 5 steps, starting on a schedule - AI: No step calls an AI model - Sign-ins: Signs in to: api.livetennisapi.com and Discord webhook - API keys: No API key is left in the file - Step types: Mindket’s checker reads all 5 of its step types ## Get it - [Get it on your Mindket account](https://account.mindket.com/account/?product=mindket#/market/1c631901-9a23-4f23-ba79-0b5235a15600) - [Its page on Mindket](https://mindket.com/p/1c631901-9a23-4f23-ba79-0b5235a15600)