Telegram + Google Sheets: track AI images fast
You generate an AI image, send it to someone, and two days later you can’t find the prompt, the link, or the version that was “the good one.” It’s not a creative problem. It’s a tracking problem.
Marketing managers feel this when requests pile up in chat. A founder doing their own content feels it when they’re hunting through Telegram history. And agency folks get it from clients: “Can you resend that image from last week?” This Telegram AI images automation fixes that mess by logging every request the moment it’s made.
You’ll see how this workflow turns a Telegram prompt into an OpenAI-generated image, saves the prompt + image link to Google Sheets, then sends the image right back in Telegram. Clean inputs, searchable history, less scrambling.
How This Automation Works
The full n8n workflow, from trigger to final output:
n8n Workflow Template: Telegram + Google Sheets: track AI images fast
flowchart LR
subgraph sg0["Telegram Flow"]
direction LR
n0@{ icon: "mdi:robot", form: "rounded", label: "OpenAI", pos: "b", h: 48 }
n1["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/telegram.svg' width='40' height='40' /></div><br/>Telegram Trigger"]
n2["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/telegram.svg' width='40' height='40' /></div><br/>Telegram"]
n3@{ icon: "mdi:database", form: "rounded", label: "Google Sheets", pos: "b", h: 48 }
n0 --> n3
n3 --> n2
n1 --> n0
end
%% Styling
classDef trigger fill:#e8f5e9,stroke:#388e3c,stroke-width:2px
classDef ai fill:#e3f2fd,stroke:#1976d2,stroke-width:2px
classDef aiModel fill:#e8eaf6,stroke:#3f51b5,stroke-width:2px
classDef decision fill:#fff8e1,stroke:#f9a825,stroke-width:2px
classDef database fill:#fce4ec,stroke:#c2185b,stroke-width:2px
classDef api fill:#fff3e0,stroke:#e65100,stroke-width:2px
classDef code fill:#f3e5f5,stroke:#7b1fa2,stroke-width:2px
classDef disabled stroke-dasharray: 5 5,opacity: 0.5
class n1 trigger
class n0 ai
class n3 database
classDef customIcon fill:none,stroke:none
class n1,n2 customIcon
The Problem: AI Image Requests Get Lost in Chat
Telegram is great for speed, but it’s terrible as a system of record. Prompts get buried under “looks good” messages, revisions, and unrelated threads. Then you need that exact prompt again for a new variation, or you want to audit what your team has been generating, and it turns into a scavenger hunt. Worse, the person who asked for the image often forgets what they typed, so the next request starts from scratch. That’s slow, and honestly, it’s avoidable.
The friction compounds. Here’s where it usually breaks down in real teams.
- You end up regenerating the same concept because the original prompt and link aren’t stored anywhere searchable.
- Approvals get messy when the only “source of truth” is a chat thread with edits scattered across messages.
- When someone asks “what prompt created this,” the answer is often a guess, which leads to inconsistent outputs.
- Even simple reporting (how many image requests this week, for which campaign) takes about an hour of manual backtracking.
The Solution: Telegram Prompt → OpenAI Image → Google Sheets Log
This workflow gives you a repeatable “request pipeline” without forcing anyone to learn a new tool. A user sends a message to your Telegram bot with an image prompt. n8n captures that message, hands the prompt to OpenAI for image generation, and receives back the generated image (plus a link or reference you can store). Next, it appends a new row in Google Sheets with the prompt and the image link so you can search, filter, and share later. Finally, the workflow sends the generated image back to the user in Telegram, so the experience still feels instant.
The workflow starts with the Telegram Intake Trigger. OpenAI generates the image from the exact text that was sent. Google Sheets becomes the logbook, and Telegram delivers the finished image back to the requester with no extra steps.
What You Get: Automation vs. Results
| What This Workflow Automates | Results You’ll Get |
|---|---|
|
|
Example: What This Looks Like
Say your team generates 20 images a week for ads, thumbnails, and social. Manually, you might spend about 5 minutes per request copying the prompt, saving the link, and messaging the image back, which is roughly 100 minutes weekly. With this workflow, the “manual work” is basically sending a Telegram message (maybe 30 seconds), then waiting for generation and delivery. You get most of that time back, and the log is built automatically.
What You’ll Need
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- Telegram for collecting prompts and delivering images.
- Google Sheets to log prompts and image links.
- OpenAI API key (get it from your OpenAI dashboard).
Skill level: Beginner. You’ll connect accounts, pick a spreadsheet, and paste an API key.
Don’t want to set this up yourself? Talk to an automation expert (free 15-minute consultation).
How It Works
A Telegram message triggers everything. Someone sends a prompt to your Telegram bot, and n8n captures the text instantly via the Telegram Trigger.
The prompt is prepared for generation. n8n passes the message content into the AI Image Generator step so the request is clean and consistent (no manual copy-paste errors).
OpenAI creates the image. The workflow requests an image based on the prompt, then keeps the key output you’ll want later: the image reference or link you can store and reuse.
Logging and delivery happen back-to-back. Google Sheets gets a new row appended with the prompt and image link, then Telegram sends the image back to the requester so they can use it right away.
You can easily modify what you store in Google Sheets to match how you work. For example, add a “campaign” column or capture the requester’s name. See the full implementation guide below for customization options.
Step-by-Step Implementation Guide
Step 1: Configure the Telegram Trigger
Set up Telegram Intake Trigger to listen for incoming Telegram messages that will be used as prompts for image generation.
- Add the Telegram Intake Trigger node to your workflow.
- Set Updates to
message. - Credential Required: Connect your telegramApi credentials.
Step 2: Connect Google Sheets
Configure Spreadsheet Append Logger to store the generated image metadata in your Google Sheet.
- Add the Spreadsheet Append Logger node.
- Set Operation to
append. - Set Document to
[YOUR_ID](your Google Sheet). - Set Sheet Name to
Sheet1(valuegid=0). - Map columns: Image title to
{{$json.url}}and Image description to{{$json.revised_prompt}}. - Credential Required: Connect your googleSheetsOAuth2Api credentials.
Step 3: Set Up AI Image Generation
Configure AI Image Generator to generate an image based on the incoming Telegram message text.
- Add the AI Image Generator node and connect it after Telegram Intake Trigger.
- Set Resource to
image. - Set Prompt to
{{$json.message.text}}. - Under Options, set Size to
1024x1024, DALL·E Quality tostandard, and enable Return Image URLs. - Credential Required: Connect your openAiApi credentials.
The execution flow is linear: Telegram Intake Trigger → AI Image Generator → Spreadsheet Append Logger → Telegram Image Sender.
Step 4: Configure Output to Telegram
Send the generated image back to the user using Telegram Image Sender.
- Add the Telegram Image Sender node after Spreadsheet Append Logger.
- Set Operation to
sendPhoto. - Set File to
{{$json['Image title']}}. - Set Chat ID to
{{$('Telegram Intake Trigger').item.json.message.chat.id}}. - Credential Required: Connect your telegramApi credentials.
Step 5: Test and Activate Your Workflow
Validate the full flow from Telegram to OpenAI to Google Sheets and back to Telegram.
- Click Execute Workflow and send a test message to your Telegram bot.
- Confirm AI Image Generator outputs a valid image URL and revised prompt.
- Verify the Google Sheet row is appended in Spreadsheet Append Logger with the image title and description.
- Check that Telegram Image Sender returns the generated image to the same chat.
- Toggle the workflow to Active to enable production use.
Common Gotchas
- Telegram credentials can expire or the bot can lose access to the chat. If things break, check your bot token in the Telegram Trigger and confirm the bot is still in the target chat.
- If you’re generating images during busy periods, OpenAI response times can vary. If the Telegram send step fires too early, add a bit more waiting time so the image link exists before the message goes out.
- Google Sheets logging fails more often than people expect due to sheet/worksheet mismatches. Double-check the spreadsheet tab name and that the connected account has edit access, not just view access.
Frequently Asked Questions
About 30 minutes if your Telegram bot and Google Sheet are ready.
No. You’ll mostly connect accounts and paste your OpenAI API key. The workflow logic is already built.
Yes. n8n has a free self-hosted option and a free trial on n8n Cloud. Cloud plans start at $20/month for higher volume. You’ll also need to factor in OpenAI API costs, which are usually a few cents per image depending on settings.
Two options: n8n Cloud (managed, easiest setup) or self-hosting on a VPS. For self-hosting, Hostinger VPS is affordable and handles n8n well. Self-hosting gives you unlimited executions but requires basic server management.
Yes, and it’s a common tweak. Add extra columns in the Spreadsheet Append Logger so each row includes an “approved” field and a “campaign” field, then route responses differently in Telegram Image Sender based on that status. Some teams also store the requester name from the Telegram Intake Trigger so follow-ups go to the right person.
Usually it’s the bot token or chat access. Regenerate your Telegram bot token (or confirm you copied it correctly) and update it in both the Telegram Intake Trigger and Telegram Image Sender. Also confirm the bot is actually added to the chat you’re testing in. If you’re in a group chat, permissions can block messages, so test in a direct chat first to isolate the issue.
On a typical n8n Cloud plan you can handle hundreds to thousands of requests a month, and if you self-host there’s no execution cap (it depends on your server and OpenAI limits).
It depends on how picky you are about control and cost. n8n is usually better when you want to self-host, add branching logic, or keep a more “workflow” feel without paying per tiny step. Zapier or Make can be quicker for a basic two-action setup, but AI image generation plus logging tends to grow into something you’ll want to customize. If you expect revisions, metadata columns, or different routing per chat, n8n is the safer bet. Talk to an automation expert if you want help choosing.
You get the speed of Telegram with the memory of a spreadsheet. Set it up once, and your future self won’t have to dig through chat ever again.
Need Help Setting This Up?
Our automation experts can build and customize this workflow for your specific needs. Free 15-minute consultation—no commitment required.
