Monitor brand mentions on X with Gemini AI visual analysis & Telegram alerts
This workflow automates brand monitoring on X by analyzing both the text and the images in posts. It uses multi-modal AI to score brand relevance, filters out noise, logs important mentions in Airtable, and sends real-time alerts to a Telegram group for high-priority posts.
What it does
Traditional brand monitoring tools often miss the most authentic user content because they only track text. They can't "see" your logo in a photo or your product featured in a video without a direct keyword mention.
This workflow acts as an AI agent that overcomes this blind spot. It finds mentions of your brand on X and then uses Google Gemini's multi-modal capabilities to perform a comprehensive analysis of both the text and any attached images. This allows it to understand the full context of a mention, score its relevance to your brand, and take the appropriate action, creating a powerful "visual intelligence" system.
How it works
The workflow runs on a schedule to find, analyze, and triage brand mentions.
- Get New Tweets: The workflow begins by using an Apify actor to scrape X for recent posts based on a defined set of search terms (e.g.,
Tesla OR $TSLA). It then filters these results to find unique mentions not already processed. - Check for Duplicates: It cross-references each found tweet with an Airtable base to ensure it hasn't been analyzed before, preventing duplicate work.
- Analyze Post Content: For each new, unique post, the workflow performs two parallel analyses using Google Gemini:
- Analyze the Photos: The AI examines the images in the post to describe the scene, identify logos or products, and determine the visual mood.
- Analyze the Text: A separate AI call analyzes the text of the post to understand its context and sentiment.
- Final Relevance Check: A "Head Strategist" AI node receives the outputs from both the visual and text analyses. It synthesizes this information to assign a final brand relevance score from 1 to 10.
- Triage and Action: Based on this score, the workflow automatically triages the post:
- High Relevance (Score > 7): The post is logged in the Airtable base, and an instant, detailed alert is sent to a Telegram monitoring group.
- Medium Relevance (Score 4-7): The post is quietly logged in Airtable for later strategic review.
- Low Relevance (Score < 4): The post is ignored, effectively filtering out noise.
Setup Instructions
To get this workflow running, you will need to configure your Airtable base and provide credentials for Apify, Google, and Telegram.
Required Credentials
- Apify: You will need an Apify API Token to run the X scraper.
- Airtable: You will need Airtable API credentials to connect to your base.
- Google AI: You will need credentials for the Google AI APIs to use the Gemini models.
- Telegram: You will need a Bot Token and the Chat ID for the channel where you want to receive high-relevance alerts.
Of course. Based on the Config node parameters you provided, the setup process is much more centralized. Here is the corrected and rewritten "Step-by-Step Configuration" section.
Of course. Here is the rewritten "Step-by-Step Configuration" section with the link to the advanced search documentation.
Step-by-Step Configuration
-
Set up Your Airtable Base: Before configuring the workflow, create a new table in your Airtable base. For the workflow to function correctly, this table must contain fields to store the analysis results. Create fields with the following names:
postId,postURL,postText,postDateCreated,authorUsername,authorName,sentiment,relevanceScore,relevanceReasoning,mediaPhotosAnalysis, andstatus. Once the table is created, have your Base ID and Table ID ready to use in theConfignode. -
Edit the
ConfigNode: The majority of the setup is handled in the firstConfignode. Click on it and edit the following parameters in the "Expressions" tab:searchTerms: Replace the example with the keywords, hashtags, and accounts you want to monitor. The field supports advanced search operators for complex queries. For a full list of available parameters, see the Twitter Advanced Search documentation.airtableBaseId: Paste your Airtable Base ID here.airtableTableId: Paste your Airtable Table ID here.lang: Set the two-letter language code for the posts you want to find (e.g., "en" for English).min_faves: Set the minimum number of "favorites" a post should have to be considered.tweetsToScrape: Define the maximum number of posts the scraper should find in each run.actorId: This is the specific Apify actor for scraping X. You can leave this as is unless you intend to use a different one.
-
Configure the Telegram Node: In the final node, "Send High Relevance Posts to Monitoring Group", you need to manually set the destination for the alerts.
- Enter the Chat ID for your Telegram group or channel.
How to Adapt the Template
This workflow is a powerful framework that can be adapted for various monitoring needs.
- Change the Source: Replace the Apify node with a different trigger or data source. You could monitor Reddit, specific RSS feeds, or a news API for mentions.
- Customize the AI Logic: The core of this workflow is in the AI prompts. You can edit the prompts in the Google Gemini nodes to change the analysis criteria. For example, you could instruct the AI to check for specific competitor logos, analyze the sentiment of comments, or identify if the post is from an influential account.
- Modify the Scoring: Adjust the logic in the "Switch" node to change the thresholds for what constitutes a high, medium, or low-relevance post to better fit your brand's needs.
- Change the Actions: Replace the Telegram node with a different action. Instead of sending an alert, you could:
- Create a ticket in a customer support system like Zendesk or Jira.
- Send a summary email to your marketing team.
- Add the post to a content curation tool or a social media management platform.
n8n Workflow: Monitor Brand Mentions on X (Twitter) with Gemini AI Visual Analysis & Telegram Alerts
This n8n workflow provides a powerful solution for businesses and individuals to monitor brand mentions on X (formerly Twitter). It leverages Google Gemini AI for advanced visual analysis of attached media, ensuring that relevant brand mentions with images are identified and promptly alerted via Telegram.
What it does:
This workflow is designed to proactively identify and analyze brand mentions on X, especially those accompanied by images or videos, and deliver actionable alerts.
- Manual Trigger: The workflow can be manually initiated for testing or on-demand checks.
- Scheduled Trigger: The workflow is configured to run on a schedule, periodically checking for new brand mentions.
- Airtable Integration: It interacts with an Airtable base, likely to fetch configuration parameters (like the brand name to monitor) or store historical data.
- HTTP Request (X API): It makes an HTTP request to the X (Twitter) API to search for recent mentions of a specified brand.
- Loop Over Items: It iterates through each tweet found by the X API.
- Code (Filter for Media): A custom code block filters the tweets, specifically looking for those that contain attached media (images or videos).
- If (Media Check): A conditional check verifies if media is present in the tweet.
- Google Gemini (Visual Analysis): If media is detected, the Google Gemini AI is used to perform a visual analysis of the attached image/video. This step likely extracts descriptions or identifies objects within the media.
- AI Agent (Contextual Analysis): An AI Agent (likely powered by Langchain) further processes the visual analysis results along with the tweet text to determine the relevance and sentiment of the brand mention.
- Structured Output Parser: This node extracts structured data from the AI Agent's output, making it easier to parse and use in subsequent steps.
- Switch (Sentiment/Relevance Check): A Switch node evaluates the output from the AI, potentially categorizing the mention by sentiment (positive, negative, neutral) or relevance.
- Edit Fields (Prepare Telegram Message): Based on the analysis, a "Set" node formats the data into a concise message suitable for a Telegram alert.
- Telegram Notification: Finally, a Telegram message is sent, alerting the user to the brand mention, including details from the tweet and the AI's analysis.
- No Operation, do nothing: If no media is found or the mention is deemed irrelevant, the workflow gracefully exits without sending an alert.
Prerequisites/Requirements:
To use this workflow, you will need:
- n8n Instance: A running n8n instance (cloud or self-hosted).
- Airtable Account: An Airtable account with a base configured to store brand monitoring settings or results.
- X (Twitter) Developer Account & API Keys: Access to the X API to search for tweets. This requires a developer account and appropriate API credentials.
- Google Gemini API Key: Access to the Google Gemini API for visual analysis capabilities.
- Telegram Bot Token & Chat ID: A Telegram bot set up to send messages, and the chat ID where you want to receive alerts.
- Langchain Integration (within n8n): Ensure your n8n instance has the Langchain nodes installed and configured for the AI Agent.
Setup/Usage:
- Import the Workflow: Download the provided JSON and import it into your n8n instance.
- Configure Credentials:
- Set up your Airtable credentials.
- Configure your HTTP Request node with your X (Twitter) API credentials (Bearer Token or OAuth).
- Add your Google Gemini API key as a credential in n8n.
- Set up your Telegram credentials (Bot Token) and specify the
Chat IDin the Telegram node.
- Customize Airtable: Ensure your Airtable base has the necessary tables and fields to store configuration (e.g., a table named "Brands" with a field for "Brand Name" to monitor).
- Adjust X API Query: Modify the HTTP Request node to target the specific search queries or hashtags relevant to your brand.
- Refine AI Logic:
- Review the Code node (ID 834) to ensure the media filtering logic aligns with your needs.
- Adjust the prompts and configurations within the Google Gemini (ID 1309) and AI Agent (ID 1119) nodes to fine-tune the visual and contextual analysis for your brand.
- Customize the conditions in the Switch node (ID 112) to define what constitutes an "alert-worthy" mention.
- Activate the Schedule: Enable the Schedule Trigger (ID 839) to have the workflow run automatically at your desired interval.
- Test the Workflow: Use the Manual Trigger (ID 838) to run the workflow and verify that it fetches tweets, analyzes media, and sends Telegram alerts correctly.
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.
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
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.