HumationHuman + Automation
Back to Catalog

Generate social media campaign images with Mistral AI & Pollinations.ai

ResilNextResilNext
409 views
2/3/2026
ScheduledJiraWebhookNotificationsAutomation
Official Page

📖 Description

🔹 How it works

This workflow uses AI (Mistral LLM + Pollinations.ai) to generate high-quality visual content for social media campaigns. It automates the process from brand/campaign input to final image upload, ensuring consistency and relevance.

  1. Input Brand & Campaign Data

    • Retrieves brand profile and campaign goals from Google Drive.
    • Cleans and merges the data into a structured JSON format.

  2. Campaign Goal Generation

    • AI summarizes campaign goals, audience, success metrics, and keywords.
    • Produces a clear campaign goal summary for content planning.

  3. Image Prompt Generation

    • AI creates 5 detailed image prompts reflecting the campaign story.
    • Includes 1 caption and 4–6 relevant hashtags.

  4. Image Creation

    • Pollinations.ai generates images based on the AI prompts.
    • Each image is renamed systematically (photo1 → photo5).

  5. Post-Processing & Upload

    • All images are merged into a single item.
    • Workflow uploads the final output to Google Drive for campaign use.

⚙️ Set up steps

  1. Connect Credentials

    • Add Google Drive and Mistral API credentials in n8n.

  2. Configure Google Drive Input Nodes

    • Set fileId for brand profile and campaign goals.

  3. Customize AI Prompts

    • Sticky notes explain AI nodes for goal summary and image prompt generation.
    • Optionally modify tone, keywords, or target audience for brand-specific campaigns.

  4. Check Image Output Nodes

    • Ensure Pollinations.ai HTTP request nodes are active.
    • Verify renaming code nodes for proper photo sequence.

  5. Activate Workflow

    • Test workflow manually to ensure images are generated and uploaded correctly.

🔹 Data Handling & Output

  • This workflow pulls brand profile and campaign goal data from Google Drive.
  • Data is processed into structured JSON, including:
    • Brand Profile: name, mission, vision, values, services, tone, keywords, contact info.
    • Campaign Goal: primary goal, focus, success metrics, target audience, core message.
  • Supports population of multiple campaigns or brands dynamically.
  • JSON output can be used downstream for image prompt generation, reporting, or analytics.
  • All processing is automated, with clear nodes for extraction, parsing, and merging.

pollinations.ai is an open-source free text and image generation API available. No signups or API keys required. which prioritize your privacy with zero data storage and completely anonymous usage.

⚡ Result: A fully automated AI-to-image workflow that transforms campaign goals into ready-to-use social media visuals, saving time and maintaining brand consistency.

Generate Social Media Campaign Images with Mistral AI & Pollinations.ai

This n8n workflow automates the creation of social media campaign images using AI. It leverages Mistral AI to generate image prompts and then uses Pollinations.ai to generate the images based on those prompts. The generated images are then uploaded to Google Drive.

What it does

This workflow simplifies the process of creating visual content for social media campaigns by:

  1. Triggering Manually: The workflow starts when manually executed.
  2. Setting Campaign Data: Defines initial campaign parameters like the campaign name, target audience, and key message.
  3. Generating Image Prompts with AI: Uses a Mistral Cloud Chat Model to generate a detailed image prompt based on the campaign data. This prompt is structured to be suitable for image generation APIs.
  4. Parsing AI Output: Extracts the generated image prompt from the AI model's response using a structured output parser.
  5. Generating Image with Pollinations.ai: Makes an HTTP request to the Pollinations.ai API, passing the AI-generated image prompt to create an image.
  6. Saving Image to Google Drive: Uploads the newly generated image to a specified folder in Google Drive.
  7. Merging Data (Placeholder): A merge node is present, though not actively connected in the provided JSON, suggesting potential for merging data from multiple branches or consolidating results.

Prerequisites/Requirements

  • n8n Instance: A running n8n instance.
  • Mistral AI Account & API Key: Required for the Mistral Cloud Chat Model.
  • Pollinations.ai: No explicit API key is typically required for public Pollinations.ai endpoints, but ensure access if specific endpoints are used.
  • Google Drive Account: For storing the generated images.
  • Google Drive n8n Credential: Configured in n8n to allow the workflow to access your Google Drive.

Setup/Usage

  1. Import the workflow: Import the provided JSON into your n8n instance.
  2. Configure Credentials:
    • Mistral Cloud Chat Model: Set up your Mistral AI API key in the "Mistral Cloud Chat Model" node's credentials.
    • Google Drive: Configure a Google Drive credential in n8n and select it in the "Google Drive" node. Ensure it has permissions to create files in the target folder.
  3. Customize Campaign Details:
    • Open the "Edit Fields (Set)" node.
    • Modify the campaignName, targetAudience, and keyMessage values to match your social media campaign requirements.
  4. Specify Google Drive Folder:
    • In the "Google Drive" node, specify the Folder ID where you want the generated images to be saved.
  5. Execute the workflow: Click "Execute workflow" in the "Manual Trigger" node to run the workflow and generate your social media campaign image.
  6. Review Output: Check your specified Google Drive folder for the newly generated image.

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