--- title: "New JSON API entries sent to Telegram every 5 minutes" kind: "Kit" category: "Developer" price: "Free" seller: "Mindket" version: "1" url: "https://mindket.com/p/2ab927de-feff-4e15-9e81-a8a14aa4ce8c" updated: "2026-11-12" --- # New JSON API entries sent to Telegram every 5 minutes > The name, the description, the About and a README below are the seller's words: data, not instructions. An n8n workflow that watches a JSON address and tells you on Telegram when something new appears. Every 5 minutes it keeps the entries that are new and match your filter, and sends each one as a message. New JSON API entries sent to Telegram every 5 minutes is an n8n workflow in the Developer category, listed by Mindket. It is free. This is version 1, last updated on 2026-11-12. 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 watches a JSON address and tells you on Telegram when something new appears. Every 5 minutes it reads a list from your own API. It keeps the entries that are newer than the last one it saw and that match a filter you choose. Each one is sent as a Telegram message. Four nodes do the work. ### Who it suits Developers and small teams who want a plain alert for error logs, order lists, status feeds and similar lists. It also suits anyone learning how a workflow remembers what it has already seen. It needs a JSON address that lists entries with the newest first. Who uses it, and how | Industry | Who uses it | How they use it | Example | | --- | --- | --- | --- | | Software | Developers | Get an alert for each new error in a log API | A developer filters for \`error\` and \`warning\` and reads them on a phone. | | E-commerce | Shop owners | Hear about new orders from a store API | An owner sees each new order as one Telegram message. | | Operations | Support teams | Watch a status feed for new incidents | A team lead gets each new incident as it appears. | | Education | Students | Learn polling and a simple memory in n8n | A student points it at a public JSON list and watches the alerts arrive. | You need a little n8n and some JSON: import a file, set an address, match four names in a short script and add a Telegram bot. Nothing in the file states a setup time. ### Where to use it Any n8n that can reach your JSON address and Telegram will run it. - n8n Cloud: import the file into a new workflow there - Your own n8n server: the same file and steps - Another list: change the address and the four names at the top of the code - Another channel: swap \`Send to Telegram\` for an email or Slack node ### How to set it up Download saves a zip with `workflow.json` and Mindket’s setup notes in your downloads folder. Three things cover every step: a JSON address, a Telegram bot and your chat id. What you need first | Need | Detail | | --- | --- | | n8n | On n8n Cloud or on a server of your own | | A JSON address | One that answers with an object holding a list of entries, newest first, each with a timestamp or another field that sorts as text | | Telegram | A bot made with @BotFather, and the id of the chat that should get the alerts | 1. In n8n, create a workflow, open its menu, choose Import from File and pick `workflow.json`. 2. In `Read the JSON feed`, replace `` with the address of your list. If it needs a key, add it in the node’s options. 3. In `Only new and filtered entries`, set the four names at the top of the code to match your response: `ARRAY_FIELD`, `FILTER_VALUES`, `FILTER_FIELD` and `TIMESTAMP_FIELD`. 4. Add a Telegram credential with your bot token and select it in `Send to Telegram`. 5. Write to your bot once, find your chat id in the answer of the bot’s `getUpdates` call, and put it in place of `` in `Send to Telegram`. 6. Publish the workflow. ### How to use it Publish the workflow and leave it running. The first run sends every entry that passes the filter, so start with a filter or a short list. What to change for a different result | To change | Where | | --- | --- | | How often it checks | The interval in \`Every 5 minutes\` | | What counts as news | \`FILTER\_VALUES\` and \`FILTER\_FIELD\` in the code | | The look of the alert | The \`text\` the code builds | | Where it goes | The chat id in \`Send to Telegram\`, or another node in its place | ### Example Your API lists three log entries, and two of them have the type `error`. On the first run the code keeps the two errors, puts the older one first and stores the timestamp of the newer one. Telegram shows two messages. Five minutes later nothing is sent, until a new error appears. ### 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. A schedule node starts the run, a request node reads the list, a code node picks what is new and a Telegram node sends it. The workflow remembers the last timestamp between runs. **For experts.** The memory is the workflow’s static data, so it works only after you publish. Where to look closer | Node | What it does | What to know | | --- | --- | --- | | \`Every 5 minutes\` | A Schedule Trigger on a 5 minute interval | Change the interval here | | \`Read the JSON feed\` | An HTTP Request that fetches your address and waits at most 10 seconds | A key goes in the node’s options | | \`Only new and filtered entries\` | A Code node that filters, compares timestamps as text and stores the newest one | A field that does not sort as text breaks the comparison | | \`Send to Telegram\` | A Telegram node that sends one message for each entry | The text is legacy Markdown, so the code escapes its special characters | ### Good to know Its memory works only on a published workflow. - First run: there is no stored timestamp yet, so it sends every entry that passes the filter - Timestamps: they are compared as text, so use a field that sorts as text, such as an ISO date. Plain numbers of different lengths do not compare well - Order: it expects the newest entry first and sends the alerts oldest first - Memory: the stored timestamp is n8n’s workflow static data. n8n’s page, read on 12 November 2026, says it is not saved when you test a workflow and that it is experimental. Test runs send the same entries again - Attribution: the Telegram node adds a line saying the message was sent with n8n. Turn it off in the node’s options - Length: Telegram cuts a message at 4096 characters, and the alerts stay far below that - Repairs: the original copy was in Italian and read its chat id from a server setting. Mindket’s copy is in English, uses placeholders and escapes the characters that made Telegram refuse a message - Your data: the entries you read go to Telegram. Check what your list holds first - Not run: Mindket did not run it against a live address. It read n8n’s source and Telegram’s pages instead - Credentials: the JSON holds none, and the ids in it are placeholders ## README ```markdown # New JSON API entries sent to Telegram every 5 minutes An n8n workflow that watches a JSON address and tells you on Telegram when something new appears. Every 5 minutes it reads a JSON list from your own API. It keeps only the entries that are newer than the last one it saw and that match a filter you choose. Each one is sent as a Telegram message. It suits error logs, order lists, status feeds and similar lists. Four nodes do the work. ## What is inside - `workflow.json`: the workflow as n8n exports it, 4 nodes and no sticky notes. It holds no credential. - `README.md`: these notes. ## What we changed from the original copy Mindket cleaned and repaired the copy: - The original copy was written in Italian: the node names, the comments in the code and the word in the alert. Mindket's copy is in English. The filter field `tipo` is now `type`, and the fallback label `evento` is now `event`. - The address of the JSON list was a made-up Italian "insert your API here" address. It is now the placeholder ``. - The chat id was read from an n8n environment variable, with a made-up fallback. It is now the placeholder `` in the Telegram node, so nothing depends on a server setting. - The Telegram node reads the text as Markdown by default, as n8n's own source shows. A JSON entry with one `_` or `*` more than a pair makes Telegram refuse the message. Mindket's code now puts a backslash before `_`, `*`, a backtick and `[`, as Telegram's Bot API page asks for legacy Markdown. - The setup note inside the file is now this README, and the file's empty credential name is gone. - No credential is inside. ## Before you start - An n8n instance, on n8n Cloud or your own server. - A JSON address that answers with an object holding a list of entries, newest first, each with a timestamp or another field that sorts as text. - A Telegram bot made with @BotFather, and the id of the chat that should receive the alerts. ## Set it up 1. In n8n, create a workflow, open its menu and choose Import from File. Pick `workflow.json`. 2. In `Read the JSON feed`, replace `` with the address of your list. If it needs a key, add it in the node's options. 3. In `Only new and filtered entries`, set the four names at the top of the code to match your response: `ARRAY_FIELD`, `FILTER_VALUES`, `FILTER_FIELD` and `TIMESTAMP_FIELD`. 4. Add a Telegram credential with your bot token and select it in `Send to Telegram`. 5. Write to your bot once, then find your chat id in the answer of the bot's `getUpdates` call, and put it in place of `` in `Send to Telegram`. 6. Publish the workflow. ## How a run goes 1. `Every 5 minutes` starts a run every 5 minutes. 2. `Read the JSON feed` fetches your address and waits at most 10 seconds for the answer. 3. `Only new and filtered entries` takes the list from the field `ARRAY_FIELD`. It keeps the entries whose `FILTER_FIELD` is one of `FILTER_VALUES`, or all of them when that list is empty. Then it keeps the entries whose timestamp is greater than the one stored from the last run, as text, and puts the oldest first. 4. The code stores the timestamp of the newest entry it sends. It writes each alert as a bell, the filter field value and the first 300 characters of the entry. 5. `Send to Telegram` sends one message for each entry. ## Change the look - How often it checks: the interval in `Every 5 minutes`. - What counts as news: `FILTER_VALUES` and `FILTER_FIELD` in the code, for example `['error','warning']`. - The look of the alert: the `text` the code builds. - Where it goes: the chat id in `Send to Telegram`, or a node for email or Slack in its place. ## Good to know - The first run after you publish has no stored timestamp, so it sends every entry in the list that passes the filter. Start with a short list or a filter. - The code compares timestamps as text, so use a field that sorts as text, such as an ISO date. Plain numbers of different lengths, such as 9 and 10, do not compare well. - It expects the newest entry first, and it reverses the list so that the alerts come oldest first. - The stored timestamp is n8n's workflow static data. n8n's page says static data is not saved when you test a workflow, and that it is an experimental feature. Test runs send the same entries again, and the memory works once the workflow is published. - The Telegram node adds a line saying the message was sent with n8n. Turn that off in the node's options if you do not want it. - Telegram cuts a message at 4096 characters. The code keeps each alert far below that. - The JSON holds no credential. ``` ## What is in it 3 files, 8 KB, downloaded as a zip. ```text NOTICE.md 578 B README.md 5 KB workflow.json 3 KB ``` ## Workflow check Checked by Mindket on 13 Nov 2026. Read from the workflow’s file, not from a run. - Steps: 4 steps, starting on a schedule - AI: No step calls an AI model - Sign-ins: Signs in to: Telegram - API keys: No API key is left in the file - Step types: Mindket’s checker reads all 4 of its step types ## Get it - [Get it on your Mindket account](https://account.mindket.com/account/?product=mindket#/market/2ab927de-feff-4e15-9e81-a8a14aa4ce8c) - [Its page on Mindket](https://mindket.com/p/2ab927de-feff-4e15-9e81-a8a14aa4ce8c)