Colorize & Animate Old Photos with AI, Auto-Publish to Social Media
Overview
This workflow transforms old, black-and-white or sepia photographs into vibrant, animated videos using AI, then automatically saves the result to Google Drive and publishes it across multiple social media platforms. It combines image colorization (FLUX Kontext), AI video animation (Kling Video AI), and cross-platform social media posting in a single automated pipeline.
Perfect for historians, archivists, family history enthusiasts, or content creators looking to breathe new life into vintage imagery. The workflow handles the entire process from user upload through final distribution, making it easy to create engaging social media content from historical photos.
Workflow Steps
-
Photo Upload Form (Form Trigger — No auth) — Displays a web form where users upload an old photo and optionally provide a custom animation description. The form is accessible at
/form/animate-photo-form. -
Upload Image to imgbb (HTTP Request — API Key auth via query parameter) — Uploads the submitted photo to imgbb.com's free image hosting service. Uses multipart form-data to send the binary image file and an API key (configured in the node's body parameters).
-
Colorize Image (HTTP Request — Header Auth) — Sends the uploaded image URL to FLUX Kontext (fal.ai) with a prompt to colorize, denoise, and enhance the photo. Uses HTTP Header authentication with a custom API key.
-
Wait for Colorization (Wait — No auth) — Pauses execution to allow the colorization process to complete. Uses a webhook-based wait mechanism.
-
Check Colorization Status (HTTP Request — Header Auth) — Polls the FLUX Kontext queue status endpoint to check if colorization is complete. Uses the request ID from step 3.
-
Colorization Completed? (IF — No auth) — Evaluates whether the status returned is "COMPLETED". If yes, proceeds to fetch the result; if not, loops back to the Wait node for continued polling.
-
Get Colorized Image (HTTP Request — Header Auth) — Retrieves the final colorized image URL from FLUX Kontext once processing is complete.
-
Animate Image (HTTP Request — Header Auth) — Sends the colorized image to Kling Video AI (fal.ai) with an animation prompt. Uses the user's optional custom description, or defaults to a natural movement prompt. Configures 5-second video duration at standard quality.
-
Wait for Animation (Wait — No auth) — Pauses for 60 seconds to allow video generation to progress before checking status.
-
Check Animation Status (HTTP Request — Header Auth) — Polls the Kling Video queue status endpoint using the request ID from step 8.
-
Animation Completed? (IF — No auth) — Checks if animation status is "COMPLETED". If yes, fetches the video; if not, loops back to the Wait node.
-
Get Animated Video (HTTP Request — Header Auth) — Retrieves the final animated video URL from Kling Video AI.
-
Download Video (HTTP Request — No auth) — Downloads the video file from the URL returned in step 12.
-
Upload to Google Drive (Google Drive — OAuth2) — Saves the downloaded video to the user's Google Drive root folder with a timestamped filename (e.g.,
animated-photo-20250101-120000.mp4). -
Final Results (Set — No auth) — Compiles a structured output containing success flag, message, colorized image URL, animated video URL, Google Drive link, and processing timestamp.
-
Upload Post (Upload Post — API Key auth) — Automatically publishes the animated video to Instagram (as Reels), X (Twitter), YouTube, and Facebook using the upload-post API service.
Setup Instructions
Required Accounts & Credentials
-
imgbb.com — Free image hosting. Sign up at imgbb.com and get your API key from the account dashboard.
-
FAL.AI — AI processing platform. Create an account at fal.ai and generate an API key. This key is used for both FLUX Kontext (colorization) and Kling Video (animation).
-
Google Drive — Connect your Google account via OAuth2 in n8n. You'll need a Google Cloud project with the Drive API enabled.
-
Upload Post API — Service for cross-platform social media posting. Sign up at uploadpost.com and obtain your API credentials.
Configuration Steps
- In the Upload Image to imgbb node, replace
generate_token_and_addin the body parameters with your actual imgbb API key. - In all HTTP Request nodes using Header Auth, configure the credential with your FAL.AI API key (typically as
Authorization: Key YOUR_API_KEY). - In the Upload to Google Drive node, authenticate with your Google account.
- In the Upload Post node, replace
ADD_UPLOAD_POST_USERwith your Upload Post API user identifier and configure the credential.
Use Cases & Variations
- Family History Projects — Automatically restore and animate old family photos for sharing with relatives.
- Historical Archives — Museums and archives can batch-process historical photographs for engaging social media content.
- Content Marketing — Create unique, nostalgic video content for brand storytelling on social platforms.
- Educational Content — Bring historical figures and events to life for educational videos.
- Variation Ideas:
- Add a Slack notification when processing completes
- Store results in a database for tracking
- Add email delivery of the final video
- Create a gallery webpage showing before/after comparisons
- Add watermarking or branding to the output video
Workflow JSON
{
"id": "NkkWMHiRAY5uPHmf",
"meta": {
"instanceId": "3378b0d68c3b7ebfc71b79896d94e1a044dec38e99a1160aed4e9c323910fbe2",
"templateCredsSetupCompleted": true
},
"name": "Convert Old Photos to AI Videos And Auto-Publish in FB, IG, YT & X",
"tags": [],
"nodes": [
{
"id": "b9ae8c3f-21f4-4aaf-9352-824d2abcf430",
"name": "Photo Upload Form",
"type": "n8n-nodes-base.formTrigger",
"position": [
-60,
120
],
"webhookId": "animate-photo-form",
"parameters": {
"path": "animate-photo-form",
"options": {},
"formTitle": "Colorize and Animate Old Photos",
"formFields": {
"values": [
{
"fieldType": "file",
"fieldLabel": "Upload Old Photo",
"requiredField": true
},
{
"fieldType": "textarea",
"fieldLabel": "Custom Animation Description (Optional)",
"placeholder": "Describe how you'd like the photo to be animated (e.g., 'make the person smile and blink')"
}
]
},
"formDescription": "Upload an old photo to colorize and animate it with AI"
},
"typeVersion": 2.1
},
{
"id": "6bb93365-9c3d-4c18-a1cc-328d45b70b2f",
"name": "Workflow Description",
"type": "n8n-nodes-base.stickyNote",
"position": [
-40,
-740
],
"parameters": {
"color": 3,
// ... truncated (copy to see full JSON)How to Import This Workflow
- 1Copy the workflow JSON above using the Copy Workflow JSON button.
- 2Open your n8n instance and go to Workflows.
- 3Click Import from JSON and paste the copied workflow.
Don't have an n8n instance? Start your free trial at n8nautomation.cloud
Related Templates
Automated Blog Post Creation from News with AI and Blogger
This workflow automates the entire process of creating a fully SEO-optimized blog post from a news article. It fetches a trending technology news headline from Mediastack, generates relevant images from Pexels, uses two AI agents (via OpenRouter) to produce a title, slug, meta description, and a complete WordPress-compatible HTML blog post, then posts it directly to Blogger and sends you a Telegram notification. It's perfect for content marketers, bloggers, or anyone who wants to consistently publish fresh, data-driven content without manual effort. Node Breakdown Schedule Trigger (No auth) — Runs the workflow at a set interval (configured every minute by default, but you should change it to daily or hourly). Mediastack News (API Key auth via query parameter) — Fetches the latest technology news article in English from the Mediastack API. Parameters: set to . Genarate image (API Key auth via header, ) — Searches Pexels for up to 2 images related to the news title. Parameters: = , = 2. Send a text message1 (Telegram bot token auth) — Sends a Telegram message with the generated image URLs to the chat ID stored in . AI Agent (Uses OpenRouter Chat Model — API Key auth) — This agent takes the news title and returns a JSON object with three fields: , , and (meta description). The prompt includes strict guidelines for SEO-friendly output. OpenRouter Chat Model (API Key auth) — The language model for the first AI agent, using . Parsing (No auth) — A Code node that cleans the raw AI output (removes markdown code fences) and parses the JSON into usable fields. Copywriter AI Agent (Uses OpenRouter Chat Model2 — API Key auth) — This agent writes a complete 1,000-word SEO blog post in HTML format. It uses the title, meta, and the two images from Pexels. The prompt is very detailed, specifying structure, keyword placement, and styling. OpenRouter Chat Model2 (API Key auth) — Same model as the first, but used for the second agent. Cleanup HTML (No auth) — A Set node that removes any leftover htmlurlhttps://www.googleapis.com/blogger/v3/blogs/$vars.bloggerid/postsPOSThttpQueryAuthAuthorization$vars.telegramchatid$vars.bloggeridbusinesssports`) to match your niche. Multi-language Support — Modify the Mediastack query to fetch news in other languages, and adjust the AI prompts to write in that language. Custom Image Sources — Replace the Pexels node with another image API (e.g., Unsplash) or use a local image generation model. Different CMS — Swap the Blogger HTTP Request node with WordPress or any other CMS API (just change the URL and body format). Human-in-the-Loop — Add a Slack or email approval step before publishing to review the AI-generated content. Newsletter Integration — Instead of posting to a blog, send the formatted content as an email newsletter via Gmail or SendGrid.
Telegram RAG Chatbot with File Upload and Groq LLM
This workflow creates a Telegram chatbot that uses Retrieval-Augmented Generation (RAG) to answer questions based on documents you upload. Users can send PDF or CSV files to a Telegram chat, and the workflow processes them into a vector database. When a user then sends a text message, the AI agent retrieves relevant chunks from the stored documents and generates an answer using the Groq Llama 3.1 model. It's like having a personal assistant that learns from your files and responds via Telegram. Node-by-Node Walkthrough Telegram Message Trigger (Telegram Trigger, no authentication required on the node itself — authentication is handled via the Telegram Bot API credentials configured in the n8n credentials store). This trigger listens for all types of updates (messages, commands, etc.) from a Telegram bot. When a new update arrives, it starts the workflow. Get a chat1 (Telegram node, Telegram Bot API token auth). It extracts the from the incoming message and passes it to the next node, ensuring the AI agent knows which chat to reply to. AI Agent1 (LangChain Agent, no auth). This is the core of the workflow. It uses a system message that instructs the AI to answer only from the knowledge base. The agent has access to the Groq Chat Model as its language model and the Retrieve documents tool to fetch relevant document chunks. It also uses Simple Memory to keep conversation context within a session (keyed by the Telegram chat ID). Groq Chat Model (Groq LLM, Groq API key auth). Uses the model. This provides fast, coherent answers. Simple Memory (Memory Buffer Window, no auth). Stores the last few turns of conversation to give the agent context. The session key is set to the Telegram chat ID from the trigger. Retrieve documents (Vector Store as Tool, no auth). This tool allows the agent to query the in-memory vector store. It returns the top 10 most similar document chunks. Embeddings HuggingFace Inference1 (Hugging Face Inference, Hugging Face API key auth). Generates embeddings for the user's query so the vector store can find relevant documents. Upload your file here (Form Trigger, no auth). This form trigger provides a web form where users can upload or files. The uploaded file(s) are passed to the Default Data Loader1. Default Data Loader1 (Document Default Data Loader, no auth). Converts the uploaded binary file into a LangChain document object. Recursive Character Text Splitter (Text Splitter, no auth). Splits the document into chunks of up to 3,000 characters with 200 character overlap. This ensures the vector store indexes manageable pieces. Simple Vector Store (In-Memory Vector Store, no auth). Stores the document chunks along with their embeddings. The embedding model used is Embeddings HuggingFace Inference. Embeddings HuggingFace Inference (Hugging Face Inference, Hugging Face API key auth). Generates embeddings for each document chunk before storing them. Reply in Telegram1 (Telegram node, Telegram Bot API token auth). Sends the AI agent's output back to the same Telegram chat. Setup Instructions Telegram Bot: Create a bot via @BotFather and get its API token. In n8n, add a Telegram credential using this token. Groq: Sign up at GroqCloud to get an API key. Add a Groq credential in n8n. Hugging Face: Create a free account at Hugging Face and generate an Inference API token. Add a Hugging Face Inference credential in n8n. n8n Form Trigger: This node is built-in. Ensure your n8n instance is publicly accessible (or use a tunnel like ngrok) so the form can be accessed by users. Deploy: Activate the workflow. Share the Telegram bot username with users. They can upload files by visiting the form URL (the one generated by the Upload your file here node) and then send text messages to the bot. Use Cases and Variations Personal knowledge base: Upload company policies, technical documentation, or study materials and ask questions about them via Telegram. Customer support bot: Replace the file upload with an HTTP node that fetches FAQs from a database, and use the same RAG architecture to answer customer queries. Multi-user support: The session memory is already scoped by Telegram chat ID, so multiple users can use the bot simultaneously without interfering. Switch LLM: Replace Groq with OpenAI, Anthropic, or any other supported LLM provider by changing the model node. Persistent vector store: Swap the in-memory vector store for Pinecone, Weaviate, or Qdrant to retain documents across restarts.
AI Blog Generator For WordPress Posts
AI Blog Generator For WordPress Posts This workflow automates the creation of blog post drafts by combining an n8n form, OpenAI's language model, and WordPress. It's designed for content creators, marketers, and bloggers who want to overcome writer's block and streamline their content pipeline. Instead of starting from a blank page, you submit a topic, target audience, and key points through a simple form, and the workflow generates a structured, well-written draft ready for your review and editing in WordPress. The core value of this workflow is its efficiency. It transforms a time-consuming task—writing a first draft—into a quick, structured process. By keeping the output as a 'draft' in WordPress, it ensures that nothing goes live without your final approval, maintaining editorial control. The workflow also includes thoughtful touches like automatic retries for the AI call and clear instructions for troubleshooting, making it robust and user-friendly. Workflow Nodes and Steps Here is a step-by-step breakdown of the workflow: Setup — read me first (Sticky Note) — Provides an overview, setup time, level, and links to the creator's site. How it runs (Sticky Note) — Explains the workflow's logic and data flow. If something breaks (Sticky Note) — Offers guidance on error handling and setting up an error workflow. Draft Request Form (Form Trigger) — This node hosts a web form with fields for 'Topic', 'Audience', and 'Key points (one per line)'. It starts the workflow when the form is submitted. (No auth required for the form itself). Write Draft (OpenAI) — This node uses the model to generate the blog post. It receives the form data and uses a carefully crafted prompt to produce a title and body in HTML format. (API Key auth). Split Title and Body (Code) — A JavaScript code node that parses the AI's response, extracting the title and the HTML body content into separate fields for the next step. (No auth). Create WordPress Draft (WordPress) — This node creates a new post in WordPress with the generated title and content, setting the status to 'draft' so it's not published immediately. (Application Password auth). Setup Instructions To use this workflow, you will need the following: OpenAI Account: You need an API key from OpenAI. Create an account at platform.openai.com, go to the API keys section, and create a new secret key. Add this key to the 'Write Draft' node's credentials. WordPress Site: You need a self-hosted WordPress.org site (not WordPress.com). To connect, you'll need to generate an Application Password. In your WordPress admin dashboard, go to Users > Profile and scroll down to the 'Application Passwords' section. Create a new one and use those credentials in the 'Create WordPress Draft' node. Activate the Workflow: After connecting your credentials, activate the workflow in n8n. The 'Draft Request Form' node will provide a production URL. Bookmark this URL to access your form. Use Cases and Variations Content Calendars: Integrate this with a Google Sheets node to log all generated drafts and their statuses. Multi-Platform Publishing: Add a step to convert the HTML draft to Markdown and send it to other CMSs like Ghost or Dev.to. SEO Optimization: Insert a node to analyze the generated content for keywords or readability scores before creating the WordPress post. Team Collaboration: Instead of a public form, trigger the workflow from a Slack command or email, allowing your team to submit topics without leaving their communication tools. Different Content Types: Modify the prompt in the 'Write Draft' node to generate other content formats like product descriptions, social media posts, or email newsletters.