Skip to main content

Monitor brand reputation crises with Twitter/X, Reddit, News API, Slack and Jira

Workflow preview

Workflow preview
100%
Monitor brand reputation crises with Twitter/X, Reddit, News API, Slack and Jira preview
Open on n8n.io

1. Workflow Overview

This workflow monitors brand mentions across multiple platforms (Twitter/X, Reddit, News) and automatically detects reputation crises based on sentiment analysis and trend detection. How it works 1...

Best for

  • Market Research automation workflows
  • AI Summarization automation workflows
  • advanced n8n builders looking for reusable templates

Tools used

n8n-nodes-base.scheduletrigger, n8n-nodes-base.twitter, n8n-nodes-base.reddit, n8n-nodes-base.httprequest, n8n-nodes-base.code, n8n-nodes-base.filter, n8n-nodes-base.merge, n8n-nodes-base.wait

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Oneclick AI Squad.

Original n8n.io source

1.1 Workflow description

Title
Monitor brand reputation crises with Twitter/X, Reddit, News API, Slack and Jira
Workflow name
Monitor brand reputation crises with Twitter/X, Reddit, News API, Slack and Jira

This workflow monitors brand mentions across multiple platforms (Twitter/X, Reddit, News) and automatically detects reputation crises based on sentiment analysis and trend detection.

How it works

  1. Multi-platform monitoring: Every 10 minutes, scans Twitter/X, Reddit, and news sites for brand mentions
  2. Data normalization: Converts all platform data into unified format
  3. Smart filtering: Removes duplicates and already-analyzed mentions
  4. AI sentiment analysis: Analyzes each mention for:
  • Sentiment score (positive/negative/neutral)
  • Amplification factors (engagement, verified accounts, news sources)
  • Crisis-level phrases and keywords
  1. Trend detection: Compares current sentiment to 24-hour baseline:
  • Detects sharp sentiment drops
  • Identifies negative mention spikes
  • Calculates impact surge
  1. Crisis classification: Assigns severity (CRITICAL/HIGH/MEDIUM/LOW)
  2. Automated response: For crises, triggers immediate alerts:
  • Executive crisis brief with action plan
  • Slack alerts to crisis team
  • Email to leadership and PR team
  • JIRA ticket creation
  • Crisis event logging

Setup steps

  1. Connect platforms:
  • Twitter/X: Add OAuth credentials to "Monitor Twitter/X" node
  • Reddit: Add OAuth credentials to "Monitor Reddit" node
  • News API: Get API key from newsapi.org and add to "Monitor News & Blogs" node
  1. Configure brand monitoring:
  • Update brand name and handles in search queries
  • Add additional platforms if needed (LinkedIn, Facebook, Instagram)
  1. Set up alerting:
  • Slack: Add credentials and update channel names
  • Email: Add SMTP settings and recipient lists
  • JIRA: Add credentials and project ID
  1. Adjust sensitivity:
  • Modify sentiment keyword dictionaries in "AI Sentiment Analysis Engine"
  • Adjust crisis threshold scores
  • Customize amplification factors
  1. Test thoroughly:
  • Run manual execution with test data
  • Verify alert routing and content
  • Test false positive handling
  1. Activate: Enable for continuous 24/7 monitoring

Key Features:

  • Multi-platform monitoring (every 10 minutes): Twitter/X, Reddit, and News sites
  • Data normalization that converts different platform formats into unified structure
  • AI sentiment analysis engine that evaluates:
  • Sentiment keywords (critical, severe, moderate, mild negative/positive)
  • Amplification factors (engagement, verified accounts, follower counts)
  • Impact scoring based on reach and influence
  • Baseline trend detection that tracks 24-hour sentiment history and detects:
  • Sharp sentiment drops (15+ points = crisis)
  • Negative mention spikes (30%+ increase)
  • Impact surges
  • Automated crisis response workflow:
  • Aggregates crisis mentions into executive brief
  • Generates detailed action plan based on severity
  • Sends Slack alerts to crisis team
  • Emails leadership with comprehensive brief
  • Creates JIRA ticket for tracking
  • Logs all events for analysis
  • Two-path routing: Crisis-level events trigger full response workflow, while routine mentions are logged for trend analysis

1.2 Logical Blocks

This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.

2. Block-by-Block Analysis

Block 1 - Every 10 Minutes

Type / Role
n8n-nodes-base.scheduleTrigger - scheduleTrigger
Config choices
Version 1.2

Block 2 - Monitor Twitter/X

Type / Role
n8n-nodes-base.twitter - twitter
Config choices
Version 2

Block 3 - Monitor Reddit

Type / Role
n8n-nodes-base.reddit - reddit
Config choices
Version 1

Block 4 - Monitor News & Blogs

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.2

Block 5 - Normalize Data Format

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Block 6 - Remove Duplicates

Type / Role
n8n-nodes-base.filter - filter
Config choices
Version 2

Block 7 - Merge Platform Data

Type / Role
n8n-nodes-base.merge - merge
Config choices
Version 3

Block 8 - Track Analyzed Mentions

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Block 9 - API Rate Limiter

Type / Role
n8n-nodes-base.wait - wait
Config choices
Version 1.1

Block 10 - Only New Mentions

Type / Role
n8n-nodes-base.filter - filter
Config choices
Version 2

Block 11 - AI Sentiment Analysis Engine

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Block 12 - Calculate Trend Baseline

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Block 13 - Filter Crisis Triggers

Type / Role
n8n-nodes-base.switch - switch
Config choices
Version 3.1

Block 14 - Aggregate Crisis Data

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Block 15 - Generate Crisis Brief

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Block 16 - Alert Crisis Team - Slack

Type / Role
n8n-nodes-base.slack - slack
Config choices
Version 2.1

Block 17 - Alert Crisis Team - Email

Type / Role
n8n-nodes-base.emailSend - emailSend
Config choices
Version 2.1

Block 18 - Create JIRA Crisis Ticket

Type / Role
n8n-nodes-base.jira - jira
Config choices
Version 1

Block 19 - Log Crisis Event

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Block 20 - Log Routine Monitoring

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Block 21 - Sticky Note

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 22 - Sticky Note4

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 23 - Sticky Note5

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 24 - Sticky Note6

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Showing the first 24 of 26 workflow blocks. Download the JSON for the full node graph.

3. Summary Table

Workflow Monitor brand reputation crises with Twitter/X, Reddit, News API, Slack and Jira
Complexity advanced
Nodes 26
Categories Market Research, AI Summarization
Author Oneclick AI Squad
Published 25 Feb 2026

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/13696/13696.json as the source template for this automation.

  2. 2. Import the template into n8n

    Open n8n, import the downloaded JSON, and review each node before activating the workflow.

  3. 3. Configure credentials and variables

    Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.

  4. 4. Test with sample data

    Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.

  5. 5. Activate and monitor

    Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.

Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.

Frequently asked questions

What does Monitor brand reputation crises with Twitter/X, Reddit, News API, Slack and Jira do?

This workflow monitors brand mentions across multiple platforms (Twitter/X, Reddit, News) and automatically detects reputation crises based on sentiment analysis and trend detection. How it works 1...

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Market Research, AI Summarization use case.