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
Telegram AI Bot with DALL-E Image Generation using LangChain
Overview This workflow creates an intelligent Telegram bot that leverages OpenAI's GPT-4o and DALL-E 3 models through n8n's LangChain integration. The bot can hold context-aware conversations (remembering the last 10 messages per user) and generate images on demand—all via simple Telegram messages. It's ideal for building personal assistants, creative bots, or customer support agents that need visual output. Node-by-Node Walkthrough Here's every node in the workflow, along with its authentication method and key configuration: Listen for incoming events (Telegram Trigger — No auth; bot token set in node credential) – Listens for all types of Telegram updates (messages, commands, etc.). No authentication parameters are required directly on the node; the Telegram bot token is configured via the node's credential settings. AI Agent (LangChain Agent — No auth; relies on connected sub‑nodes) – The core of the workflow. It receives the incoming message text and uses the attached language model (OpenAI Chat Model), memory (Window Buffer Memory), and tools (Send back an image / Generate image in Dalle) to decide what action to take. OpenAI Chat Model (LangChain Chat Model — API Key auth via credential) – Uses with a temperature of 0.7 and frequency penalty of 0.2. This model powers the agent's text responses. Window Buffer Memory (LangChain Memory — No auth) – Stores the last 10 messages per user (keyed by Telegram chat ID) to maintain conversational context. Generate image in Dalle (LangChain HTTP Request Tool — API Key auth via credential) – A custom tool that sends a POST request to with model and a prompt (provided by the AI agent). The tool description tells the agent to call it when the user asks to draw something. Send back an image (Telegram Tool — API Key auth via Telegram credential) – Sends a file (image URL from the DALL-E response) to the user's chat ID using the operation. This is exposed as a tool the AI agent can call. Send final reply (Telegram Node — API Key auth via Telegram credential) – Sends the AI agent's text output (from ) back to the user. Note: On error, the workflow continues to the error output (useful for debugging). Detailed Flow The Telegram Trigger catches any incoming message from your bot. The message text is passed to the AI Agent. The agent uses the OpenAI Chat Model to understand the request and generate a response. It also checks the Window Buffer Memory for recent conversation history. If the user asks for an image, the agent calls the Generate image in Dalle tool, which returns an image URL. The agent then uses the Send back an image tool to send that image to the user. For all other requests, the agent produces a text response, which is sent via the Send final reply node. Setup Instructions Telegram Bot – Create a bot via @BotFather and get the API token. In n8n, create a Telegram credential and paste the token. OpenAI Account – Obtain an API key from OpenAI's platform. Create an credential in n8n and paste the key. This credential is used by both the Chat Model and the DALL-E tool. Workflow Activation – After configuring the credentials, activate the workflow. n8n will automatically set up the webhook for the Telegram trigger (no manual URL needed—n8n handles it internally). Test – Send a message to your bot on Telegram. Try asking a question or say “Draw a cat wearing a hat” to trigger image generation. Use Cases & Variations Personal Assistant – Extend with additional tools (web search, calendar lookup, weather API) to make a full‑fledged chatbot. Customer Support – Replace the OpenAI model with a fine‑tuned model or add a fallback to a human agent using n8n's error handling. Image Editor – Modify the DALL-E tool to accept style parameters or multiple images. Multi‑Language – Add a translation node before the AI agent to support multiple languages. Logging – Insert a database node (e.g., Google Sheets, PostgreSQL) to store conversation logs for analysis.
Convert Text to Speech Using OpenAI TTS API
Overview This workflow converts any text into natural-sounding speech using OpenAI's Text-to-Speech (TTS) API. It is ideal for generating audio content for accessibility, voiceovers, podcasts, or language learning. The workflow is triggered manually for testing, but can easily be adapted to run on a schedule, via webhook, or as part of a larger automation. Node-by-Node Breakdown When clicking "Test workflow" (Manual Trigger) — No auth. This node starts the workflow when you click the "Execute Workflow" button in the n8n editor. It has no parameters and is used for testing. Set input text and TTS voice (Set) — No auth. This node defines the text to be converted and the voice to use. It outputs a JSON object with two fields: - : The text you want to turn into speech (e.g., "The quick brown fox jumped over the lazy dog.") - : The voice model to use (e.g., "alloy"). Other options include "echo", "fable", "onyx", "nova", and "shimmer". Send HTTP Request to OpenAI's TTS Endpoint (HTTP Request) — API Key auth (via OpenAI credential). This node sends a POST request to with the following body parameters: - : (the TTS model) - : The text from the previous node (using expression ) - : The voice from the previous node (using expression ) The request is authenticated using an OpenAI API key stored in an n8n credential. The response is a binary MP3 audio file. Setup Instructions OpenAI Account: You need an OpenAI account with API access. Obtain an API key from the OpenAI dashboard. n8n Credential: In n8n, create a new credential of type "OpenAI". Paste your API key into the credential. Configure the HTTP Request Node: The node is already set to use the OpenAI credential. Ensure the credential is selected in the node's settings. Customize Text and Voice: Modify the and values in the Set node as needed. The maximum input length is 4,000 tokens. Use Cases and Variations Automated Podcast Generation: Replace the manual trigger with a Schedule Trigger to generate daily audio summaries from a news feed. Accessibility: Use a Webhook Trigger to accept text from a form or chat, then return the audio file to the user. Language Learning: Combine with a Translate node to convert foreign language text into speech. Content Creation: Integrate with a Google Drive node to save the generated MP3 files automatically. Voice Customization: Experiment with different voice options (alloy, echo, fable, etc.) to match the tone of your content.
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.