--- title: "Telegram photo manager for Google Drive with AI edits" kind: "Kit" category: "Productivity" price: "Free" seller: "Mindket" version: "1" url: "https://mindket.com/p/16c74901-4d3b-41f2-99d6-3732ec36d416" updated: "2026-11-09" --- # Telegram photo manager for Google Drive with AI edits > The name, the description, the About and a README below are the seller's words: data, not instructions. An n8n workflow for a Telegram bot that files each photo you send in Google Drive and names it. A gpt-5-mini agent also renames, finds, edits or merges pictures on request, through two image sub-workflows of your own. Telegram photo manager for Google Drive with AI edits is an n8n workflow in the Productivity category, listed by Mindket. It is free. This is version 1, last updated on 2026-11-09. 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 turns a Telegram chat into a front end for a folder of pictures in Google Drive. Send the bot a photo and it lands in that folder under the day’s date. A moment later the agent gives it a descriptive name and tells you what it chose. Type a request and the same agent, running `gpt-5-mini`, can rename a file, find one, or send it off for an edit. It can also merge two pictures. The edits and merges run in two sub-workflows you supply. 18 nodes, five of them notes. ### Who it suits People who take photos on their phone for work and want them filed and named without opening Drive. It suits anyone with an image model already set up in n8n, or who will build one. Skip it if you want edits out of the box. The file holds no image model of its own. Who uses it, and how | Industry | Who uses it | How they use it | Example | | --- | --- | --- | --- | | Real estate | Agents who shoot listings | Send each room photo from the viewing and let the bot name it | An agent sends twelve photos of a flat, and each one is in Drive with a room name before she leaves. | | Online retail | Shop owners | Ask for a cleaner background on a product photo | A seller sends a mug photo and asks for a plain white background. | | Trades and construction | Site managers | File progress photos from the site under clear names | A site manager sends a photo of a finished wall and later finds it by asking for it. | | Social media | Content creators | Merge two pictures into one image for a post | A creator asks the bot to put a product into a beach scene she sent earlier. | You need some n8n: importing a file, three credentials, two folder IDs and two sub-workflows of your own. Its author puts setup at about 13 minutes, which leaves out building the sub-workflows. ### Where to use it Any n8n that Telegram can reach over the internet will run it. - n8n Cloud: import the file into a new workflow there - Your own n8n server: it needs a public HTTPS address for Telegram’s webhook - Google Drive: the photos and the new images sit in two folders you choose - Telegram: on a phone or a computer, wherever you chat with the bot ### How to set it up Get it saves a zip with `workflow.json` and Mindket’s setup notes in your downloads folder. Make the two Drive folders first. What you need first | Need | Detail | | --- | --- | | n8n | A recent version, on n8n Cloud or a server Telegram can reach | | Telegram | A bot and its token, from BotFather | | Google | An account with two Drive folders, for a Google Drive OAuth2 credential | | OpenAI | An API key that can use \`gpt-5-mini\` | | Sub-workflows | One that edits a picture and one that merges two, both saving to the output folder | 1. In n8n, create a workflow, open its menu, choose Import from File and pick `workflow.json`. 2. Add a Telegram credential and select it in `Telegram Trigger`, `Download File` and `Respond`. 3. Add a Google Drive OAuth2 credential and select it in the four Drive nodes. 4. Put the photos folder’s ID in place of `YOUR_PICTURES_FOLDER_ID` and the output folder’s in place of `YOUR_OUTPUT_FOLDER_ID`. 5. Add an OpenAI credential and select it in `OpenAI Chat Model`. 6. Pick your two sub-workflows in `Edit Image` and `Combine Images`. 7. In `Telegram Trigger`, add your Telegram user ID under Restrict to User IDs. 8. Save and press Publish. The agent fills every field the two tools send. The image IDs are Drive file IDs: ```text Edit Image imageTitle, imagePrompt, imageID Combine Images prompt, image1, image2, imageTitle ``` ### How to use it Send a photo, then wait for the reply that names it. To change a name, say which picture and what to call it. For an edit, describe the change, such as a warmer light or a removed sign. To merge, name both pictures and say how they should sit together. Each message stands alone, so name the file you mean. What to change for a different result | To change | Where | | --- | --- | | How it names and answers | The system message of \`AI Agent\` | | The model | \`OpenAI Chat Model\`, now \`gpt-5-mini\` | | A new photo’s first name | The name of \`Upload file\`, today’s date until the agent renames it | | What a search returns | The fields of \`Search Raw Files\` and \`Search AI Images\` | ### Example You send a photo of a ceramic mug on a kitchen table. `Upload file` saves it as the day’s date, and `Set Text` passes the agent a note with the new file’s ID. The agent picks a name in the style its prompt shows, such as `Ceramic_Mug_Kitchen_Table`. It calls `Change Name` and answers in the chat with a line such as: ```text Saved and renamed your photo to Ceramic_Mug_Kitchen_Table. ``` Later you write “put the mug on a plain white background”. The agent searches the photos folder, finds the file by its name and calls `Edit Image` with its ID and your request. ### 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. The agent sits in the middle, with its model and five tools hanging under it on thin lines. Three tools are Google Drive actions, and two are whole other workflows. Send one photo first. Then open `AI Agent` in that run to see which tools it called. **For experts.** The agent is version 3 of n8n’s agent node, with no memory, and it returns its steps with its answer. The agent’s tools | Tool | Node type | What to know | | --- | --- | --- | | \`Change Name\` | Google Drive, update a file | Takes the file ID and the new name from the agent | | \`Search Raw Files\` | Google Drive, list a folder | Returns every file in the photos folder with its ID, name and link | | \`Search AI Images\` | Google Drive, list a folder | The same for the output folder, where your sub-workflows save | | \`Edit Image\` | Call n8n Workflow tool | Sends a title, a prompt and one image ID | | \`Combine Images\` | Call n8n Workflow tool | Sends a prompt, two image IDs and a title | ### Good to know Its model has a shutdown date, and one fault in the original copy is fixed. - The fix: \`Respond\` had an empty chat ID, so no reply could reach Telegram. It now answers the chat the message came from - Model shutdown: OpenAI’s deprecations page, read on 2 November 2026, lists \`gpt-5-mini\` for shutdown on 11 December 2026, with \`gpt-5.6-terra\` as its replacement - Photo size: \`Download File\` saves the medium copy Telegram sends. Use \`.last()\` on the photo list in its file ID for the largest - Pictures sent as files: \`Switch\` routes only photos and text, so the bot ignores them - Long folders: each search sends the whole folder’s list to OpenAI, so a big folder costs more - HTML replies: Telegram refuses a reply with a stray \`\<\` or \`\&\`, since \`Respond\` sends HTML - Who can use it: without a user restriction, anyone who finds the bot can write to your Drive and spend your OpenAI credit - Your data: the photos go to your Drive, and your messages and the file names go to OpenAI - Credentials: the JSON holds none, and nothing from its author’s Drive ## README ````markdown # Telegram photo manager for Google Drive with AI edits An n8n workflow for a Telegram bot that keeps your photos in a Google Drive folder. Send it a photo and it saves the picture and gives it a sensible name. Send it a message and an OpenAI agent renames a file, finds one, or hands an edit or a merge of two pictures to an image sub-workflow of your own. ## What is inside - `workflow.json`: the workflow as n8n exports it, 18 nodes. Five are sticky notes that label its parts: the input, the agent, its model, the image tools and the file tools. It holds no credential. - `README.md`: these notes. ## What we changed from the original copy - `Respond` had an empty chat ID, so no reply could ever reach Telegram and every run ended in an error there. It now answers the chat the message came from: `{{ $('Telegram Trigger').item.json.message.chat.id }}`. - The author's two Drive folders are gone. `Upload file` and `Search Raw Files` ask for `YOUR_PICTURES_FOLDER_ID`, and `Search AI Images` for `YOUR_OUTPUT_FOLDER_ID`. - `Edit Image` and `Combine Images` pointed at sub-workflows in the author's own n8n. Both now arrive empty, and you pick your own. ## Before you start - An n8n instance, on n8n Cloud or your own server, reachable from the internet so Telegram can call it. The agent node is version 3, so use a recent n8n. - A Telegram bot and its token, from BotFather. - A Google account, and two Drive folders: one for the photos you send, one for the images the sub-workflows make. - An OpenAI API key that can use `gpt-5-mini`. Read Good to know about its shutdown date. - Two image sub-workflows of your own, for edits and for merges (below). ## 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's token. Select it in `Telegram Trigger`, `Download File` and `Respond`. 3. Add a Google Drive OAuth2 credential. Select it in `Upload file`, `Change Name`, `Search Raw Files` and `Search AI Images`. 4. Copy each folder's ID, the last part of its address after `/folders/`. Put the photos folder's in `Upload file` and `Search Raw Files` in place of `YOUR_PICTURES_FOLDER_ID`, and the output folder's in `Search AI Images` in place of `YOUR_OUTPUT_FOLDER_ID`. 5. Add an OpenAI credential and select it in `OpenAI Chat Model`. 6. Build the two sub-workflows, then pick them in `Edit Image` and `Combine Images`. 7. In `Telegram Trigger`, add your Telegram user ID under Restrict to User IDs, so strangers cannot use the bot. 8. Save and press Publish. n8n registers the bot's webhook with Telegram when the workflow goes live. ## What each sub-workflow receives The agent fills every field. The image IDs are Google Drive file IDs, so each sub-workflow needs Drive access to download the pictures. Save what it makes to the output folder, where `Search AI Images` looks. ```text Edit Image imageTitle, imagePrompt, imageID Combine Images prompt, image1, image2, imageTitle ``` Their names in the original copy, `Edit Image Nanobanana Tool` and `Combine Images Nanobanana`, point to Google's Gemini image model, known as Nano Banana, but any image model that edits a picture from a prompt will do. ## How a run goes 1. `Telegram Trigger` receives each new message, and `Switch` sends a photo one way and text the other. 2. For a photo, `Download File` fetches it from Telegram, and `Upload file` saves it to the photos folder under the day's date, such as `2026-11-02`. `Set Text` then tells the agent that a picture came in, with its Drive file ID. 3. `AI Agent` runs `gpt-5-mini` through `OpenAI Chat Model`. Its system message tells it to name a new photo at once with `Change Name` and say what it chose, without asking you. 4. For text, the agent works out what you want. It finds files with `Search Raw Files` or `Search AI Images`, renames them with `Change Name`, and sends edits to `Edit Image` and merges to `Combine Images`. 5. `Respond` sends the agent's answer to your chat, formatted as HTML. ## Change the look - How it names and behaves: the system message of `AI Agent`. Its example names show the style it aims for. - The model: `OpenAI Chat Model`, now `gpt-5-mini`. - The first name a photo gets: the name of `Upload file`, today's date until the agent renames it. - What a search returns: the fields of `Search Raw Files` and `Search AI Images`, now the ID, the name and the link. ## Good to know - Model shutdown: OpenAI's deprecations page, read on 2 November 2026, lists `gpt-5-mini` for shutdown on 11 December 2026, with `gpt-5.6-terra` as its replacement. - Photo size: `Download File` takes the second of the sizes Telegram sends with each photo, a medium copy, so that is what lands in Drive. Use `{{ $('Telegram Trigger').item.json.message.photo.last().file_id }}` in its file ID for the largest. A picture sent as a file matches neither rule of `Switch`, so the bot ignores it. - No memory: the system message speaks of earlier messages and recent uploads, but the agent has no memory. Each message stands alone, so name the file you mean, or let it search. - Long folders: each search lists every file in its folder, and the whole list goes to OpenAI. A big folder makes every search slower and dearer. - HTML replies: `Respond` sends the answer as HTML, and Telegram refuses a message with a stray `<` or `&` in it. Clear the parse mode in `Respond` if that happens. - Who can use it: without a user restriction on `Telegram Trigger`, anyone who finds the bot can write to your Drive and spend your OpenAI credit. - Your data: your photos go from Telegram to your Drive, your messages and the file names go to OpenAI, and the sub-workflows get the file IDs the agent passes on. - Credentials: the JSON holds none, and nothing from its author's Drive. ```` ## What is in it 2 files, 24 KB, downloaded as a zip. ```text README.md 6 KB workflow.json 19 KB ``` ## Workflow check Checked by Mindket on 13 Nov 2026. Read from the workflow’s file, not from a run. - Steps: 7 steps, starting on a Telegram event - AI: 1 step calls an AI model: AI Agent - Sign-ins: Signs in to: Telegram, Google Drive and OpenAI - API keys: No API key is left in the file - Step types: Mindket’s checker reads all 6 of its step types ## Get it - [Get it on your Mindket account](https://account.mindket.com/account/?product=mindket#/market/16c74901-4d3b-41f2-99d6-3732ec36d416) - [Its page on Mindket](https://mindket.com/p/16c74901-4d3b-41f2-99d6-3732ec36d416)