HumationHuman + Automation
Back to Catalog

Automate RSS to social media pipeline with AI, Airtable & GetLate for multiple platforms

Mikal Hayden-GatesMikal Hayden-Gates
188 views
2/3/2026
TranslationGoogle SheetsData LoggingGoogle TranslateAutomation
Official Page

Overview

Automates your complete social media content pipeline: sources articles from Wallabag RSS, generates platform-specific posts with AI, creates contextual images, and publishes via GetLate API. Built with 63 nodes across two workflows to handle LinkedIn, Instagram, and Bluesky—with easy expansion to more platforms.

Ideal for: Content marketers, solo creators, agencies, and community managers maintaining a consistent multi-platform presence with minimal manual effort.

How It Works

Two-Workflow Architecture:

  1. Content Aggregation Workflow
    • Monitors Wallabag RSS feeds for tagged articles (#to-share-linkedin, #to-share-instagram, etc.)
    • Extracts and converts content from HTML to Markdown
    • Stores structured data in Airtable with platform assignment
  2. AI Generation & Publishing Workflow
    • Scheduled trigger queries Airtable for unpublished content
    • Routes to platform-specific sub-workflows (LinkedIn, Instagram, Bluesky)
    • LLM generates optimized post text and image prompts based on custom brand parameters
    • Optionally generates AI images and hosts them on Imgbb CDN
    • Publishes via GetLate API (immediate or draft mode)
    • Updates Airtable with publication status and metadata

Key Features:

  • Tag-based content routing using Wallabag's native system
  • Swappable AI providers (Groq, OpenAI, Anthropic)
  • Platform-specific optimization (tone, length, hashtags, CTAs)
  • Modular design—duplicate sub-workflows to add new platforms in ~30 minutes
  • Centralized Airtable tracking with 17 data points per post

Set Up Steps

Setup time: ~45-60 minutes for initial configuration

  1. Create accounts and get API keys (~15 min)
    • Wallabag (with RSS feeds enabled)
    • GetLate (social media publishing)
    • Airtable (create base with provided schema—see sticky notes)
    • LLM provider (Groq, OpenAI, or Anthropic)
    • Image service (Hugging Face, Fal.ai, or Stability AI)
    • Imgbb (image hosting)
  2. Configure n8n credentials (~10 min)
    • Add all API keys in n8n's credential manager
    • Detailed credential setup instructions in workflow sticky notes
  3. Set up Airtable database (~10 min)
    • Create "RSS Feed - Content Store" base
    • Add 19 required fields (schema provided in workflow sticky notes)
    • Get Airtable base ID and API key
  4. Customize brand prompts (~15 min)
    • Edit "Set Custom SMCG Prompt" node for each platform
    • Define brand voice, tone, goals, audience, and image preferences
    • Platform-specific examples provided in sticky notes
  5. Configure platform settings (~10 min)
    • Set GetLate account IDs for each platform
    • Enable/disable image generation per platform
    • Choose immediate publish vs. draft mode
    • Adjust schedule trigger frequency
  6. Test and deploy
    • Tag test articles in Wallabag
    • Monitor the first few executions in draft mode
    • Activate workflows when satisfied with the output

Important: This is a proof-of-concept template. Test thoroughly with draft mode before production use. Detailed setup instructions, troubleshooting tips, and customization guidance are in the workflow's sticky notes.

Technical Details

  • 63 nodes: 9 Airtable operations, 8 HTTP requests, 7 code nodes, 3 LangChain LLM chains, 3 RSS triggers, 3 GetLate publishers
  • Supports: Multiple LLM providers, multiple image generation services, unlimited platforms via modular architecture
  • Tracking: 17 metadata fields per post, including publish status, applied parameters, character counts, hashtags, image URLs

Prerequisites

  • n8n instance (self-hosted or cloud)
  • Accounts: Wallabag, GetLate, Airtable, LLM provider, image generation service, Imgbb
  • Basic understanding of n8n workflows and credential configuration
  • Time to customize prompts for your brand voice

Detailed documentation, Airtable schema, prompt examples, and troubleshooting guides are in the workflow's sticky notes.

Category Tags

#social-media-automation, #ai-content-generation, #rss-to-social, #multi-platform-posting, #getlate-api, #airtable-database, #langchain, #workflow-automation, #content-marketing

Automate RSS to Social Media Pipeline with AI, Airtable, and GetLate for Multiple Platforms

This n8n workflow automates the process of fetching new articles from an RSS feed, generating AI-powered summaries and social media content, scheduling posts, and managing the content pipeline using Airtable. It's designed to streamline content distribution across various social media platforms.

What it does

This workflow performs the following key steps:

  1. Monitors RSS Feeds: Triggers when new items are published in a configured RSS feed.
  2. Fetches RSS Feed Content: Reads the content of the new RSS feed item.
  3. Generates AI Summary & Social Content:
    • Uses a Groq Chat Model (via LangChain) to generate a concise summary of the article.
    • Generates social media content (e.g., tweet, LinkedIn post) based on the article and summary.
    • Generates relevant hashtags.
    • Suggests a suitable image prompt for the article.
  4. Processes Image Prompt: Uses a Code node to refine the image prompt for consistency.
  5. Creates Image: (Potentially, though not explicitly shown in the provided JSON, an image generation step would follow the "Edit Image" node to create an image based on the prompt). The "Edit Image" node is present, suggesting image manipulation capabilities.
  6. Stores Content in Airtable: Adds the article details, AI-generated summary, social media content, hashtags, and image information to an Airtable base.
  7. Schedules Social Media Posts (via GetLate):
    • If the Airtable record indicates the content is ready for posting, it proceeds to schedule.
    • Uses an HTTP Request node to interact with the GetLate API to schedule the generated social media posts.
    • Handles different social media platforms (e.g., Twitter, LinkedIn) based on a "Social Platform" field.
  8. Updates Airtable Status: Marks the Airtable record as "Posted" or updates its status after scheduling.
  9. Conditional Logic: Uses "If" and "Switch" nodes to control the flow based on whether an item is new, ready for posting, or for routing to different social platforms.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running n8n instance.
  • RSS Feed URL(s): The URL(s) of the RSS feeds you wish to monitor.
  • Airtable Account: An Airtable account with a base and table configured to store your content. This table should include fields for:
    • Title
    • Link
    • Summary
    • Social Content (for various platforms like Twitter, LinkedIn)
    • Hashtags
    • Image Prompt
    • Image URL
    • Status (e.g., "New", "Ready to Post", "Posted")
    • Social Platform (e.g., "Twitter", "LinkedIn")
  • Groq API Key: For the Groq Chat Model to generate AI content.
  • GetLate Account & API Key: For scheduling social media posts.
  • Credentials: Configure credentials for Airtable, Groq, and HTTP Request (for GetLate) within n8n.

Setup/Usage

  1. Import the Workflow: Download the JSON and import it into your n8n instance.
  2. Configure RSS Feed Trigger:
    • Open the "RSS Feed Trigger" node.
    • Enter the URL(s) of the RSS feeds you want to monitor.
    • Set the desired polling interval.
  3. Configure Airtable Node:
    • Open the "Airtable" node.
    • Select your Airtable credential.
    • Specify your Base ID and Table Name.
    • Map the fields to store the RSS item data and AI-generated content.
  4. Configure Groq Chat Model:
    • Open the "Groq Chat Model" node.
    • Select your Groq credential.
    • Review and adjust the prompt for generating summaries and social content as needed.
  5. Configure HTTP Request (GetLate):
    • Open the "HTTP Request" node (for GetLate).
    • Set up an HTTP Request credential with your GetLate API key.
    • Ensure the URL and body of the request are correctly configured to interact with the GetLate API for scheduling posts, referencing the dynamic data from previous nodes.
  6. Review and Adjust Logic:
    • Examine the "If" and "Switch" nodes to understand the conditional routing. Adjust conditions if your Airtable status fields or social platform names differ.
    • Modify the "Edit Fields" and "Code" nodes if you need to transform data differently or add custom logic.
  7. Activate the Workflow: Once all configurations are complete, activate the workflow. It will now automatically fetch new RSS articles, process them with AI, store them in Airtable, and schedule social media posts.

Related Templates

Track competitor SEO keywords with Decodo + GPT-4.1-mini + Google Sheets

This workflow automates competitor keyword research using OpenAI LLM and Decodo for intelligent web scraping. Who this is for SEO specialists, content strategists, and growth marketers who want to automate keyword research and competitive intelligence. Marketing analysts managing multiple clients or websites who need consistent SEO tracking without manual data pulls. Agencies or automation engineers using Google Sheets as an SEO data dashboard for keyword monitoring and reporting. What problem this workflow solves Tracking competitor keywords manually is slow and inconsistent. Most SEO tools provide limited API access or lack contextual keyword analysis. This workflow solves that by: Automatically scraping any competitor’s webpage with Decodo. Using OpenAI GPT-4.1-mini to interpret keyword intent, density, and semantic focus. Storing structured keyword insights directly in Google Sheets for ongoing tracking and trend analysis. What this workflow does Trigger — Manually start the workflow or schedule it to run periodically. Input Setup — Define the website URL and target country (e.g., https://dev.to, france). Data Scraping (Decodo) — Fetch competitor web content and metadata. Keyword Analysis (OpenAI GPT-4.1-mini) Extract primary and secondary keywords. Identify focus topics and semantic entities. Generate a keyword density summary and SEO strength score. Recommend optimization and internal linking opportunities. Data Structuring — Clean and convert GPT output into JSON format. Data Storage (Google Sheets) — Append structured keyword data to a Google Sheet for long-term tracking. Setup Prerequisites If you are new to Decode, please signup on this link visit.decodo.com n8n account with workflow editor access Decodo API credentials OpenAI API key Google Sheets account connected via OAuth2 Make sure to install the Decodo Community node. Create a Google Sheet Add columns for: primarykeywords, seostrengthscore, keyworddensity_summary, etc. Share with your n8n Google account. Connect Credentials Add credentials for: Decodo API credentials - You need to register, login and obtain the Basic Authentication Token via Decodo Dashboard OpenAI API (for GPT-4o-mini) Google Sheets OAuth2 Configure Input Fields Edit the “Set Input Fields” node to set your target site and region. Run the Workflow Click Execute Workflow in n8n. View structured results in your connected Google Sheet. How to customize this workflow Track Multiple Competitors → Use a Google Sheet or CSV list of URLs; loop through them using the Split In Batches node. Add Language Detection → Add a Gemini or GPT node before keyword analysis to detect content language and adjust prompts. Enhance the SEO Report → Expand the GPT prompt to include backlink insights, metadata optimization, or readability checks. Integrate Visualization → Connect your Google Sheet to Looker Studio for SEO performance dashboards. Schedule Auto-Runs → Use the Cron Node to run weekly or monthly for competitor keyword refreshes. Summary This workflow automates competitor keyword research using: Decodo for intelligent web scraping OpenAI GPT-4.1-mini for keyword and SEO analysis Google Sheets for live tracking and reporting It’s a complete AI-powered SEO intelligence pipeline ideal for teams that want actionable insights on keyword gaps, optimization opportunities, and content focus trends, without relying on expensive SEO SaaS tools.

Ranjan DailataBy Ranjan Dailata
161

Generate song lyrics and music from text prompts using OpenAI and Fal.ai Minimax

Spark your creativity instantly in any chat—turn a simple prompt like "heartbreak ballad" into original, full-length lyrics and a professional AI-generated music track, all without leaving your conversation. 📋 What This Template Does This chat-triggered workflow harnesses AI to generate detailed, genre-matched song lyrics (at least 600 characters) from user messages, then queues them for music synthesis via Fal.ai's minimax-music model. It polls asynchronously until the track is ready, delivering lyrics and audio URL back in chat. Crafts original, structured lyrics with verses, choruses, and bridges using OpenAI Submits to Fal.ai for melody, instrumentation, and vocals aligned to the style Handles long-running generations with smart looping and status checks Returns complete song package (lyrics + audio link) for seamless sharing 🔧 Prerequisites n8n account (self-hosted or cloud with chat integration enabled) OpenAI account with API access for GPT models Fal.ai account for AI music generation 🔑 Required Credentials OpenAI API Setup Go to platform.openai.com → API keys (sidebar) Click "Create new secret key" → Name it (e.g., "n8n Songwriter") Copy the key and add to n8n as "OpenAI API" credential type Test by sending a simple chat completion request Fal.ai HTTP Header Auth Setup Sign up at fal.ai → Dashboard → API Keys Generate a new API key → Copy it In n8n, create "HTTP Header Auth" credential: Name="Fal.ai", Header Name="Authorization", Header Value="Key [Your API Key]" Test with a simple GET to their queue endpoint (e.g., /status) ⚙️ Configuration Steps Import the workflow JSON into your n8n instance Assign OpenAI API credentials to the "OpenAI Chat Model" node Assign Fal.ai HTTP Header Auth to the "Generate Music Track", "Check Generation Status", and "Fetch Final Result" nodes Activate the workflow—chat trigger will appear in your n8n chat interface Test by messaging: "Create an upbeat pop song about road trips" 🎯 Use Cases Content Creators: YouTubers generating custom jingles for videos on the fly, streamlining production from idea to audio export Educators: Music teachers using chat prompts to create era-specific folk tunes for classroom discussions, fostering interactive learning Gift Personalization: Friends crafting anniversary R&B tracks from shared memories via quick chats, delivering emotional audio surprises Artist Brainstorming: Songwriters prototyping hip-hop beats in real-time during sessions, accelerating collaboration and iteration ⚠️ Troubleshooting Invalid JSON from AI Agent: Ensure the system prompt stresses valid JSON; test the agent standalone with a sample query Music Generation Fails (401/403): Verify Fal.ai API key has minimax-music access; check usage quotas in dashboard Status Polling Loops Indefinitely: Bump wait time to 45-60s for complex tracks; inspect fal.ai queue logs for bottlenecks Lyrics Under 600 Characters: Tweak agent prompt to enforce fuller structures like [V1][C][V2][B][C]; verify output length in executions

Daniel NkenchoBy Daniel Nkencho
601

Automate invoice processing with OCR, GPT-4 & Salesforce opportunity creation

PDF Invoice Extractor (AI) End-to-end pipeline: Watch Drive ➜ Download PDF ➜ OCR text ➜ AI normalize to JSON ➜ Upsert Buyer (Account) ➜ Create Opportunity ➜ Map Products ➜ Create OLI via Composite API ➜ Archive to OneDrive. --- Node by node (what it does & key setup) 1) Google Drive Trigger Purpose: Fire when a new file appears in a specific Google Drive folder. Key settings: Event: fileCreated Folder ID: google drive folder id Polling: everyMinute Creds: googleDriveOAuth2Api Output: Metadata { id, name, ... } for the new file. --- 2) Download File From Google Purpose: Get the file binary for processing and archiving. Key settings: Operation: download File ID: ={{ $json.id }} Creds: googleDriveOAuth2Api Output: Binary (default key: data) and original metadata. --- 3) Extract from File Purpose: Extract text from PDF (OCR as needed) for AI parsing. Key settings: Operation: pdf OCR: enable for scanned PDFs (in options) Output: JSON with OCR text at {{ $json.text }}. --- 4) Message a model (AI JSON Extractor) Purpose: Convert OCR text into strict normalized JSON array (invoice schema). Key settings: Node: @n8n/n8n-nodes-langchain.openAi Model: gpt-4.1 (or gpt-4.1-mini) Message role: system (the strict prompt; references {{ $json.text }}) jsonOutput: true Creds: openAiApi Output (per item): $.message.content → the parsed JSON (ensure it’s an array). --- 5) Create or update an account (Salesforce) Purpose: Upsert Buyer as Account using an external ID. Key settings: Resource: account Operation: upsert External Id Field: taxid_c External Id Value: ={{ $json.message.content.buyer.tax_id }} Name: ={{ $json.message.content.buyer.name }} Creds: salesforceOAuth2Api Output: Account record (captures Id) for downstream Opportunity. --- 6) Create an opportunity (Salesforce) Purpose: Create Opportunity linked to the Buyer (Account). Key settings: Resource: opportunity Name: ={{ $('Message a model').item.json.message.content.invoice.code }} Close Date: ={{ $('Message a model').item.json.message.content.invoice.issue_date }} Stage: Closed Won Amount: ={{ $('Message a model').item.json.message.content.summary.grand_total }} AccountId: ={{ $json.id }} (from Upsert Account output) Creds: salesforceOAuth2Api Output: Opportunity Id for OLI creation. --- 7) Build SOQL (Code / JS) Purpose: Collect unique product codes from AI JSON and build a SOQL query for PricebookEntry by Pricebook2Id. Key settings: pricebook2Id (hardcoded in script): e.g., 01sxxxxxxxxxxxxxxx Source lines: $('Message a model').first().json.message.content.products Output: { soql, codes } --- 8) Query PricebookEntries (Salesforce) Purpose: Fetch PricebookEntry.Id for each Product2.ProductCode. Key settings: Resource: search Query: ={{ $json.soql }} Creds: salesforceOAuth2Api Output: Items with Id, Product2.ProductCode (used for mapping). --- 9) Code in JavaScript (Build OLI payloads) Purpose: Join lines with PBE results and Opportunity Id ➜ build OpportunityLineItem payloads. Inputs: OpportunityId: ={{ $('Create an opportunity').first().json.id }} Lines: ={{ $('Message a model').first().json.message.content.products }} PBE rows: from previous node items Output: { body: { allOrNone:false, records:[{ OpportunityLineItem... }] } } Notes: Converts discount_total ➜ per-unit if needed (currently commented for standard pricing). Throws on missing PBE mapping or empty lines. --- 10) Create Opportunity Line Items (HTTP Request) Purpose: Bulk create OLIs via Salesforce Composite API. Key settings: Method: POST URL: https://<your-instance>.my.salesforce.com/services/data/v65.0/composite/sobjects Auth: salesforceOAuth2Api (predefined credential) Body (JSON): ={{ $json.body }} Output: Composite API results (per-record statuses). --- 11) Update File to One Drive Purpose: Archive the original PDF in OneDrive. Key settings: Operation: upload File Name: ={{ $json.name }} Parent Folder ID: onedrive folder id Binary Data: true (from the Download node) Creds: microsoftOneDriveOAuth2Api Output: Uploaded file metadata. --- Data flow (wiring) Google Drive Trigger → Download File From Google Download File From Google → Extract from File → Update File to One Drive Extract from File → Message a model Message a model → Create or update an account Create or update an account → Create an opportunity Create an opportunity → Build SOQL Build SOQL → Query PricebookEntries Query PricebookEntries → Code in JavaScript Code in JavaScript → Create Opportunity Line Items --- Quick setup checklist 🔐 Credentials: Connect Google Drive, OneDrive, Salesforce, OpenAI. 📂 IDs: Drive Folder ID (watch) OneDrive Parent Folder ID (archive) Salesforce Pricebook2Id (in the JS SOQL builder) 🧠 AI Prompt: Use the strict system prompt; jsonOutput = true. 🧾 Field mappings: Buyer tax id/name → Account upsert fields Invoice code/date/amount → Opportunity fields Product name must equal your Product2.ProductCode in SF. ✅ Test: Drop a sample PDF → verify: AI returns array JSON only Account/Opportunity created OLI records created PDF archived to OneDrive --- Notes & best practices If PDFs are scans, enable OCR in Extract from File. If AI returns non-JSON, keep “Return only a JSON array” as the last line of the prompt and keep jsonOutput enabled. Consider adding validation on parsing.warnings to gate Salesforce writes. For discounts/taxes in OLI: Standard OLI fields don’t support per-line discount amounts directly; model them in UnitPrice or custom fields. Replace the Composite API URL with your org’s domain or use the Salesforce node’s Bulk Upsert for simplicity.

Le NguyenBy Le Nguyen
942