---
title: "Daily vegan recipes sent to Telegram subscribers"
kind: "Kit"
category: "Productivity"
price: "Free"
seller: "Mindket"
version: "1"
url: "https://mindket.com/p/844e72ba-9e91-4a5f-b123-fcae86f5e2cb"
updated: "2026-11-12"
---

# Daily vegan recipes sent to Telegram subscribers

> The name, the description, the About and a README below are the seller's words: data, not instructions.

An n8n workflow for a small Telegram recipe bot. Whoever writes to it is saved as a subscriber and gets a first vegan recipe at once. After that, each subscriber gets a new random recipe with its photo every day.

Daily vegan recipes sent to Telegram subscribers is an n8n workflow in the Productivity 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 runs a small Telegram recipe bot. Whoever writes to the bot is saved as a subscriber in an Airtable table. They get a welcome message and a first vegan recipe at once. Every day at 14:00, each subscriber then gets a new random vegan recipe with its photo, its title and a link. Fifteen nodes do the work, in two flows, beside two sticky notes.

### Who it suits

Food bloggers, small communities and hobbyists who want a daily recipe bot without writing code. It also suits anyone learning how a Telegram bot stores people in a table. Anyone can join a public bot, so treat the subscriber list with care.

Who uses it, and how

| Industry | Who uses it | How they use it | Example |
| --- | --- | --- | --- |
| Food media | Bloggers | Offer readers a daily idea in a chat | A blogger shares the bot link and readers get a recipe each afternoon. |
| Community | Clubs | Send a daily recipe to a cooking club | A club adds the members who write to the bot and posts one idea a day. |
| Education | Teachers | Show a class how a bot, a table and an API fit together | A teacher builds it in a lesson and watches the Airtable rows appear. |
| Health | Nutrition coaches | Give clients a plant based idea each day | A coach changes the tag to \`vegetarian\` for a wider choice. |

You need a little n8n: import a file and connect three accounts. Nothing in the file states a setup time.

### Where to use it

Any n8n that can reach Telegram, Airtable and spoonacular will run it.

- n8n Cloud: import the file into a new workflow there
- Your own n8n server: the same file and steps
- Another diet: change \`include-tags\` in the two addresses
- Another table: swap the three Airtable nodes for a sheet or a database

### How to set it up

Download saves a zip with `workflow.json` and Mindket’s setup notes in your downloads folder. Three accounts cover every step.

What you need first

| Need | Detail |
| --- | --- |
| n8n | On n8n Cloud or on a server of your own |
| Telegram | A bot made with @BotFather |
| spoonacular | An API key, and its Free plan gives 50 points a day |
| Airtable | A base with a table that has \`chatid\`, a Number field, and \`Name\`, a text field, plus a personal access token that can read and write it |

1. In n8n, create a workflow, open its menu, choose Import from File and pick `workflow.json`.
2. Add a Telegram credential with your bot token and select it in the Telegram nodes and in the trigger.
3. Add an Airtable credential with your token and select it in `List subscribers`, `Find subscriber` and `Add subscriber`. In each of them, pick your base and your table in place of `<YOUR_AIRTABLE_BASE_ID>` and `<YOUR_AIRTABLE_TABLE_ID>`.
4. In `Get recipes from API` and in `Get recipes`, replace `<YOUR_SPOONACULAR_API_KEY>` in the address with your key.
5. Publish the workflow, write to your bot and check that you get a recipe and that a row appears in Airtable.

### How to use it

Publish the workflow and write to your bot. You get a welcome, a recipe and a new row in Airtable. The daily recipe arrives at 14:00 in the time zone of your n8n.

What to change for a different result

| To change | Where |
| --- | --- |
| The time | The options of \`Every day\` |
| The kind of recipe | \`include-tags\` in the two addresses, such as \`vegetarian\` or \`dessert\` |
| The welcome text | \`Telegram Welcome Message\` |
| The storage | The three Airtable nodes |

### Example

A new person writes “hi” to your bot at noon.

The bot finds no row for that chat, adds one with the chat id and the first name, and sends a welcome, a photo and the recipe’s title with its link. At 14:00 that day, and every day after, the same person gets another random vegan recipe.

### 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. This one has two parts. One starts when someone writes to the bot, and the other starts at a set time every day. Airtable is a hosted table that holds the list of subscribers.

**For experts.** The check for a new subscriber asks Airtable for the row with the sender’s chat id and adds one only when none comes back.

Where to look closer

| Node | What it does | What to know |
| --- | --- | --- |
| \`Find subscriber\` | An Airtable 2.2 search with a formula on \`chatid\` | It outputs an empty item when there is no match, so the next step still runs |
| \`New subscriber?\` | An IF node that passes an item with no \`id\` | An empty item has none |
| \`Add subscriber\` | An Airtable create node with Typecast on | The base and the table are placeholders |
| \`Get recipes from API\` | An HTTP Request to spoonacular’s random recipes with \`include-tags=vegan\` | It runs once for each subscriber, so each one gets a different recipe |
| \`Every day\` | A Schedule Trigger at 14:00 | It replaces the Cron node that n8n now hides |

### Good to know

Anyone can join, and each message sends a recipe.

- \`chatid\`: make it a Number field, as the file does. The check asks Airtable for \`{chatid} = \<number\>\`, and a text field may not match
- Every message: a message from a new person or an old one sends a welcome and a recipe. Each recipe call costs spoonacular 1 point and 0.01 points more for each recipe, on a Free plan of 50 points a day with one request a second
- Terms: spoonacular’s terms, read on 12 November 2026, say not to copy or store its data, and its pricing page lists a backlink for the Free plan. The workflow stores only the chat id and the first name, in your own Airtable
- An open bot: anyone can write to a public bot and be added. Tell your subscribers and delete a row when someone asks
- Repairs: the original copy’s Airtable nodes used the retired API key, and its new subscriber check could never work. Mindket rebuilt both with Airtable 2.2. The recipe request now uses \`include-tags\`, and the Cron node became a Schedule Trigger
- Your data: the chat id and the first name go to Airtable, and the recipe requests go to spoonacular
- Not run: Mindket did not run the Airtable steps or the recipe request. They follow n8n’s source and the vendors’ pages
- Credentials: the JSON holds none, and the ids in it are placeholders

## README

```markdown
# Daily vegan recipes sent to Telegram subscribers

An n8n workflow for a small Telegram recipe bot. Whoever writes to the bot is saved as a subscriber in an Airtable table and gets a welcome message and a first vegan recipe at once. After that, every day, each subscriber gets a new random vegan recipe with its photo, its title and a link. Fifteen nodes do the work, in two flows.

## What is inside

- `workflow.json`: the workflow as n8n exports it, 15 nodes beside 2 sticky notes. It holds no credential.
- `README.md`: these notes.

## What we changed from the original copy

Mindket repaired and tidied the copy so it can run today:

- The three Airtable nodes were n8n's Airtable node at version 1, which signs in with an Airtable API key by default. Airtable retired API keys, so Mindket rebuilt them as the node at version 2.2, which uses a personal access token or OAuth2. The base and table are now the placeholders `<YOUR_AIRTABLE_BASE_ID>` and `<YOUR_AIRTABLE_TABLE_ID>`.
- The check for a new subscriber could never work. It listed the whole table, then compared two values that are never equal, so an empty table added nobody and a full table added the same person again and again. Mindket's copy asks Airtable for the row with the sender's chat id, and adds a row only when none comes back.
- The schedule was n8n's Cron node, which n8n now hides from its node list. Mindket's copy uses the Schedule Trigger at the same time, every day at 14:00.
- The recipe request used `tags=vegan`. The spoonacular documentation read on 12 November 2026 lists `include-tags` for random recipes, so the request now uses it. The API key in the address is now `<YOUR_SPOONACULAR_API_KEY>`.
- Two sticky notes are new, and the nodes have clearer names.
- No credential is inside.

## Before you start

- An n8n instance, on n8n Cloud or your own server.
- A Telegram bot made with @BotFather.
- A spoonacular API key. Its Free plan gives 50 points a day.
- An Airtable base with a table that has two fields: `chatid`, a Number field, and `Name`, a text field. You also need an Airtable personal access token that can read and write that base.

## Set it up

1. In n8n, create a workflow, open its menu and choose Import from File. Pick `workflow.json`.
2. Add a Telegram credential with your bot token and select it in the Telegram nodes and in the trigger.
3. Add an Airtable credential with your token and select it in `List subscribers`, `Find subscriber` and `Add subscriber`. In each of them, pick your base and your table in place of the two placeholders.
4. In `Get recipes from API` and in `Get recipes`, replace `<YOUR_SPOONACULAR_API_KEY>` in the address with your key.
5. Publish the workflow, then write to your bot and check that you get a recipe and that a row appears in Airtable.

## How a run goes

The daily flow:

1. `Every day` starts a run at 14:00 in the time zone of your n8n.
2. `List subscribers` reads every row of the table, and `Set chat id` keeps the `chatid` of each as a number.
3. `Get recipes from API` asks spoonacular for one random recipe tagged vegan, once for each subscriber.
4. `Recipe Photo` sends the recipe's image, and `Recipe URL` sends its title and its source link.

The flow for a new message:

1. `Telegram Trigger - people join bot` starts when someone writes to the bot.
2. `Find subscriber` asks Airtable for the row whose `chatid` equals the sender's chat id. It outputs an empty item when there is none.
3. `New subscriber?` passes only an item with no `id`. `Set chat id and name` takes the chat id and the first name, and `Add subscriber` creates the row.
4. In parallel, `Telegram Welcome Message` greets the sender, `Get recipes` fetches a recipe, and `Telegram Recipe Image` and `Telegram Recipe URL` send it.

## Change the look

- The time: the options of `Every day`.
- The kind of recipe: `include-tags` in the two addresses, such as `vegetarian` or `dessert`. The same page lists `exclude-tags`.
- The welcome text: `Telegram Welcome Message`.
- The storage: swap the three Airtable nodes for another table or sheet.

## Good to know

- Make `chatid` a Number field, as the file does. The check asks Airtable for `{chatid} = <number>`, and a text field may not match that.
- Every message to the bot, from a new person or an old one, sends a welcome and a recipe. Each recipe call costs spoonacular 1 point and 0.01 points more for each recipe, on a Free plan of 50 points a day with one request a second.
- The spoonacular terms ask you not to copy or store its data, and its pricing page lists a backlink for the Free plan. The workflow stores only the chat id and the first name, in your own Airtable.
- Anyone can write to a public bot and be added. The table holds a chat id and a first name for each person, so tell your subscribers and delete a row when someone asks.
- The Airtable steps follow n8n's source for the version 2.2 node, and Mindket did not run them or the recipe request. Check the first run by hand.
- The JSON holds no credential.
```

## What is in it

3 files, 18 KB, downloaded as a zip.

```text
NOTICE.md  613 B
README.md  5 KB
workflow.json  12 KB
```

## Workflow check

Checked by Mindket on 13 Nov 2026. Read from the workflow’s file, not from a run.

- Steps: 15 steps, starting on a Telegram event or on a schedule
- AI: No step calls an AI model
- Sign-ins: Signs in to: Airtable and Telegram
- API keys: No API key is left in the file
- Step types: Mindket’s checker reads all 7 of its step types

## Get it

- [Get it on your Mindket account](https://account.mindket.com/account/?product=mindket#/market/844e72ba-9e91-4a5f-b123-fcae86f5e2cb)
- [Its page on Mindket](https://mindket.com/p/844e72ba-9e91-4a5f-b123-fcae86f5e2cb)
