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

  1. 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.

  2. 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).

  3. 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.

  4. Wait for Colorization (Wait — No auth) — Pauses execution to allow the colorization process to complete. Uses a webhook-based wait mechanism.

  5. 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.

  6. 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.

  7. Get Colorized Image (HTTP Request — Header Auth) — Retrieves the final colorized image URL from FLUX Kontext once processing is complete.

  8. 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.

  9. Wait for Animation (Wait — No auth) — Pauses for 60 seconds to allow video generation to progress before checking status.

  10. Check Animation Status (HTTP Request — Header Auth) — Polls the Kling Video queue status endpoint using the request ID from step 8.

  11. Animation Completed? (IF — No auth) — Checks if animation status is "COMPLETED". If yes, fetches the video; if not, loops back to the Wait node.

  12. Get Animated Video (HTTP Request — Header Auth) — Retrieves the final animated video URL from Kling Video AI.

  13. Download Video (HTTP Request — No auth) — Downloads the video file from the URL returned in step 12.

  14. 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).

  15. 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.

  16. 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

  1. imgbb.com — Free image hosting. Sign up at imgbb.com and get your API key from the account dashboard.

  2. 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).

  3. Google Drive — Connect your Google account via OAuth2 in n8n. You'll need a Google Cloud project with the Drive API enabled.

  4. Upload Post API — Service for cross-platform social media posting. Sign up at uploadpost.com and obtain your API credentials.

Configuration Steps

  1. In the Upload Image to imgbb node, replace generate_token_and_add in the body parameters with your actual imgbb API key.
  2. In all HTTP Request nodes using Header Auth, configure the credential with your FAL.AI API key (typically as Authorization: Key YOUR_API_KEY).
  3. In the Upload to Google Drive node, authenticate with your Google account.
  4. In the Upload Post node, replace ADD_UPLOAD_POST_USER with 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
19 nodesmanual triggerAI
Sticky NoteHTTP RequestWaitIFGoogle DriveSetUpload Post

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

  1. 1Copy the workflow JSON above using the Copy Workflow JSON button.
  2. 2Open your n8n instance and go to Workflows.
  3. 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.

16 nodes

AI Chat Agent with OpenAI, Memory, and Web Search

Overview This workflow creates an intelligent AI chat agent that combines OpenAI's language model with conversational memory and real-time web search capabilities via SerpAPI. It is designed to power interactive chat applications where the AI can remember context across messages and fetch up-to-date information from the internet when needed. This is particularly useful for building customer support bots, research assistants, or any conversational interface that requires both knowledge retention and live data access. The workflow is triggered by incoming chat messages and processes them through an AI agent that coordinates between the language model, memory buffer, and search tool. The agent can decide when to use web search to answer questions that require current information, while maintaining conversation history for coherent multi-turn dialogues. Workflow Steps Manual Trigger (No auth) — This node allows you to manually start the workflow for testing purposes. It has no parameters configured and simply provides a button to execute the workflow on demand. When chat message received (No auth) — This is a webhook-based trigger that listens for incoming chat messages. It generates a unique webhook URL that you can integrate with your chat frontend or messaging platform. The parameter is empty, meaning default webhook behavior is used. AI Agent (No auth) — This is the core orchestrator node that manages the conversation flow. It coordinates between the OpenAI model, memory buffer, and SerpAPI tool. The agent decides which tool to use based on the user's query and maintains the conversation state. OpenAI Chat Model (API Key auth) — This node connects to OpenAI's GPT-4o-mini model to generate responses. It requires an OpenAI API key configured in n8n credentials. The parameter is set to , which is a cost-effective and fast model suitable for chat applications. The parameter is empty, using default model settings. Window Buffer Memory (No auth) — This node implements a sliding window memory that stores recent conversation history. It allows the AI to remember context from previous messages within a configurable window size. The parameters are empty, using default memory settings. SerpAPI (API Key auth) — This tool node enables web search functionality via SerpAPI (Google Search API). It requires a SerpAPI API key configured in n8n credentials. The parameter is empty, using default search settings. The agent calls this node when it determines that real-time web data is needed to answer a query. Setup Instructions To use this workflow, you need the following accounts and credentials: OpenAI Account: Sign up at platform.openai.com and create an API key. In n8n, create an "OpenAI" credential and paste your API key. SerpAPI Account: Register at serpapi.com and obtain an API key. In n8n, create a "SerpAPI" credential with your key. Webhook URL: After activating the workflow, copy the webhook URL from the "When chat message received" node. Integrate this URL into your chat application (e.g., a custom web chat widget, Slack app, or Telegram bot). Optional: Configure the memory window size in the "Window Buffer Memory" node if you want to limit or extend conversation context. Use Cases and Variations This workflow can be adapted for multiple scenarios: Customer Support Bot: Replace SerpAPI with a knowledge base tool (e.g., vector store or database lookup) to answer product-specific questions. Research Assistant: Keep SerpAPI for web search and add additional tools like Wikipedia or news APIs. Multi-Platform Chat: Connect the webhook to different messaging platforms (Slack, Discord, Telegram) by adding appropriate trigger nodes. Personal Assistant: Add calendar or email tools to let the AI manage schedules and send messages. Language Translation: Replace the OpenAI model with a translation-specific model or add a translation tool node. To extend the workflow, you can add more tool nodes (e.g., database queries, file operations) and connect them to the AI Agent. The agent will automatically learn to use new tools based on their descriptions.

6 nodes

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.

7 nodes

Ready to automate with n8n?

Get affordable managed n8n hosting with 24/7 support.