Create and publish AI videos from Telegram with VEED and Blotato

Name: Create and publish AI videos from Telegram with VEED and Blotato
Availability: InStock
Author: VEED

Create and publish AI videos from Telegram with VEED and Blotato preview

Open on n8n.io

$20/month : Unlimited workflows

2500 executions/month

Try free

THE #1 IN WEB SCRAPING

Scrape any website without limits

Try free

HOSTINGER

Early Deal
DISCOUNT 20%

Self-hosted n8n

Unlimited workflows - from $4.99/mo

Try free

#1 hub for scraping, AI & automation

6000+ actors - $5 credits/mo

Try free

Overview

Create & Publish AI Videos from Telegram Chat with VEED and Blotato

Overview

This n8n workflow creates a conversational AI video agent accessible through Telegram. Users chat with a bot to request AI-generated talking-head videos using VEED's MCP tools, then optionally publish to 9 social media platforms via Blotato with a single approval tap.

Output: AI-generated talking-head videos delivered in Telegram and published to TikTok, YouTube, Instagram, LinkedIn, Facebook, X, Threads, Bluesky, and Pinterest.

What It Does

User Message (Telegram) → AI Agent → VEED MCP tools create video → Response sent via Telegram
 ↕ Memory ↓ (if video URL detected)
 Approval prompt (Approve/Reject)
 ↓ Approved
 Upload to Blotato → Publish to 9 platforms in parallel
 ↓
 Merge results → Summary sent via Telegram

Flow Breakdown

Step	Component	What Happens
1. Message Received	📩 Telegram Trigger	User sends a text message to the bot
2. AI Processing	🤖 AI Video Agent (gpt-5-nano)	Interprets request, decides which VEED tools to use
3. Context Retention	💾 Conversation Memory	Maintains conversation history per chat (20-message window)
4. Video Creation	🎬 VEED MCP Tools	Lists characters/voices, confirms details, creates video via VEED Fabric
5. Response Delivery	📤 Send Agent Response	Sends agent text back to user in Telegram
6. URL Extraction	📋 Extract Video URL	Detects the `VIDEO_READY:` marker in agent output
7. Approval Prompt	📩 Publish to Social Media?	Telegram sendAndWait with Approve/Reject buttons (24h timeout)
8. Upload	📤 Upload Video to Blotato	Uploads video file to Blotato CDN, returns hosted URL
9. Publish	TikTok, YouTube, Instagram, LinkedIn, Facebook, X, Threads, Bluesky, Pinterest	All 9 platform nodes post in parallel using the Blotato URL
10. Summary	📤 Send Publish Summary	Confirms publication back to user in Telegram

Required Connections

n8n Credentials

Node	Credential Type	Where to Get
📩 Telegram Trigger	Telegram Bot API	Create bot via @BotFather in Telegram
🧠 OpenAI Chat Model	OpenAI API Key	https://platform.openai.com/api-keys
🎬 VEED MCP Tools	MCP OAuth2	Your VEED OAuth2 client credentials
📤 Send Agent Response	Telegram Bot API	Same bot token as trigger
📩 Publish to Social Media?	Telegram Bot API	Same bot token as trigger
📤 Upload Video to Blotato	Blotato API	https://my.blotato.com/settings → API
TikTok / YouTube / Instagram / ...	Blotato API	Same Blotato credential as upload

Community Node Required

Install @blotato/n8n-nodes-blotato via Settings → Community Nodes → Install in n8n.

Configuration Options

AI Agent System Prompt

The AI Agent's behavior is defined by its system prompt. Edit the 🤖 AI Video Agent node to customize:

You are a friendly AI video creation assistant powered by VEED.
You help users create professional talking-head videos with AI avatars through Telegram.

Video Creation Flow:
1. Understand their need - Ask what video they want
2. Choose a character - Show available AI avatars
3. Choose a voice - Ask preferred language/locale
4. Confirm details - Summarize before creating
5. Create the video - Generate with confirmed parameters
6. Track progress - Poll generation status
7. Deliver result - Share the video URL with VIDEO_READY: marker

Agent Configuration

Field	Default	Description
Model	`gpt-5-nano`	OpenAI model used for reasoning
Max Iterations	`15`	Maximum tool-calling rounds per message
Memory Window	`20` messages	How many past messages the agent remembers
Session Key	`{{ $json.message.chat.id }}`	Isolates memory per Telegram chat

Available VEED MCP Tools

Tool	Required Parameters	Description
`list_workspaces`	—	Show available workspaces
`list_characters`	— (optional: gender)	Browse AI avatar characters
`list_voices`	locale (e.g. `"en"`)	Browse voices (optional: gender filter)
`confirm_fabric_video`	script, voiceId, characterId	Preview video details before creating
`create_fabric_video`	script, voiceId, characterId	Create a talking-head video (optional: aspectRatio)
`get_generation_status`	jobId	Check video generation progress
`get_credit_balance`	—	Check remaining VEED credits

Blotato Platform Configuration

Each platform node needs its accountId configured (select from dropdown after connecting Blotato credentials):

Platform	Extra Configuration
TikTok	—
YouTube	Title, privacy status (`private` by default), notify subscribers
Instagram	—
LinkedIn	—
Facebook	Page ID (select from dropdown)
Twitter / X	—
Threads	—
Bluesky	—
Pinterest	Board ID

Disable any platform node you don't use.

Caption Configuration

Edit the ⚙️ Set Caption node to customize what gets posted:

caption: defaults to first 200 characters of the agent's response
video_url: automatically extracted from the VIDEO_READY: marker

Conversation Examples

User Says	Agent Does
"Hi, what can you do?"	Introduces itself and explains video creation capabilities
"Create a video about AI trends"	Asks about character/voice preferences, then guides through creation flow
"Show me available characters"	Calls `list_characters`, formats results for easy selection
"Use a female English voice"	Calls `list_voices` with locale `"en"` and gender filter, shows options
"Yes, create it!"	Calls `create_fabric_video`, then immediately checks `get_generation_status`
"Is my video ready?"	Calls `get_generation_status` with the last jobId from memory
Taps "Approve"	Video uploads to Blotato, publishes to all 9 platforms, summary sent
Taps "Reject"	"No problem! Your video won't be published to social media."

Output

Per Video Generated

Asset	Format	Delivered Via
Video URL	VEED hosted MP4 link	Telegram message
Approval prompt	Approve/Reject buttons	Telegram sendAndWait
Social media posts	Video + caption	TikTok, YouTube, Instagram, LinkedIn, Facebook, X, Threads, Bluesky, Pinterest
Publish summary	Text confirmation	Telegram message

Estimated Costs Per Video

Service	Usage	Approximate Cost
OpenAI gpt-5-nano	~1-3K tokens per conversation turn	~$0.005-0.02
VEED Fabric	1 video render (~8 credits/sec)	~$0.10-0.20
Blotato	Media upload + 9 platform posts	Included in paid plan
Telegram Bot API	Messages	Free
Total		~$0.10-0.25 per video

> Costs vary based on conversation length, video duration, and current API pricing.

Setup Checklist

Step 1: Import Workflow

Import create-and-publish-ai-videos-from-telegram-chat-with-veed-and-blotato.json into n8n

Step 2: Install Blotato Community Node

Go to Settings → Community Nodes → Install
Enter @blotato/n8n-nodes-blotato and install

Step 3: Create Telegram Bot

Open Telegram and message @BotFather
Send /newbot and follow the prompts to create your bot
Copy the bot token provided by BotFather

Step 4: Configure n8n Credentials

Click on 📩 Telegram Trigger node → Add Telegram Bot credential with your token
Click on 🧠 OpenAI Chat Model node → Add OpenAI API Key credential
Click on 🎬 VEED MCP Tools node → Add MCP OAuth2 credential with your VEED OAuth2 client credentials
Click on 📤 Send Agent Response node → Select the same Telegram Bot credential
Click on 📩 Publish to Social Media? node → Select the same Telegram Bot credential
Click on 📤 Upload Video to Blotato node → Add Blotato API credential (from blotato.com settings)

Step 5: Configure Blotato Platforms

Open each platform node (TikTok, YouTube, Instagram, etc.)
Select your connected account from the accountId dropdown
For YouTube: set title and privacy preferences
For Facebook: select your Page from the dropdown
For Pinterest: set Board ID
Disable any platform nodes you don't need

Step 6: Activate & Test

Activate the workflow by clicking Publish and toggling it active
Send a test message to your bot in Telegram (e.g., "Hi, what can you do?")
Verify the bot responds with its capabilities
Create a video and test the full flow including the approval prompt
Approve publishing and verify posts appear on your social accounts

Limitations & Notes

Technical Limitations

Telegram activation: The workflow must be published and active — simply executing it is not enough for the Telegram trigger to receive messages.
Memory window: Only the last 20 messages are retained per conversation. Older context is lost.
VEED processing: Video generation takes 1-5 minutes. The agent reports status but the user must wait.
Concurrent users: Multiple users are supported — each Telegram chat gets independent conversation memory keyed by chat.id.
Approval timeout: The publish prompt expires after 24 hours if not answered.
VIDEO_READY marker: The agent must include VIDEO_READY: <url> in its response for the publishing flow to trigger. This is enforced via the system prompt.
Blotato paid plan: API access requires a paid Blotato subscription.

Content Considerations

The AI agent autonomously decides which VEED tools to use based on the user's request
Users can request specific characters, voices, and scripts through natural conversation
The agent cannot edit or modify videos after creation
Video output depends on available VEED characters and voices
Each second of generated video costs approximately 8 VEED credits
Published captions default to the first 200 characters of the agent's response — edit the ⚙️ Set Caption node to customize

Best Practices

Set bot commands: Use @BotFather's /setcommands to add help commands for your users
Test with simple requests first: Start with "list available characters" before attempting full video creation
Monitor token usage: Longer conversations consume more OpenAI tokens per turn
Customize the system prompt: Tailor the agent's persona, default locale, and guidelines to your use case
Disable unused platforms: Disable platform nodes you haven't connected to avoid errors
YouTube defaults to private: Videos are published as private by default — change in the YouTube node if needed

Troubleshooting

Issue	Solution
Bot not responding	Ensure workflow is published and active, not just executed manually
"Unauthorized" from Telegram	Verify bot token is correct in n8n Telegram credential
VEED MCP connection failed	Re-authorize the VEED OAuth2 credential in n8n
Agent doesn't use VEED tools	Verify 🎬 VEED MCP Tools node is connected to the AI Agent node
Memory not working across messages	Confirm session key expression `{{ $('📩 Telegram Trigger').item.json.message.chat.id }}` is correct
Video generation timeout	VEED processing can take up to 5 minutes — agent should poll `get_generation_status`
"Model not found" error	Verify OpenAI API key has access to gpt-5-nano model
No approval prompt after video	Check the agent includes `VIDEO_READY:` marker — verify system prompt is intact
Blotato upload fails	Verify Blotato API credential is valid and plan is active
Platform publish fails	Ensure `accountId` is configured in the failing platform node
"Can't parse entities" error	The Send Agent Response node should have no `parse_mode` set (plain text)
Blotato node not found	Install `@blotato/n8n-nodes-blotato` via Settings → Community Nodes

Version History

Version	Date	Changes
1.0	Mar 2026	Initial release with Telegram bot, AI Agent, VEED MCP integration, conversation memory
2.0	Apr 2026	Added Blotato multiplatform publishing (9 platforms), Telegram approval flow, video URL extraction, caption configuration

Credits

Built with:

n8n - Workflow automation
OpenAI - AI agent reasoning (gpt-5-nano)
VEED - AI video generation (via MCP)
Blotato - Multiplatform social media publishing
Telegram - Chat interface & approval flow
LangChain - Agent framework and memory

VEED

4 workflows

Complexity

advanced

Published 24 Mar 2026

Likes 0

View on n8n.io Download Workflow

Install path: /data/workflows/14290/14290.json

Share Your Workflow

Have a useful automation to share? Publish it and help the community.

Submit Your Template How to Submit

Related Workflows

Create LinkedIn post drafts from Fireflies meetings with GPT-4o-mini, Drive and Slack

### Description Connect Fireflies to this workflow once and every meeting you record becomes a LinkedIn post draft automatically. The moment Fireflies finishes transcribing a call, it fires a signal to the workflow — which fetches the full transcript, extracts real insights, and uses GPT-4o-mini to write a 180–280 word scroll-stopping post with a hook, key learnings, and hashtags. The finished draft is saved to Google Drive and previewed in Slack so you can review and publish when ready. Built for founders, consultants, and sales leaders who want a consistent LinkedIn presence without spending time writing from scratch after every call. --- ## What This Workflow Does - **Triggers automatically when a call ends** — Fireflies sends a signal the moment transcription completes, so no manual input is ever needed - **Validates every incoming signal** — Checks that the signal contains a valid meeting ID and silently discards invalid or test pings - **Extracts real meeting insights** — Pulls speaker dialogue, Fireflies-detected pricing and question sentences, keywords, overview, and sentiment from the full transcript - **Writes a structured LinkedIn post** — GPT-4o-mini produces a hook, a specific insight paragraph, 3–5 emoji learnings, a closing question, and hashtags — all grounded in your actual meeting content - **Saves a complete Google Doc** — Stores the post alongside meeting reference details, participants, keywords, action items, and a link back to the Fireflies transcript - **Previews the post in Slack** — Posts the first 350 characters of the draft to your Slack channel so your team can review before the post goes live - **Exits cleanly for incomplete transcripts** — If Fireflies hasn't finished processing yet, the workflow stops silently without errors --- ## Setup Requirements ### Tools Needed - n8n instance (self-hosted or cloud) - Fireflies.ai account with webhook access - OpenAI account with GPT-4o-mini API access - Google Drive (one folder where posts will be saved) - Slack workspace with OAuth2 app configured ### Credentials Required - Fireflies API key (pasted directly into **5. Set — Config Values**) - OpenAI API key - Google Drive OAuth2 - Slack OAuth2 **Estimated Setup Time: 15–20 minutes** --- ## Step-by-Step Setup 1. **Import the workflow** — Open n8n → Workflows → Import from JSON → paste the workflow JSON → click Import 2. **Activate the workflow and copy the webhook URL** — Toggle the workflow to Active → click on node **1. Webhook — Fireflies Transcript Done** → copy the webhook URL shown 3. **Register the webhook in Fireflies** — Log in to fireflies.ai → go to Settings → Developer Settings → Webhooks → paste the webhook URL → save 4. **Get your Fireflies API key** — In Fireflies, go to Settings → Integrations → copy your API key 5. **Fill in Config Values** — Open node **5. Set — Config Values** → replace all placeholders: | Field | What to enter | |---|---| | `YOUR_FIREFLIES_API_KEY` | Your Fireflies API key from step 4 | | `YOUR_GOOGLE_DRIVE_FOLDER_ID` | The folder ID from your Google Drive URL (the string after `/folders/` in the URL when you open the folder) | | `#content-team` | Your Slack channel name including the `#` | | `YOUR FULL NAME` | The author's full name (used in the post sign-off) | | `YOUR JOB TITLE` | The author's job title (e.g. CEO, SEO Consultant) | | `YOUR COMPANY NAME` | Your company name (used in the AI prompt) | 6. **Connect OpenAI** — Open node **11. OpenAI — GPT-4o-mini Model** → click the credential dropdown → add your OpenAI API key → test the connection 7. **Connect Google Drive** — Open node **13. Google Drive — Save LinkedIn Post** → click the credential dropdown → add Google Drive OAuth2 → sign in with your Google account → authorize access 8. **Connect Slack** — Open node **14. Slack — Send Post Preview** → click the credential dropdown → connect your Slack workspace via OAuth2 → invite the n8n bot to your channel in Slack (`/invite @n8n`) > ⚠️ **The workflow must be Active before registering the webhook in Fireflies.** An inactive workflow will not receive signals from Fireflies. Activate first, then paste the URL. --- ## How It Works (Step by Step) **Step 1 — Webhook: Fireflies Transcript Done** This step listens for a signal from Fireflies. Every time Fireflies finishes transcribing a meeting, it sends a POST request to this webhook URL containing the meeting ID. No manual trigger is needed — it fires automatically after every recorded call. **Step 2 — Code: Extract Meeting ID** The meeting ID is extracted from the incoming signal. Fireflies can send the payload in several different formats, so this step checks all possible locations and pulls the ID safely. If no meeting ID is found at all, a flag is set to mark the signal as invalid. **Step 3 — IF: Valid Meeting ID?** This is the first gate check. If a valid meeting ID was found (YES path), the workflow continues to fetch the transcript. If the signal was invalid or contained no meeting ID (NO path), the workflow routes to **4. Set — Invalid Webhook Skip** and stops cleanly. **Step 4 — Set: Invalid Webhook Skip** This step handles the invalid signal case. It sets a brief message confirming the webhook was skipped and the workflow ends here for that trigger. **Step 5 — Set: Config Values** Your Fireflies API key, Google Drive folder ID, Slack channel, author name, author title, and company name are stored here. The validated meeting ID from step 2 is also carried forward so the transcript fetch can use it directly. **Step 6 — HTTP: Fetch Transcript** A request is sent to the Fireflies API using your API key and the meeting ID. It retrieves the complete transcript including all sentences with speaker labels, AI-detected pricing and task sentences, keyword summary, overview, gist, bullet points, and sentiment percentages. **Step 7 — Code: Process Transcript Data** The raw transcript is processed into clean, usable fields. All sentences are combined into a readable text block (limited to 5,000 characters for GPT efficiency). Fireflies-flagged pricing sentences, question sentences, and task sentences are extracted separately. Sentiment percentages, keywords, action items, and overview are all pulled out. A formatted document title is generated automatically using the meeting name and date. If the transcript is empty or not yet available, a flag is set for the next gate check. **Step 8 — IF: Transcript Ready?** This is the second gate check. If transcript data is available (YES path), the workflow moves to AI post writing. If Fireflies hasn't finished processing the transcript yet (NO path), the workflow routes to **9. Set — Transcript Not Ready Skip** and stops cleanly without errors. **Step 9 — Set: Transcript Not Ready Skip** This step handles the not-ready case. It logs the meeting ID and a message confirming the transcript was skipped. The workflow ends here for that run. **Step 10 — AI Agent: Write LinkedIn Post** GPT-4o-mini receives the author details, meeting context, Fireflies summary, bullet points, keywords, action items, questions raised in the call, and the transcript excerpt. It writes a 180–280 word LinkedIn post following a fixed structure: a scroll-stopping hook (not starting with "I" or "We"), a specific insight paragraph in first person, 3–5 emoji key learnings pulled from real transcript content, a closing question or call to action, and 4–5 hashtags. A sign-off with the author's name and title is added at the end. **Step 11 — OpenAI: GPT-4o-mini Model** This is the language model powering the writing step. It runs at temperature 0.8 for creative, varied output and is capped at 700 tokens to keep the post within the target word count. **Step 12 — Code: Build Doc and Slack Message** The AI-generated post is assembled into a complete Google Doc with the post text at the top, followed by meeting reference details: title, date, duration, participants, Fireflies transcript link, keywords, and action items. A Slack preview is also built here — the first 350 characters of the post plus meeting details and a link back to the Fireflies transcript. **Step 13 — Google Drive: Save LinkedIn Post** The complete document is saved to your specified Google Drive folder. The file is named automatically using the meeting title and date (e.g. "LinkedIn Post — Client Strategy Call — 14 Apr 2025"). **Step 14 — Slack: Send Post Preview** The preview message is posted to your Slack channel at the same time the Google Doc is being saved. Your team sees the post hook and first paragraph instantly, with the full document link available in Drive for review before publishing. --- ## Key Features ✅ **Fully automatic — zero manual trigger** — Fireflies fires the workflow the moment any call transcript is ready, no human action needed ✅ **Two validation gates** — Invalid webhook signals and unready transcripts both exit cleanly without causing errors or empty posts ✅ **Grounded in real content** — The AI prompt feeds actual transcript sentences, keywords, bullet points, and action items so posts are specific, not generic ✅ **Fixed post structure every time** — Hook, insight paragraph, emoji learnings, closing CTA, hashtags, and sign-off are enforced on every run ✅ **Auto-named Google Docs** — Files are named by meeting title and date automatically so your Drive folder stays organized without any manual renaming ✅ **Slack preview before publishing** — Your team sees the draft before it goes live — one review step, no surprises ✅ **Handles all Fireflies payload formats** — The extraction step checks every possible payload structure so the webhook never silently fails due to a format change ✅ **Temperature tuned for creative writing** — GPT runs at 0.8 so each post has a natural, human tone rather than a repetitive AI pattern --- ## Customisation Options **Change the post length target** — In node **10. AI Agent — Write LinkedIn Post**, edit the instruction from "180 to 280 words" to a different range. Also adjust `maxTokens` in node **11. OpenAI — GPT-4o-mini Model** accordingly (e.g. set to 900 for longer posts). **Add a second post format** — After node **10. AI Agent — Write LinkedIn Post**, add a second AI Agent step with a different prompt structure (e.g. a short 3-sentence insight post or a carousel-style numbered list) to generate two post options per call instead of one. **Route posts by meeting type** — In node **5. Set — Config Values**, add a `postCategory` field. Then add an IF check after step 7 that reads the meeting title — if it contains "demo" or "sales", use a sales-focused prompt; if it contains "team" or "internal", use a thought leadership prompt. **Save to a dated subfolder in Drive** — In node **12. Code — Build Doc and Slack Message**, generate a folder path string using the meeting date (e.g. `2025/April`) and use the Google Drive step to create or find that subfolder before saving, keeping your Drive organized by month automatically. **Add a Notion database entry** — After node **13. Google Drive — Save LinkedIn Post**, add a Notion API HTTP request to create a new row in a content calendar database with the post title, meeting date, status (Draft), and Google Drive link for content planning visibility. --- ## Troubleshooting **Workflow not triggering when a call ends:** - Confirm the workflow is Active before expecting Fireflies to fire it — inactive workflows do not receive webhooks - Log in to Fireflies → Settings → Developer Settings → Webhooks → confirm the webhook URL is saved correctly and matches the URL from node **1. Webhook — Fireflies Transcript Done** - Check that your Fireflies plan includes webhook support — some plans restrict this feature **Fireflies API key error or empty transcript:** - Confirm `YOUR_FIREFLIES_API_KEY` in node **5. Set — Config Values** is replaced with your actual key — not the placeholder text - Get your key from fireflies.ai → Settings → Integrations → API Key - If the transcript returns empty, the call may not have been processed yet by Fireflies — the workflow exits cleanly via **9. Set — Transcript Not Ready Skip** in this case **OpenAI not generating the post:** - Confirm the API key is connected in node **11. OpenAI — GPT-4o-mini Model** and your account has available credits - Check the execution log of node **10. AI Agent — Write LinkedIn Post** for the raw error message - If the post is under 50 characters, node **12. Code — Build Doc and Slack Message** catches this and outputs a failure message instead of a broken doc **Google Drive not saving the file:** - Confirm the Google Drive OAuth2 credential in node **13. Google Drive — Save LinkedIn Post** is connected and not expired — re-authorize if needed - Check that `YOUR_GOOGLE_DRIVE_FOLDER_ID` in node **5. Set — Config Values** is the folder ID from your Drive URL, not the full URL — copy only the string after `/folders/` - Make sure the Google account you authorized has write access to the target folder **Slack preview not arriving:** - Confirm the Slack OAuth2 credential in node **14. Slack — Send Post Preview** is connected and authorized - Check that the channel name in node **5. Set — Config Values** includes the `#` prefix and matches your Slack channel exactly - Type `/invite @n8n` in the target Slack channel to ensure the bot has permission to post --- ## Support Need help setting this up or want a custom version built for your team or agency? 📧 Email: [[email protected]]([email protected]) 🌐 Website: [https://www.incrementors.com/](https://www.incrementors.com/)

View

Create AI coloring book pages from Google Sheets and save to Google Drive with Stable Diffusion

This workflow automatically generates printable coloring pages from themes stored in Google Sheets. It reads configuration data such as theme, style, and keywords, creates prompts, generates multiple image variations using AI, and saves the results to Google Drive. Finally, it logs metadata to Google Sheets for easy tracking and management.

View

Generate Instagram posts with OpenAI, RSS news, and auto image posting

## What this workflow does This workflow automatically generates and publishes Instagram content using AI. It: - Generates content ideas using AI - Creates images automatically - Edits images (resize/format) - Publishes directly to Instagram ## How it works 1. Trigger starts the workflow (manual or scheduled) 2. AI generates a content idea and prompt 3. Image is generated via API 4. Image is processed and formatted 5. Post is published automatically ## Setup - Connect your OpenAI (or AI provider) credentials - Add your image generation API key - Connect your Instagram account - (Optional) Connect Google Drive for storage Setup time: 15–20 minutes

View

Need Custom Automation?

Get help designing a custom n8n workflow that connects your stack and fits your process.

Create and publish AI videos from Telegram with VEED and Blotato

Workflow preview

Overview

Create & Publish AI Videos from Telegram Chat with VEED and Blotato

Overview

What It Does

Flow Breakdown

Required Connections

n8n Credentials

Community Node Required

Configuration Options

AI Agent System Prompt

Agent Configuration

Available VEED MCP Tools

Blotato Platform Configuration

Caption Configuration

Conversation Examples

Output

Per Video Generated

Estimated Costs Per Video

Setup Checklist

Step 1: Import Workflow

Step 2: Install Blotato Community Node

Step 3: Create Telegram Bot

Step 4: Configure n8n Credentials

Step 5: Configure Blotato Platforms

Step 6: Activate & Test

Limitations & Notes

Technical Limitations

Content Considerations

Best Practices

Troubleshooting

Version History

Credits