HumationHuman + Automation
Back to Catalog

Automate social media content planning with Llama 3.3 AI, trending topics & Google Suite

DigiMetaLabDigiMetaLab
224 views
2/3/2026
Lead ManagementFormstackWebhookSalesforceCRM
Official Page

How it works:

  1. Daily Trigger: Every morning at 8 AM, the workflow is automatically triggered.

  2. Fetch Trending Topics: The workflow collects trending topics from external sources, such as news RSS feeds and Reddit popular posts. These trends are merged and summarized to provide up-to-date context for content generation.

  3. Read Active Campaigns: The workflow reads all rows from the “Active Campaigns” Google Sheet, but only processes campaigns with a status of "active" to avoid generating content for paused or inactive campaigns.

  4. Enrich Campaigns with Trends: Each active campaign is enriched with the latest trending topics, so the generated content can reference current events or popular themes.

  5. AI Content Generation: For each enriched campaign, Groq AI generates:

  • An engaging post caption tailored to the platform and target audience
  • Creative direction with visual suggestions
  • Relevant hashtags (5-10)
  • Best posting time recommendation for the platform

  1. Quality Scoring: The workflow calculates a quality score for each generated content idea, considering factors like caption length, hashtag count, and creative direction.

  2. Append to Google Sheets: The generated content ideas, along with their quality scores and other details, are appended to the “Daily Content Plan” Google Sheet for record-keeping and team collaboration.

  3. Schedule in Google Calendar: For each campaign, an event is created in Google Calendar with the content details and recommended posting time, ensuring the team is reminded to review or publish the content.

  4. Daily Email Summary (Optional): At the end of the process, a summary email can be sent to the team, including statistics such as the number of campaigns processed, average quality score, and a platform breakdown.

Set up steps:

  1. Prepare Your Google Sheets:
  • Create a sheet named “Active Campaigns” with columns: Project Name, Theme, Target Audience, Platform, and Status (to mark campaigns as active/inactive).
  • Create another sheet named “Daily Content Plan” with columns for Project Name, Date, Platform, Caption, Creative Direction, Hashtags, and any other details you want to track.
  1. Connect Google Services to n8n:
  • In n8n, set up and authenticate your Google Sheets and Google Calendar credentials. You can find authentication information in the n8n documentation for Google credentials.

  1. Add a Cron Node: Drag in a Cron node and set it to trigger every day at 8:00 AM.

  2. Read Campaigns from Google Sheets:

  • Add a Google Sheets node.
  • Set the operation to “Read Rows” and select your “Active Campaigns” sheet.
  • (Optional) Use a Filter or IF node to process only rows where Status is “active”.

  1. (Optional) Fetch Trending Topics: If you want to enrich your content with trending topics, add nodes to fetch data from RSS feeds, Reddit, or other sources.

  2. Process Each Campaign:

  • Use a SplitInBatches node to process each campaign row individually.
  1. Generate Content Ideas with Groq AI:
  • Add a Groq AI node (or OpenAI node if Groq is not available).
  • Configure the prompt to generate a content idea using the campaign’s theme, target audience, and platform. You can reference fields from the Google Sheets node using expressions like $("Google Sheets").item.json['Theme'].
  1. Append Results to “Daily Content Plan”:
  • Add another Google Sheets node.
  • Set the operation to “Append” and select your “Daily Content Plan” sheet.
  • Map the generated content fields to the appropriate columns.
  1. Schedule Events in Google Calendar:
  • Add a Google Calendar node.
  • Set the operation to “Create Event”.
  • Use the project name and content idea for the event title and description, and set the event time as needed.
  1. (Optional) Send a Daily Summary Email:
  • Add an Email node to send a summary of the day’s content plan to your team.
  1. Test the Workflow:
  • Run the workflow manually to ensure all steps work as expected.
  • Check that new content ideas appear in the “Daily Content Plan” sheet and that events are created in Google Calendar.
  1. Activate the Workflow:
  • Once you’ve confirmed everything works, activate the workflow so it runs automatically every morning.

n8n Workflow: Automate Social Media Content Planning with Llama 3.3 AI, Trending Topics & Google Suite

This n8n workflow automates the process of generating social media content ideas based on trending topics, planning them in a Google Sheet, and scheduling them in Google Calendar. It leverages an AI agent (Llama 3.3 via Groq) to analyze RSS feeds for trending content and structure the output, streamlining your content creation pipeline.

What it does:

  1. Triggers on Schedule: The workflow runs automatically at predefined intervals.
  2. Reads RSS Feeds: It fetches the latest articles from specified RSS feeds to identify trending topics.
  3. Processes with AI Agent: An AI Agent (configured with Groq's Llama 3.3 model) analyzes the RSS feed content to extract key information and generate social media content ideas.
  4. Parses AI Output: The AI's structured output is parsed to ensure data consistency.
  5. Aggregates Data: Combines the processed data for further actions.
  6. Checks for Existing Content in Google Sheets: It queries a Google Sheet to see if the generated content ideas already exist, preventing duplicates.
  7. Filters New Content: Only new, unique content ideas proceed in the workflow.
  8. Adds New Content to Google Sheets: New content ideas are added as new rows to a designated Google Sheet, serving as a content calendar or planning board.
  9. Schedules Events in Google Calendar: For each new content idea, an event is created in Google Calendar, allowing for visual scheduling and planning.
  10. Sends Email Notifications (Optional): A Gmail node is present, suggesting the capability to send email notifications, potentially for approval or update alerts.
  11. Posts to Reddit (Optional): A Reddit node is included, indicating the possibility of directly posting content or updates to Reddit.

Prerequisites/Requirements:

  • n8n Instance: A running n8n instance.
  • Google Sheets Credential: An n8n credential configured for Google Sheets access (OAuth 2.0 recommended).
  • Google Calendar Credential: An n8n credential configured for Google Calendar access (OAuth 2.0 recommended).
  • Groq Credential: An n8n credential for Groq API access (for the Llama 3.3 AI model).
  • Gmail Credential (Optional): An n8n credential for Gmail access if email notifications are desired.
  • Reddit Credential (Optional): An n8n credential for Reddit access if posting to Reddit is desired.
  • RSS Feed URLs: URLs of RSS feeds containing relevant trending topics.
  • Google Sheet: A pre-existing Google Sheet to serve as your content planning board.
  • Google Calendar: A Google Calendar to schedule content.

Setup/Usage:

  1. Import the Workflow: Download the provided JSON and import it into your n8n instance.
  2. Configure Credentials:
    • Set up your Google Sheets, Google Calendar, and Groq credentials within n8n.
    • If using, configure Gmail and Reddit credentials.
  3. Configure RSS Read Node (ID: 37):
    • Enter the URLs of the RSS feeds you want to monitor for trending topics.
  4. Configure AI Agent Node (ID: 1119):
    • Ensure your Groq credential is selected.
    • Review and adjust the prompt for the AI agent to guide it in generating social media content ideas relevant to your needs (e.g., "Analyze the following trending articles and suggest 3 social media post ideas, including a headline, a brief description, and relevant hashtags, formatted as JSON.").
    • Verify the model used (e.g., Llama 3.3).
  5. Configure Google Sheets Node (ID: 18):
    • Specify the Spreadsheet ID and Sheet Name where your content plan will be stored.
    • Adjust the "Read" operation to fetch existing content for duplication checks.
    • Configure the "Write" operation to add new content ideas.
  6. Configure Google Calendar Node (ID: 317):
    • Specify the Calendar ID where events should be created.
    • Map the appropriate fields from the AI's output to the event title, description, and start/end times.
  7. Configure Schedule Trigger Node (ID: 839):
    • Define the desired frequency for the workflow to run (e.g., daily, weekly).
  8. Review and Activate: Carefully review all node configurations, especially the data mapping and AI prompts. Once satisfied, activate the workflow.

This workflow provides a robust foundation for automating your social media content planning, leveraging the power of AI to stay on top of trending topics.

Related Templates

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 Dutch Public Procurement Data Collection with TenderNed

TenderNed Public Procurement What This Workflow Does This workflow automates the collection of public procurement data from TenderNed (the official Dutch tender platform). It: Fetches the latest tender publications from the TenderNed API Retrieves detailed information in both XML and JSON formats for each tender Parses and extracts key information like organization names, titles, descriptions, and reference numbers Filters results based on your custom criteria Stores the data in a database for easy querying and analysis Setup Instructions This template comes with sticky notes providing step-by-step instructions in Dutch and various query options you can customize. Prerequisites TenderNed API Access - Register at TenderNed for API credentials Configuration Steps Set up TenderNed credentials: Add HTTP Basic Auth credentials with your TenderNed API username and password Apply these credentials to the three HTTP Request nodes: "Tenderned Publicaties" "Haal XML Details" "Haal JSON Details" Customize filters: Modify the "Filter op ..." node to match your specific requirements Examples: specific organizations, contract values, regions, etc. How It Works Step 1: Trigger The workflow can be triggered either manually for testing or automatically on a daily schedule. Step 2: Fetch Publications Makes an API call to TenderNed to retrieve a list of recent publications (up to 100 per request). Step 3: Process & Split Extracts the tender array from the response and splits it into individual items for processing. Step 4: Fetch Details For each tender, the workflow makes two parallel API calls: XML endpoint - Retrieves the complete tender documentation in XML format JSON endpoint - Fetches metadata including reference numbers and keywords Step 5: Parse & Merge Parses the XML data and merges it with the JSON metadata and batch information into a single data structure. Step 6: Extract Fields Maps the raw API data to clean, structured fields including: Publication ID and date Organization name Tender title and description Reference numbers (kenmerk, TED number) Step 7: Filter Applies your custom filter criteria to focus on relevant tenders only. Step 8: Store Inserts the processed data into your database for storage and future analysis. Customization Tips Modify API Parameters In the "Tenderned Publicaties" node, you can adjust: offset: Starting position for pagination size: Number of results per request (max 100) Add query parameters for date ranges, status filters, etc. Add More Fields Extend the "Splits Alle Velden" node to extract additional fields from the XML/JSON data, such as: Contract value estimates Deadline dates CPV codes (procurement classification) Contact information Integrate Notifications Add a Slack, Email, or Discord node after the filter to get notified about new matching tenders. Incremental Updates Modify the workflow to only fetch new tenders by: Storing the last execution timestamp Adding date filters to the API query Only processing publications newer than the last run Troubleshooting No data returned? Verify your TenderNed API credentials are correct Check that you have setup youre filter proper Need help setting this up or interested in a complete tender analysis solution? Get in touch 🔗 LinkedIn – Wessel Bulte

Wessel BulteBy Wessel Bulte
247

🎓 How to transform unstructured email data into structured format with AI agent

This workflow automates the process of extracting structured, usable information from unstructured email messages across multiple platforms. It connects directly to Gmail, Outlook, and IMAP accounts, retrieves incoming emails, and sends their content to an AI-powered parsing agent built on OpenAI GPT models. The AI agent analyzes each email, identifies relevant details, and returns a clean JSON structure containing key fields: From – sender’s email address To – recipient’s email address Subject – email subject line Summary – short AI-generated summary of the email body The extracted information is then automatically inserted into an n8n Data Table, creating a structured database of email metadata and summaries ready for indexing, reporting, or integration with other tools. --- Key Benefits ✅ Full Automation: Eliminates manual reading and data entry from incoming emails. ✅ Multi-Source Integration: Handles data from different email providers seamlessly. ✅ AI-Driven Accuracy: Uses advanced language models to interpret complex or unformatted content. ✅ Structured Storage: Creates a standardized, query-ready dataset from previously unstructured text. ✅ Time Efficiency: Processes emails in real time, improving productivity and response speed. *✅ Scalability: Easily extendable to handle additional sources or extract more data fields. --- How it works This workflow automates the transformation of unstructured email data into a structured, queryable format. It operates through a series of connected steps: Email Triggering: The workflow is initiated by one of three different email triggers (Gmail, Microsoft Outlook, or a generic IMAP account), which constantly monitor for new incoming emails. AI-Powered Parsing & Structuring: When a new email is detected, its raw, unstructured content is passed to a central "Parsing Agent." This agent uses a specified OpenAI language model to intelligently analyze the email text. Data Extraction & Standardization: Following a predefined system prompt, the AI agent extracts key information from the email, such as the sender, recipient, subject, and a generated summary. It then forces the output into a strict JSON structure using a "Structured Output Parser" node, ensuring data consistency. Data Storage: Finally, the clean, structured data (the from, to, subject, and summarize fields) is inserted as a new row into a specified n8n Data Table, creating a searchable and reportable database of email information. --- Set up steps To implement this workflow, follow these configuration steps: Prepare the Data Table: Create a new Data Table within n8n. Define the columns with the following names and string type: From, To, Subject, and Summary. Configure Email Credentials: Set up the credential connections for the email services you wish to use (Gmail OAuth2, Microsoft Outlook OAuth2, and/or IMAP). Ensure the accounts have the necessary permissions to read emails. Configure AI Model Credentials: Set up the OpenAI API credential with a valid API key. The workflow is configured to use the model, but this can be changed in the respective nodes if needed. Connect the Nodes: The workflow canvas is already correctly wired. Visually confirm that the email triggers are connected to the "Parsing Agent," which is connected to the "Insert row" (Data Table) node. Also, ensure the "OpenAI Chat Model" and "Structured Output Parser" are connected to the "Parsing Agent" as its AI model and output parser, respectively. Activate the Workflow: Save the workflow and toggle the "Active" switch to ON. The triggers will begin polling for new emails according to their schedule (e.g., every minute), and the automation will start processing incoming messages. --- Need help customizing? Contact me for consulting and support or add me on Linkedin.

DavideBy Davide
1616