HumationHuman + Automation
Back to Catalog

Automatic weekly digital PR stories suggestions with Reddit and Anthropic

Custom Workflows AICustom Workflows AI
3431 views
2/3/2026
File ManagementGoogle DriveAutomationEmailNotion
Official Page

Introduction

The "Automatic Weekly Digital PR Stories Suggestions" workflow is a sophisticated automated system designed to identify trending news stories on Reddit, analyze public sentiment through comment analysis, extract key information from source articles, and generate strategic angles for potential digital PR campaigns.

This workflow leverages the power of social media trends, natural language processing, and AI-driven analysis to deliver curated, sentiment-analyzed news opportunities for PR professionals.

Operating on a weekly schedule, the workflow searches Reddit for posts related to specified topics, filters them based on engagement metrics, and performs a deep analysis of both the content and public reaction.

It then generates comprehensive reports that include story opportunities, audience insights, and strategic recommendations. These reports are automatically compiled, stored in Google Drive, and shared with team members via Mattermost for immediate collaboration.

This workflow solves the time-consuming process of manually monitoring social media for trending stories, analyzing public sentiment, and identifying PR opportunities.

By automating these tasks, PR professionals can focus on strategy development and execution rather than spending hours on research and analysis.

Who is this for?

This workflow is designed for digital PR professionals, content marketers, communications teams, and media relations specialists who need to stay on top of trending stories and public sentiment to develop timely and effective PR campaigns. It's particularly valuable for:

  • PR agencies managing multiple clients across different industries
  • In-house PR teams needing to identify media opportunities quickly
  • Content marketers looking for trending topics to create timely content
  • Communications professionals monitoring public perception of industry news

Users should have basic familiarity with n8n workflows and the PR strategy development process. While technical knowledge of the integrated APIs is not required to use the workflow, some understanding of Reddit, sentiment analysis, and PR campaign development would be beneficial for interpreting and acting on the generated reports.

What problem is this workflow solving?

Digital PR professionals face several challenges that this workflow addresses:

  1. Information Overload: Manually monitoring social media platforms for trending stories is time-consuming and often results in missed opportunities.

  2. Sentiment Analysis Complexity: Understanding public perception of news stories requires reading through hundreds of comments and identifying patterns, which is labor-intensive and subjective.

  3. Content Extraction: Visiting multiple news sources to read and analyze articles takes significant time.

  4. Strategic Angle Development: Identifying unique PR angles that leverage trending stories and public sentiment requires synthesizing large amounts of information.

  5. Team Collaboration: Sharing findings and insights with team members in a structured format can be cumbersome.

By automating these processes, the workflow enables PR professionals to quickly identify trending stories with PR potential, understand public sentiment, and develop strategic angles based on comprehensive analysis, all while maintaining a structured approach to team collaboration.

What this workflow does

Overview

The workflow automatically identifies trending posts on Reddit related to specified topics, analyzes both the content of linked articles and public sentiment from comments, and generates comprehensive PR strategy reports. These reports include story opportunities, audience insights, and strategic recommendations based on the analysis. The final reports are compiled, stored in Google Drive, and shared with team members via Mattermost.

Process

  1. Topic Selection and Reddit Search:

    • The workflow starts with a list of topics specified in the "Set Data" node
    • It searches Reddit for posts related to these topics
    • Posts are filtered based on upvotes and other criteria to focus on trending content

  2. Comment Analysis:

    • For each post, the workflow retrieves comments
    • It extracts the top 30 comments based on score
    • Using Claude AI, it analyzes the comments to understand:
      • Overall sentiment
      • Dominant narratives
      • Audience insights
      • PR implications

  3. Content Analysis:

    • The workflow extracts the content of the linked article using Jina AI
    • It analyzes the content to identify:
      • Core story elements
      • Technical aspects
      • Narrative opportunities
      • Viral elements

  4. PR Strategy Development:

    • Based on the combined analysis of comments and content, the workflow generates:
      • First-mover story opportunities
      • Trend-amplifier story ideas
      • Priority rankings
      • Execution roadmap
      • Strategic recommendations

  5. Report Generation and Distribution:

    • The workflow compiles comprehensive reports for each post
    • Reports are converted to text files
    • All files are compressed into a ZIP archive
    • The archive is uploaded to Google Drive
    • A link to the archive is shared with team members via Mattermost

Setup

To set up this workflow, follow these steps:

  1. Import the Workflow:

    • Download the workflow JSON file
    • Import it into your n8n instance

  2. Configure API Credentials:

    • Reddit: Add a new credential "Reddit OAuth2 API" by following the guide at https://docs.n8n.io/integrations/builtin/credentials/reddit/
    • Anthropic: Add a new credential "Anthropic Account" by following the guide at https://docs.n8n.io/integrations/builtin/credentials/anthropic/
    • Google Drive: Add a new credential "Google Drive OAuth2 API" by following the guide at https://docs.n8n.io/integrations/builtin/credentials/google/oauth-single-service/

  3. Configure the "Set Data" Node:

    • Set your interested topics (one per line)
    • Add your Jina API key (obtain from https://jina.ai/api-dashboard/key-manager)

  4. Configure the Mattermost Node:

    • Update your Mattermost instance URL
    • Set your Webhook ID and Channel
    • Follow the guide at https://developers.mattermost.com/integrate/webhooks/incoming/ for webhook setup

  5. Adjust the Schedule (Optional):

    • The workflow is set to run every Monday at 6am
    • Modify the "Schedule Trigger" node if you need a different schedule

  6. Test the Workflow:

    • Run the workflow manually to ensure all connections are working properly
    • Check the output to verify the reports are being generated correctly

How to customize this workflow to your needs

This workflow can be customized in several ways to better suit your specific requirements:

  1. Topic Selection:

    • Modify the topics in the "Set Data" node to focus on industries or subjects relevant to your PR strategy
    • Add multiple topics to cover different client interests or market segments

  2. Filtering Criteria:

    • Adjust the "Upvotes Requirement Filtering" node to change the minimum upvotes threshold
    • Modify the filtering conditions to include or exclude certain types of posts

  3. Analysis Parameters:

    • Customize the prompts in the "Comments Analysis," "News Analysis," and "Stories Report" nodes to focus on specific aspects of the content or comments
    • Adjust the temperature settings in the Anthropic Chat Model nodes to control the creativity of the AI responses

  4. Report Format:

    • Modify the "Set Final Report" node to change the structure or content of the final reports
    • Add or remove sections based on your specific reporting needs

  5. Distribution Method:

    • Replace or supplement the Mattermost notification with email notifications, Slack messages, or other communication channels
    • Add additional storage options beyond Google Drive

  6. Schedule Frequency:

    • Change the "Schedule Trigger" node to run the workflow more or less frequently
    • Set up multiple triggers for different topics or clients

  7. Integration with Other Systems:

    • Add nodes to integrate with your CRM, content management system, or project management tools
    • Create connections to automatically populate content calendars or task management systems

Automatic Weekly Digital PR Stories Suggestions with Reddit and Anthropic

This n8n workflow automates the process of generating weekly digital PR story suggestions by leveraging Reddit's trending content and Anthropic's AI capabilities. It helps PR professionals and marketers stay ahead by identifying popular topics and transforming them into actionable story ideas.

What it does

  1. Schedules Execution: The workflow runs automatically on a weekly basis (every Monday at 9:00 AM).
  2. Fetches Trending Reddit Posts: It queries the Reddit API to retrieve the top 20 "hot" posts from the /r/all subreddit.
  3. Filters for Relevant Posts: It processes the fetched Reddit posts, extracting key information like title, URL, and score.
  4. Generates PR Story Ideas with AI: For each Reddit post, it uses the Anthropic Chat Model via a Basic LLM Chain to generate a digital PR story idea. The prompt guides the AI to consider the post's content and suggest a relevant, engaging PR angle.
  5. Aggregates Suggestions: All generated PR story ideas are collected into a single dataset.
  6. Converts to CSV: The aggregated story ideas are converted into a CSV file format.
  7. Compresses the CSV: The CSV file is then compressed into a ZIP archive.
  8. Uploads to Google Drive: The compressed ZIP file containing the weekly PR story suggestions is uploaded to a specified folder in Google Drive.

Prerequisites/Requirements

  • n8n Instance: A running n8n instance.
  • Reddit API Credentials: An application registered with Reddit to obtain Client ID and Client Secret for API access.
  • Anthropic API Key: An API key for the Anthropic AI service (e.g., for Claude models).
  • Google Drive Account: A Google account with access to Google Drive for storing the generated files.
  • Google Drive Credentials (OAuth2): An OAuth2 credential setup in n8n for Google Drive access.

Setup/Usage

  1. Import the Workflow: Import the provided JSON workflow into your n8n instance.
  2. Configure Credentials:
    • Reddit: Set up a new Reddit credential using your Client ID and Client Secret.
    • Anthropic: Set up a new Anthropic credential with your API Key.
    • Google Drive: Set up a new Google Drive OAuth2 credential.
  3. Configure Nodes:
    • Reddit Node: Ensure the "Resource" is set to "Post" and "Operation" to "Get Many". You might want to adjust the "Subreddit" (currently /r/all) or "Limit" (currently 20) if needed.
    • Basic LLM Chain Node: Review and adjust the prompt for the Anthropic Chat Model if you want to refine the PR story generation.
    • Google Drive Node: Specify the "Folder ID" where you want the compressed CSV files to be uploaded.
  4. Activate the Workflow: Enable the workflow in n8n. It will automatically run every Monday at 9:00 AM.
  5. Monitor: Check your specified Google Drive folder weekly for new PR story suggestion files.

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