Slack and Telegram integration

📊 Description This workflow analyzes meeting transcripts using AI to understand team sentiment, engagement, and morale. The results are saved in Google Sheets for easy tracking and review. It receives meeting data through a webhook, validates the input, sends the transcript to AI for analysis, cleans the output, and stores the insights in a structured format. This helps teams track morale over time and spot risks early. 🔁 What This Template Does Receives meeting transcript data through a webhook. Checks that all required fields are present. Sends the transcript to AI for analysis. Identifies sentiment, engagement, emotional tone, and morale risk. Cleans and structures the AI response. Adds a timestamp for when the analysis was done. Looks for an existing record in Google Sheets using the meeting ID. Updates the row if the meeting already exists. Creates a new row if the meeting is new. Sends a response back to the webhook caller. ⭐ Key Benefits Removes the need for manual sentiment review Gives consistent and structured meeting insights Helps detect morale and engagement risks early Avoids duplicate records using meeting ID Keeps all sentiment data in one place Works with any system that can send webhooks 🧩 Features Webhook-based meeting data input AI-powered sentiment and engagement analysis Clear extraction of morale and risk signals Clean and predictable output structure Google Sheets create or update logic Safe retry handling using meeting ID Webhook response after completion Production-ready workflow design 🔐 Requirements A webhook source that can send meeting data Azure OpenAI credentials or a compatible AI model Google Sheets OAuth credentials A Google Sheet with required columns An AI prompt for meeting sentiment analysis 🎯 Target Audience Engineering and product teams HR and people operations teams Project and delivery managers Leadership teams tracking team health n8n automation builders Organizations monitoring meeting effectiveness

🌸 Affirmation Sender + Weekly Gratitude Digest v2 A gentle, automated wellness ritual for high-impact women who scale with grace. 📌 What it does Every morning at 7 a.m.* (your timezone) → a *fresh affirmation lands in Email, Telegram, or both. Every Sunday at 6 p.m.* → a *beautiful recap of your last-7-day gratitude notes is delivered. Logs everything** to a simple Notion hub so you can revisit, review, or share. ✨ Out-of-the-box experience | Channel | Morning Affirmation | Sunday Digest | |---------|---------------------|---------------| | Email | Styled HTML + tasteful Unsplash hero image | Scroll-ready digest with blush-gold imagery | | Telegram | Minimal text + emoji sparkle | Same digest, perfectly mobile-formatted | 🛠️ 30-second setup Fork the template in n8n. Fill four fields in Set: User Config (email, Telegram chat ID, Notion DB ID, channel). Connect credentials (Email SMTP, Telegram Bot, Notion, optional Slack/Discord). Activate — your future self will thank you. 🧩 Notion schema you’ll create (copy-paste once) | Property | Type | Example | |----------|------|---------| | Name | Title | “I choose grace and ease today.” | | Type | Select | Affirmation or Gratitude | | Date | Date | 2025-08-19 | | Channel | Multi-select | email, telegram | | Message | Rich text | Full text or note | 🆕 v2 upgrades Timezone-aware** – respects the workflow’s TZ setting. Filtered queries** – digest only fetches Type = Gratitude from the last 7 days (faster, lighter). Rich media* – every email includes an Unsplash banner (keywords you choose, no API key*). Observability* – global error handler pings Slack or Discord within 5 seconds* if anything breaks. ✅ No hidden data, no secrets Zero hard-coded keys. Test with a sandbox Notion DB first. Ready for solo founders, coaches, or community managers who want to gift their members a daily dose of calm. 🚀 One-click install Clone → configure → activate. Your gentlest growth system is now on autopilot.

Notion Status-Based Alert Template Who is this for? Teams that live in Notion and want an instant ping to the right person when a task changes state. Perfect for content creators, project managers, or any small team that tracks work in a Notion database and prefers Slack / Telegram / Discord / e-mail notifications over manually checking a board. What problem does this solve? Polling Notion or checking a kanban board is slow and error-prone. This workflow watches a Notion database and routes an alert to specific people based on the item’s Status. One central map decides who gets pinged for “On Deck”, “In Progress”, “Ready for Review”, or “Ready to Publish”. How it works Trigger – choose either method Polling (Notion Trigger) – fires every minute. Push (Webhook) – register the production URL in a Notion automation and disable polling. Set Notion Page Info – copies Title, Status, URL, etc. into top-level fields. Switch (Status router) – routes the item down a branch that matches its Status. Set-Mention nodes – one per Status. Each node sets a single field mention (e.g. <@U123456>). Add or edit these nodes to map new statuses or recipients. Build Message – assembles a rich text block: Task title Status: <@UserIDs> <Notion URL|Open in Notion> Send nodes – Slack (active) + optional Telegram / WhatsApp / Discord / Email (disabled by default). All reuse the same {{$json.message}}. Setup steps Import this template into n8n. Connect credentials Notion API token Slack OAuth (and any other channels you enable) Edit the Status → Mention map Open each Set-Mention node and replace the placeholder with the real Slack ID / chat ID / phone / email. Copy a node for every extra Status you use, wire it to a new Switch output, and update the value. Set environment variables (recommended) NOTION_DB_ID, SLACK_CHANNEL, EMAIL_FROM, etc. Pick your trigger style Keep polling enabled or disable it and enable the Webhook, then register the webhook URL in Notion. Test – change a task’s Status in Notion → watch Slack for the ping. Example output > Title: “Draft blog post – AI productivity” > Status: Ready for Review > Slack message: > > Draft blog post – AI productivity > Status: Ready for Review > <@U789012> > <https://www.notion.so/…|Open in Notion> > Extending the flow Wire additional channels after Build Message—they all consume the same {{$json.message}}. Add richer logic (e.g. due-date reminders) in the Set Notion Page Info node. Verify Notion webhook signatures in a Function node if you rely on push triggers. This template is the leanest possible setup: one table of statuses → direct pings to the right people. Swap the IDs, flip on your favourite channels, and ship.

What this workflow does This workflow allows you to monitor multiple Github repos simultaneously without polling due to use of Webhooks. It programmatically allows for adding and deleting of repos to your watchlist to make management convenient. Description Can monitor multiple repos simultaneously. Programmatically register or unregister repos from a list. No need for manual work. Webhook notification means no constant polling necessary. Setup Creating Credentials on Github Generate a personal access token on github by following these esteps; Right hand side of page -> Settings -> scroll to bottom -> Developer Settings > Personal Access Token > Tokens (classic) > Generate New Token Give scopes: admin:repo_hook repo (if you want to use it for your own private repo) if you need more help, see here: https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens Setting Credentials in n8n In Register Github Webhook Authenticaion > Generic Credential Type Generic Auth Type > Header Auth Header Auth > Create New Credential with Name set to 'Authorization' and Value set to 'Bearer '. (You can reuse this for Delete Github Webhook and Get Existing Webhooks). Now in Register Github Webhook, scroll down to Send Body > JSON and inside the JSON, change the value of "url" to the webhook address given as Production URL in the node Webhook Trigger. Notification settings In the third row, link up the Webhook Trigger to any API of your choice. Slack and Telegram are given as examples. You can also format the notification message as you wish. Setup time: roughly 10 minutes. Instructions Video: https://vimeo.com/1013473758 Test Register Webhooks In Repos to Monitor, add any repo you want to monitor changes for. Disable Webhook Trigger, Click Test Workflow and if your Github credentials were set correctly, it will automatically register the webhooks. - You can test this by running the single node Get Existing Webhook and confirming it outputs the repo addresses. Handle Github Events Now that you have registered the webhooks, re-enable Webhook Trigger and activate the workflow. Make a commit to any of the registered repos. Confirm that the notification went through. That's it!

📘 Description This workflow is an AI-assisted clean plate and object removal pipeline built for modern VFX production environments. It transforms a single plate image and removal brief into multiple high-quality clean plate variations, complete with automated quality evaluation, compositing-ready assets, and production-ready Nuke scripts—bridging the gap between manual paint workflows and fully automated AI-driven cleanup pipelines. ⚙️ Step-by-Step Flow 1 . The workflow begins with a webhook trigger that acts as the clean plate request intake layer, receiving a POST request containing the plate image URL, removal brief, shot code, and optional parameters such as object type, frame range, and QC thresholds. This input flows into a validation and data structuring stage, where required fields are verified, default values are assigned, and the payload is normalized to ensure consistency across downstream processes. The system then performs prompt engineering and expands the single removal brief into four specialized passes: a primary production-ready clean plate, an alternative variation, a foreground removal pass for background isolation, and a difference map for quality control visualization. Each pass is enriched with object-specific removal instructions, reconstruction constraints, and technical shot metadata to guide accurate AI generation. 2 . At the core of the pipeline, an image-to-video rendering process leverages the provided plate image as a reference and submits each variation as an independent job to the Seedance AI API, generating video-based clean plate outputs. A polling mechanism continuously tracks each job at fixed intervals, ensuring that processing only advances once rendering is successfully completed. Once outputs are available, a metadata and automated QC layer evaluates each pass by assigning a quality score based on resolution and consistency logic, comparing it against a predefined threshold to classify results as either auto-approved or flagged for review. A decision routing layer then determines the next step—allowing approved outputs to continue through the pipeline while immediately notifying the team via Slack in case of failures. 3 . Following this, the system generates a fully production-ready Nuke compositing script, automatically configuring nodes for the original plate, AI-generated clean plate, difference map visualization, merge operations, grading adjustments, and final output writes, all aligned with standardized folder structures and naming conventions. The asset pipeline then downloads the generated videos, uploads them to Google Drive using structured shot-based organization, and logs all associated metadata—including plate references, output variations, and project details—into a Notion database for centralized tracking. An aggregation layer consolidates all outputs into a unified structured response, combining QC results, video links, compositing scripts, and storage paths. Finally, a multi-channel notification system dispatches a detailed message to Slack and Telegram, presenting all clean plate variations with QC status, video previews, inline Nuke scripts, and direct access to delivery folders for seamless team review and integration into production workflows. 🚨 Error Handling • Global error trigger • Sends failure alerts to Slack instantly • Prevents silent pipeline failures and data loss 🧩 Prerequisites • Seedance API (AI video generation) • Google Drive OAuth2 • Notion API • Slack + Telegram credentials • Webhook integration 💡 Key Benefits ✔ Fully automated clean plate generation with zero manual prep ✔ Multiple AI-generated passes for flexible compositing workflows ✔ Built-in QC validation with intelligent decision routing ✔ Auto-generated Nuke scripts ready for production use ✔ Structured asset storage and centralized tracking ✔ Real-time notifications for faster team collaboration 👥 Perfect For VFX paint and prep teams Compositors working in Nuke pipelines Film and post-production studios AI-assisted cleanup and restoration workflows Studios managing high-volume plate processing

📘 Description This workflow is a real-time AI-powered cricket commentary bot that continuously monitors live match data and converts it into short, expert-style insights. It fetches live cricket scores every few seconds, extracts key match details, generates commentary using AI, and delivers updates instantly to Telegram. It also includes fail-safe mechanisms via email and Slack alerts to ensure reliability. ⚙️ Step-by-Step Flow Every 10 Seconds Trigger (Schedule) Runs continuously at a 10-second interval to keep match updates near real-time. Fetch Live Cricket Score (SerpAPI Node) Queries Google for live India cricket match data using SerpAPI. Extract Latest Match Data (Function Node) Pulls structured match details: Team names Scores Match result/status Tournament Skip If No Match Result (IF Node) Prevents unnecessary processing when no valid match data is available. Generate AI Match Commentary (OpenAI GPT-4o-mini) Transforms raw match data into structured insights: Match summary Key turning point Best performance Tactical insight Maintains expert tone and concise commentary style. Send Commentary to Telegram (Telegram Node) Delivers formatted commentary instantly to a Telegram chat using Markdown. Email Alert on AI Failure (Gmail Node) If AI generation fails: Sends an email alert Ensures manual follow-up Error Trigger → Slack Alert Catches any workflow-level failures and sends alerts to a Slack channel for monitoring. 🧩 Prerequisites • SerpAPI credential (for live scores) • OpenAI API (GPT-4o-mini) • Telegram Bot + chat ID • Gmail OAuth2 (for failure alerts) • Slack API (optional for error monitoring) 💡 Key Benefits ✔ Near real-time cricket updates (10s interval) ✔ AI-generated expert commentary (not raw scores) ✔ Automated delivery to Telegram ✔ Failure-safe alerts via email + Slack ✔ Fully hands-off live match tracking 👥 Perfect For Cricket Telegram channels and communities Sports commentary automation systems Live score notification bots Fan engagement platforms for real-time updates

This n8n template monitors your self-hosted apps for new releases across GitHub and container registries, uses Claude AI to analyze changelogs, and delivers color-coded update digests to Discord, Telegram, Slack, and ntfy. Stop finding out about updates after something breaks. Claude reads every changelog and tells you exactly what changed, what might break, and how urgent the update is — with a ready-to-run Docker update command for each release. Good to know Estimated cost is $0.01–0.03 per daily run using Claude Haiku. See Anthropic pricing for current rates. PostgreSQL logging is included but optional — the core workflow runs without a database using n8n's built-in static data for version tracking. Test mode is ON by default. Your first run pushes a sample release through the full pipeline (AI analysis, formatting, delivery) so you can verify everything works before going live. How it works Schedule trigger runs daily at 8 AM and builds a watchlist from your manually configured repos plus optional docker-compose auto-detection Checks GitHub Releases API for repos and Docker Hub/GHCR tag APIs for container images. Pre-releases and RC/beta tags are automatically filtered out Compares each release against the last known version stored in workflow static data to detect what's genuinely new Claude Haiku reads each changelog and returns a structured summary with breaking change detection, CVE/security scanning, migration steps, and urgency classification (critical/recommended/optional) Alert rules route critical and security updates to instant alerts, while everything else batches into a single daily digest sorted by urgency Formatted messages are delivered to your enabled channels with color-coded embeds, Docker update commands, and links to full release notes Release history is optionally logged to PostgreSQL for tracking update timelines How to use Add your Anthropic API key as an n8n credential, open the Configure Watcher node to set your channel URLs, and edit the Build Repo Watchlist node to add your repos — that's the minimum to get running Click "Test workflow" to push a sample release through the full pipeline and verify delivery Set test_mode to false and toggle Active — the workflow checks daily and only alerts when new releases are found Requirements Anthropic API key (setup guide) At least one delivery channel: Discord webhook (setup guide), Telegram bot, Slack app, or ntfy topic Optional: GitHub Personal Access Token for higher API rate limits (setup guide) Optional: PostgreSQL for release history logging Customizing this workflow Add or remove repos and container registries in the Build Repo Watchlist code node — pre-loaded with 10 popular self-hosted apps Enable docker-compose auto-detection to automatically build your watchlist from a compose file URL or pasted content Set per-repo alert rules including urgency overrides, instant alert flags, and channel routing Adjust the schedule, swap delivery channels, or add additional registries

Facebook Story Replies → Telegram “Human Required” Routing + Supabase CRM This workflow automatically captures Facebook Story replies, normalizes incoming webhook payloads, stores them in Supabase, assigns them to the correct regional support team based on UTC time, and sends real-time notifications to Slack and Telegram. This workflow listens to Facebook Story reply webhooks, converts raw payloads into a clean data structure, saves each reply in Supabase with a pending status, and automatically assigns it to the Asia or Europe support team based on the current UTC time. Once assigned, notifications are sent to Slack and Telegram, ensuring no customer reply is missed. You receive: Real-time Facebook Story reply ingestion** Automatic support team assignment (Asia / Europe)** Centralized Supabase storage** Instant Slack & Telegram notifications** Alerts for replies outside support hours** Ideal for support teams handling high volumes of social media interactions with strict response-time requirements. Quick Start – Implementation Steps Add your Facebook Webhook credentials and verify the callback URL. Connect Supabase credentials and confirm the replies table exists. Configure UTC-based time window logic for your support regions. Connect Slack credentials and select the notification channel. Add Telegram Bot Token and target chat ID. Activate the workflow — live reply handling starts instantly. What It Does This workflow automates end-to-end handling of Facebook Story replies: Receives Story reply events from Facebook via webhook. Normalizes incoming payloads into a structured format. Stores replies in Supabase with a pending status. Checks current UTC time to identify the active support window. Assigns replies to Asia or Europe support teams. Updates reply status to assigned when routing succeeds. Sends notifications to Slack and Telegram. Raises alerts for replies outside support hours. Logs all actions for auditing and follow-up. This ensures consistent handling, assignment, and visibility of customer interactions. Who’s It For This workflow is ideal for: Social media support teams Customer success teams Digital marketing teams E-commerce support operations SaaS companies handling Facebook DMs Businesses requiring timezone-based support routing Requirements to Use This Workflow To run this workflow, you need: n8n instance** (cloud or self-hosted) Facebook App** with Webhook access Supabase project** + API credentials Slack workspace** with API permissions Telegram Bot Token** and chat ID Basic understanding of JSON payloads and UTC time logic How It Works Webhook Listener – Receives Facebook Story reply events. Normalize Payload – Converts raw webhook data into a clean format. Save to Supabase – Stores reply with pending status. Time Window Check – Evaluates current UTC time. Assign Support Team – Routes to Asia or Europe team. Update Status – Marks reply as assigned. Send Notifications – Alerts Slack and Telegram. Alert Handling – Flags replies outside support hours. Setup Steps Import the workflow JSON into your n8n instance. Configure the Facebook Webhook node and verify it with your Facebook App. Connect Supabase credentials and ensure the replies table includes: id platform story_id sender_id sender_name message status assigned_to timestamps Adjust support time windows (UTC) in the IF/Switch node. Connect Slack API credentials and choose the notification channel. Add Telegram Bot Token and chat ID. Test using sample Facebook Story reply payloads. Activate the workflow — production ready. How To Customize Nodes Customize Support Hours Modify the time-check logic node to: Change Asia / Europe support windows Add additional regions Handle weekends or holidays Customize Supabase Storage You can extend the table with: Response SLA Agent name Resolution status Follow-up notes Raw webhook payload Customize Notifications Slack & Telegram messages can include: Mentions (@channel, @support) Emojis for priority Direct links to CRM or dashboard Highlighted urgent keywords Customize Assignment Logic You may: Route based on message content Assign by priority or keywords Add AI-based sentiment classification Use round-robin agent assignment Add-Ons (Optional Enhancements) You can extend this workflow to: Add sentiment analysis (OpenAI) Auto-reply with predefined responses Create SLA breach alerts Integrate with CRM tools Generate daily or weekly reports Add dashboard visualization in Supabase Escalate urgent replies automatically Use Case Examples Social Media Support Routing Automatically assign story replies to the correct regional team. SLA Enforcement Ensure replies are handled within working hours. Multi-Channel Alerts Notify teams instantly via Slack and Telegram. Centralized Reply Tracking Store all interactions in Supabase for audits. Scalable Support Automation Handle growing message volumes without manual routing. Troubleshooting Guide | Issue | Possible Cause | Solution | |----------------------|--------------------------|-----------------------------------------------| | No webhook data | Webhook not verified | Re-check Facebook webhook verification | | Replies not assigned | Time logic mismatch | Validate UTC time windows | | No Slack alert | Invalid credentials | Reconnect Slack API | | Supabase insert fails| Column mismatch | Match table schema exactly | | Telegram alert missing | Wrong chat ID | Verify bot permissions | | Workflow inactive | Workflow not activated | Enable workflow | Need Help? If you need help extending this workflow like adding AI analysis, advanced routing logic, CRM integration or scaling it for high-volume social channels, our n8n team at WeblineIndia can assist with enterprise-grade automation solutions.

Daily Cyber News Digest to Telegram Workflow Created By: Abdullah Dilshad 📧 [email protected] Stay informed with automated daily summaries. This workflow aggregates cyber news from multiple trusted sources, uses AI to intelligently select and summarize the top 5 most relevant articles, and delivers a clean, concise digest directly to your Telegram chat every morning at 10:00 AM. What This Workflow Does Collects Data: Fetches cybersecurity news from multiple global APIs. Filters Noise: Uses AI to discard irrelevant updates. Summarizes: Generates short, professional summaries (1–2 sentences). Delivers: Automatically sends a formatted digest to Telegram within message length limits. How It Works Schedule Trigger Runs automatically every day at 10:00 AM (customizable). News Collection Fetches articles using the keyword "cyber" from: GNews NewsAPI Data Processing Merges articles from both sources into a single, unified dataset. AI-Powered Selection OpenAI analyzes all fetched articles. Intelligently selects the Top 5 most relevant cybersecurity stories. Smart Summarization Each article is condensed into 1–2 clear sentences. Includes: Publication date, Source name, and Article link. Telegram Delivery Sends a clean, formatted digest to your specified Telegram chat. Ensures the total message length stays under Telegram’s 4096-character limit. Setup Instructions Get API Keys Sign up for free API keys from GNews.io and NewsAPI.org. Connect Accounts Add your Telegram and OpenAI credentials in n8n. Configure Telegram Enter your Telegram Chat ID in the "Send a Text Message" node. Customize the Schedule Change the trigger time if you prefer delivery at a different hour. Customization & Use Cases This workflow is fully reusable and scalable. You can replace the keyword "cyber" to track any topic relevant to your needs. Example Topics: 🤖 Artificial Intelligence (AI) 💰 Cryptocurrency & Blockchain 🚀 Startups & Venture Capital 📱 Consumer Technology 🏭 Industry-specific updates Note: This workflow is designed to be adapted for individual tracking, team updates, or competitor analysis.

The original LLM Council concept was introduced by Andrej Karpathy and published as an open-source repository demonstrating multi-model consensus and ranking. This workflow is my adaptation of that original idea, reimplemented and structured as a production-ready n8n template. Original repository - https://github.com/karpathy/llm-council This n8n template implements the LLM Council pattern: a single user question is processed in parallel by multiple large language models, independently evaluated by peer models, and then synthesized into one high-quality, consensus-driven final answer. It is designed for use cases where answer quality, balance, and reduced single-model bias are critical. 📌 Section 1: Trigger & Input ⚡ When Chat Message Received (Chat Trigger) Purpose: Receives a user’s message and initiates the entire workflow. How it works: A user sends a chat message The message is stored as the Original Question The same input is forwarded simultaneously to multiple LLM pipelines Why it matters: Provides a clean, unified entry point for all downstream multi-model logic. 📌 Section 2: Stage 1 — Parallel LLM Responses 🤖 Basic LLM Chains (x4) Models used: Anthropic Claude OpenAI GPT xAI Grok Google Gemini Purpose: Each model independently generates its own response to the same question. Key characteristics: Identical prompt structure for all models Independent reasoning paths No shared context between models Why it matters: Produces diverse perspectives, reasoning styles, and solution approaches. 📌 Section 3: Stage 2 — Response Anonymization 🧾 Set Nodes (Response A / B / C / D) Purpose: Stores model outputs in an anonymized format: Response A Response B Response C Response D Why it matters: Prevents evaluator models from knowing which LLM authored which response, reducing bias during evaluation. 📌 Section 4: Stage 3 — Peer Evaluation & Ranking 📊 Evaluation Chains (Claude / GPT / Grok / Gemini) Purpose: Each model acts as a reviewer and: Analyzes all four anonymized responses Describes strengths and weaknesses of each Produces a strict FINAL RANKING from best to worst Ranking format (strict): FINAL RANKING: Response B Response A Response D Response C Why it matters: Creates multiple independent quality assessments from different model perspectives. 📌 Section 5: Stage 4 — Ranking Aggregation 🧮 Code Node (JavaScript) Purpose: Aggregates all peer rankings by: Parsing ranking positions Calculating average position per response Counting evaluation occurrences Sorting responses by best average score Output includes: Aggregated rankings Best response label Best average score Why it matters: Transforms subjective rankings into a structured, quantitative consensus. 📌 Section 6: Stage 5 — Final Consensus Answer 🧠 Chairman LLM Chain Purpose: One model acts as the Council Chairman and: Reviews all original responses Considers peer rankings and aggregated scores Identifies consensus patterns and disagreements Produces a single, clear, high-quality final answer Why it matters: Delivers a refined response that reflects collective model intelligence rather than a simple average. 📊 Workflow Overview Stage Node / Logic Purpose 1 Chat Trigger Receive user question 2 LLM Chains Generate independent responses 3 Set Nodes Anonymize outputs 4 Evaluation Chains Peer review & ranking 5 Code Node Aggregate rankings 6 Chairman LLM Final synthesized answer 🎯 Key Benefits 🧠 Multi-model intelligence — avoids reliance on a single LLM ⚖️ Reduced bias — anonymized peer evaluation 📊 Quality-driven selection — ranking-based consensus 🔁 Modular architecture — easy to add or replace models 🌍 Language-flexible — input and output languages configurable 🧩 Production-ready logic — clear stages, deterministic ranking 🚀 Ideal Use Cases High-stakes decision support Complex technical or architectural questions Strategy and research synthesis AI assistants requiring higher trust and reliability Comparing and selecting the best LLM-generated answers

Extract employee emails from company domains using Human-in-the-Loop scraping using BrowserAct This workflow automates the process of enriching company data by scraping employee emails and positions from company websites. It processes a list of URLs from a Google Sheet, handles anti-bot measures (CAPTCHAs) by alerting you via Telegram to solve them manually before resuming, and saves the verified data back to your sheet. Target Audience Sales development representatives (SDRs), lead generation agencies, and recruiters needing verified contact info. How it works Read List: The workflow reads a list of company URLs from a Google Sheet. Scrape Data: It loops through each URL and triggers BrowserAct to scrape the site for team pages or contact info. Check Status: Finished**: If scraping is successful, it parses the data (Name, Email, Position). Paused: If a CAPTCHA is detected, the workflow sends a **Telegram alert. It pauses execution until you verify the CAPTCHA in the browser, then resumes automatically. Failed**: If scraping fails, it logs an error. Save Data: Extracted emails and names are appended to a new tab in the Google Sheet specific to that company. Notify: Once a company is processed, a Slack notification is sent. How to set up Configure Credentials: Connect your Google Sheets, BrowserAct, Telegram, and Slack accounts in n8n. Prepare BrowserAct: Ensure the Company Domain to Email Enrichment template is saved in your BrowserAct account. Setup Google Sheet: Create a Google Sheet with a column named Company url and populate it with target domains. Configure Notifications: Open the Send a message node (Slack) and select your target channel. Open the Alert User and Remind user nodes (Telegram) and ensure your Chat ID is correct. Activate: Run the workflow manually to start processing the list. Requirements BrowserAct* account with the Company Domain to Email Enrichment* template. Google Sheets** account. Telegram** account (Bot Token). Slack** account. How to customize the workflow Change Data Source: Replace the Google Sheet input with an Airtable or HubSpot node to pull domains from your CRM. Enrich Data: Add a Clearbit or Hunter.io node after scraping to cross-reference found emails. Modify Alerts: Change the Telegram alerts to Email or SMS (via Twilio) if preferred. Need Help? How to Find Your BrowserAct API Key & Workflow ID How to Connect n8n to BrowserAct How to Use & Customize BrowserAct Templates Workflow Guidance and Showcase Video Scale Your Lead Gen! 🚀 Automate Email Extraction with n8n & Browseract

Curate daily tech news for Slack and Telegram using BrowserAct & OpenRouter This workflow automates the creation and delivery of a professional morning tech briefing. It scrapes headlines from major sources like The Verge and Product Hunt, uses parallel AI agents to format the content specifically for Telegram (HTML) and Slack (Markdown), and broadcasts the updates to your team or community channels. Target Audience Product managers, development teams, community managers, and tech enthusiasts who want a consolidated daily news digest without manual curation. How it works Daily Trigger: A Schedule Trigger starts the workflow every morning at 10:00 AM. Fetch News: A BrowserAct node executes a background task to scrape the latest headlines and links from defined sources (default: The Verge and Product Hunt). Parallel Formatting: The data splits into two paths: Telegram Path: The "Telegram Master" AI Agent formats the news into clean HTML, adding emojis and ensuring links work within Telegram's API constraints. Slack Path: The "Slack Master" AI Agent formats the same news into Slack-compatible Markdown, prioritizing developer tools and using Slack-specific syntax. Smart Splitting: Both AI agents automatically split the content into multiple message parts if the text exceeds the character limits of the respective platforms. Broadcast: The workflow iterates through the generated message parts and sends them sequentially to Telegram and Slack. How to set up Configure Credentials: Connect your BrowserAct, OpenRouter (for AI models), Telegram, and Slack accounts in n8n. Prepare BrowserAct: Ensure the Automated Multi-Site Morning Brief template is saved in your BrowserAct account. Configure Channels: Open the Send a text message (Telegram) node and enter your Chat ID. Open the Send a message (Slack) node and select your target channel. Activate: Turn on the workflow to start receiving daily briefs. Requirements BrowserAct* account with the Automated Multi-Site Morning Brief* template. OpenRouter** account (or credentials for a specific LLM like Claude or Gemini). Telegram** Bot Token. Slack** account. How to customize the workflow Add News Sources: Update the BrowserAct node inputs to scrape different websites (e.g., Hacker News, TechCrunch). Change AI Persona: Modify the system prompts in the Telegram Master or Slack Master nodes to change the tone from "Professional" to "Casual" or "Sarcastic." Add More Platforms: Duplicate one of the formatting branches to create a version for Discord or Microsoft Teams. Need Help? How to Find Your BrowserAct API Key & Workflow ID How to Connect n8n to BrowserAct How to Use & Customize BrowserAct Templates Workflow Guidance and Showcase Video Keep Your Team Updated Automatically 🌅 n8n Morning Brief Workflow

(Retail) Customer Cleanup API → Supabase and send Notification This workflow provides an API-first solution to validate, clean, deduplicate and store customer data in Supabase. It ensures consistent customer records, prevents duplicates and keeps both internal teams and customers informed through automated notifications. This workflow acts as a backend customer intake API. It validates and normalizes incoming customer data, checks for existing users in Supabase, stores new customers safely and returns clear API responses. Internal teams receive Slack and Telegram updates, while customers get an email confirmation on successful creation. You receive: Centralized customer data validation** Automatic duplicate prevention** Supabase-backed customer storage** Real-time API responses** Team notifications + user confirmation email** Ideal for retail, e-commerce and SaaS teams that want clean customer data without manual intervention. Quick Start – Implementation Steps Import the provided n8n workflow JSON. Configure Supabase credentials with read/write access. Connect Slack, Telegram and Gmail/SMTP credentials. Copy the Webhook URL and use it as your customer intake API. Activate the workflow — your customer API is live. What It Does This workflow automates customer data intake and processing: Receives customer data via a POST API call. Cleans and normalizes names, email and phone numbers. Validates required fields and formats using JavaScript. Aggregates clear, field-specific validation errors. Checks Supabase to prevent duplicate users. Stores valid, new customers in Supabase. Returns structured API responses (success, validation error or duplicate). Sends notifications to Slack and Telegram. Emails the customer after successful account creation. This ensures reliable, consistent customer records across systems. Who’s It For This workflow is ideal for: Retail and e-commerce platforms CRM and customer data teams SaaS product teams Backend automation teams Marketing teams needing clean contact lists Developers building API-driven systems Requirements to Use This Workflow To run this workflow, you need: n8n instance** (cloud or self-hosted) Supabase project** with a customers table Supabase service role key Slack workspace** with API access Telegram bot** + chat ID Gmail or SMTP account** for user notifications How It Works API Request – Client sends customer data to the webhook endpoint. Validation & Cleanup – JavaScript validates and formats data. Validation Fail – Returns 400 response with clear error messages. Duplicate Check – Supabase is queried using the email address. Duplicate Found – Returns 409 response without creating a record. Create Customer – New customer is saved in Supabase. Success Response – API confirms successful creation. Notifications – Slack, Telegram and customer email are triggered. Setup Steps Create a Supabase table with fields for customer data, validation status and errors. Add Supabase credentials to n8n. Import the workflow JSON into n8n. Configure the Webhook node and copy the API URL. Review the validation logic if custom rules are required. Configure Slack, Telegram and email credentials. Test using Postman for invalid, duplicate and valid requests. Activate the workflow. How To Customize Nodes Customize Validation Rules Update the JavaScript validation node to add country-specific phone rules or additional fields. Customize Duplicate Logic Extend duplicate checks to include phone numbers or other identifiers. Customize Notifications Modify Slack and Telegram messages, add emojis, mentions or execution metadata. Add-Ons (Optional Enhancements) You can extend this workflow to: Add API key authentication Enable rate limiting Log failed attempts separately Support multi-country phone validation Add CRM or email marketing sync Implement soft deletes or upserts Use Case Examples Customer Registration API Centralize customer creation for web and mobile apps. Data Hygiene Automation Prevent invalid or duplicate contacts in your database. Retail & CRM Integration Keep customer records consistent across systems. Marketing Readiness Ensure only clean, valid contacts enter campaigns. Troubleshooting Guide | Issue | Possible Cause | Solution | | ----------------------- | ----------------------------- | ----------------------------------- | | Validation always fails | Incorrect payload structure | Ensure data is sent in request body | | Duplicate user created | Duplicate check misconfigured | Verify Supabase filter conditions | | No Slack alert | Invalid credentials | Reconnect Slack API | | No email sent | Gmail/SMTP not configured | Verify sender account | | API not responding | Webhook not active | Activate the workflow | Need Help? If you need help customizing or extending this workflow, adding authentication, scaling for high traffic, integrating CRMs or enhancing validation, the n8n automation team at WeblineIndia can assist you with production-ready automation and integration support. Contact us today.

Cloudflare Incident Monitoring & Escalation Workflow 🚀 Try Decodo — Web Scraping & Data API (Coupon: TRUNG) Decodo is a powerful public data access platform offering managed web scraping APIs and proxy infrastructure to collect structured web data at scale. It handles proxies, anti-bot protection, JavaScript rendering, retries, and global IP rotation—so you can focus on data, not scraping complexity. Why Decodo Managed Web Scraping API with anti-bot bypass & high success rates Works with JS-heavy sites; outputs JSON/HTML/CSV Easy integration (Python, Node.js, cURL) for eCommerce, SERP, social & general web data 🎟️ Special Discount Use coupon TRUNG to get the Advanced Scraping API plan — 23,000 requests for $5. Who this workflow is for For DevOps, SRE, IT Ops, and Platform teams running production traffic behind Cloudflare who need reliable incident awareness without alert fatigue. Use it if you want: Continuous Cloudflare incident monitoring Clear severity-based routing Automatic escalation into JIRA Clean Slack & Telegram notifications Deduplicated, noise-controlled alerts What this workflow does This workflow polls the Cloudflare Status API, detects unresolved incidents, scores their impact, and routes them to the right channels. High-impact incidents are escalated to JIRA. Lower-impact updates are notified (or skipped) to reduce noise. How it works (high level) Runs on a fixed schedule (e.g. every 5 minutes) Fetches current Cloudflare incidents Stops early if no active issues exist Normalizes and scores incidents (severity, impact, affected service) Deduplicates previously-alerted incidents Builds human-readable notification payloads Routes by impact: High → create JIRA incident + notify Low → notify or suppress Sends alerts to Slack and Telegram Requirements Decoco Scrapper API credential n8n (self-hosted or Cloud) Cloudflare Status API (public) Slack bot (chat:write) Telegram bot + chat ID JIRA project with issue-create permission Optional LLM credentials (summarization/classification) Notes All secrets are stored in n8n Credentials Workflow is idempotent and safe to rerun No assumptions about root cause or remediation Built for production-grade incident visibility with n8n.

Facebook Page Comment Moderation Scoreboard → Team Report This workflow automatically monitors Facebook Page comments, analyzes them using AI for intent, toxicity & spam, stores moderation results in a database and sends a clear summary report to Slack and Telegram. This workflow runs every few hours to fetch Facebook Page comments and analyze them using OpenAI. Each comment is classified as positive, neutral or negative, checked for toxicity, spam & abusive language and then stored in Supabase. A simple moderation summary is sent to Slack and Telegram. You receive: Automated Facebook comment moderation AI-based intent, toxicity, and spam detection Database logging of all moderated comments Clean Slack & Telegram summary reports Ideal for teams that want visibility into comment quality without manually reviewing every message. Quick Start – Implementation Steps Import the workflow JSON into n8n. Add your Facebook Page access token to the HTTP Request node. Connect your OpenAI API key for comment analysis. Configure your Supabase table for storing moderation data. Connect Slack and Telegram credentials and choose target channels. Activate the workflow — moderation runs automatically. What It Does This workflow automates Facebook comment moderation by: Running on a scheduled interval (every 6 hours). Fetching recent comments from a Facebook Page. Preparing each comment for AI processing. Sending comments to OpenAI for moderation analysis. Extracting structured moderation data: Comment intent Toxicity score Spam detection Abusive language detection Flagging risky comments based on defined rules. Storing moderation results in Supabase. Generating a summary report. Sending the report to Slack and Telegram. This ensures consistent, repeatable moderation with no manual effort. Who’s It For This workflow is ideal for: Social media teams Community managers Marketing teams Customer support teams Moderation and trust & safety teams Businesses managing high-volume Facebook Pages Anyone wanting AI-assisted comment moderation Requirements to Use This Workflow To run this workflow, you need: n8n instance** (cloud or self-hosted) Facebook Page access token** OpenAI API key** Supabase project and table** Slack workspace** with API access Telegram bot** and chat ID Basic understanding of APIs and JSON (helpful but not required) How It Works Scheduled Trigger – Workflow starts automatically every 6 hours. Fetch Comments – Facebook Page comments are retrieved. Prepare Data – Comments are formatted for processing. AI Moderation – OpenAI analyzes each comment. Normalize Results – AI output is cleaned and standardized. Store Data – Moderation results are saved in Supabase. Aggregate Stats – Summary statistics are calculated. Send Alerts – Reports are sent to Slack and Telegram. Setup Steps Import the workflow JSON into n8n. Open the Fetch Facebook Page Comments node and add: Page ID Access token Connect your OpenAI account in the AI moderation node. Create a Supabase table and map fields correctly. Connect Slack and select a reporting channel. Connect Telegram and set the chat ID. Activate the workflow. How To Customize Nodes Customize Flagging Rules Update the normalization logic to: Change toxicity thresholds Flag only spam or abusive comments Add custom moderation rules Customize Storage You can extend Supabase fields to include: Language AI confidence score Reviewer notes Resolution status Customize Notifications Slack and Telegram messages can include: Emojis Mentions (@channel) Links to Facebook comments Severity labels Add-Ons (Optional Enhancements) You can extend this workflow to: Auto-hide or delete toxic comments Reply automatically to positive comments Detect language and region Generate daily or weekly moderation reports Build dashboards using Supabase or BI tools Add escalation alerts for high-risk comments Track trends over time Use Case Examples Community Moderation Automatically identify harmful or spam comments. Brand Reputation Monitoring Spot negative sentiment early and respond faster. Support Oversight Detect complaints or frustration in comments. Marketing Insights Measure positive vs negative engagement. Compliance & Auditing Keep historical moderation logs in a database. Troubleshooting Guide | Issue | Possible Cause | Solution | |-----|---------------|----------| | No comments fetched | Invalid Facebook token | Refresh token & permissions | | AI output invalid | Prompt formatting issue | Use strict JSON prompt | | Data not saved | Supabase mapping mismatch | Verify table fields | | Slack message missing | Channel or credential error | Recheck Slack config | | Telegram alert fails | Wrong chat ID | Confirm bot permissions | | Workflow not running | Trigger disabled | Enable Cron node | Need Help? If you need help customizing, scaling or extending this workflow — such as advanced moderation logic, dashboards, auto-actions or production hardening, then our n8n workflow development team at WeblineIndia can assist with expert automation solutions.

Get notified when the International Space Station passes over your location - but only when you can actually see it! This workflow combines real-time ISS tracking with weather condition checks to send you alerts at the perfect moment for observation. Who is this for Space enthusiasts and astronomy hobbyists who want to spot the ISS Parents looking to share exciting science moments with their kids Remote workers who want a unique break reminder Educators creating engaging science experiences What this workflow does Tracks ISS position every 10 minutes using the Open Notify API Calculates distance and direction from your location using the Haversine formula Checks weather conditions via OpenWeatherMap to determine if ISS will be visible Provides observation guidance including compass direction, elevation angle, and viewing tips Includes crew information showing who is currently aboard the ISS Sends multi-channel alerts to Discord, Telegram, and Gmail simultaneously How to set up Configure your location in the Calculate Distance and Direction node Add OpenWeatherMap credentials (free tier available) Set up at least one notification channel (Discord, Telegram, or Gmail) Activate the workflow Requirements OpenWeatherMap API key (free) At least one notification channel configured

Who is this for? This template is perfect for: AI art enthusiasts** who want to stay updated on trending AI-generated artwork Content curators** looking to automate art discovery Japanese-speaking users** who want translated captions Social media managers** tracking AI art trends across platforms What this workflow does This workflow automatically collects viral AI art posts from Instagram and delivers them to your Telegram with Japanese translations. It runs daily and filters only high-engagement posts to ensure quality content. Key Features: 📸 Collects from 4 AI art hashtags (#AIart, #midjourney, #stablediffusion, #aiartwork) 🔥 Filters viral posts only (100+ likes threshold) 🇯🇵 Auto-translates captions to Japanese via DeepL ⚠️ Sends error alerts to Telegram if something goes wrong ⏱️ Built-in rate limiting to avoid API blocks How it works Schedule Trigger - Runs daily at 18:00 Instagram Scraping - Apify collects posts from multiple AI art hashtags Viral Filter - Only posts with 100+ likes and valid captions pass through Translation - DeepL translates captions from English to Japanese Image Download - Fetches the post image Telegram Delivery - Sends photo with translated caption, likes count, and source link Rate Limiting - 3-second delay between posts to avoid API limits Setup Requirements Apify account** - Sign up at apify.com for Instagram scraping DeepL API key** - Get free API access at deepl.com/pro-api Telegram Bot** - Create via @BotFather and get your Chat ID How to set up Import this workflow into n8n Set up credentials: Connect your Apify account Add your DeepL API key Configure Telegram Bot token Replace YOUR_TELEGRAM_CHAT_ID with your actual Chat ID in both Telegram nodes (Optional) Adjust the viral threshold in the Filter node (Optional) Modify hashtags in the Apify node Activate the workflow How to customize Change hashtags:** Edit the directUrls array in the Apify node Adjust viral threshold:** Change the 100 value in the Filter node Change schedule:** Modify the trigger time in the Schedule Trigger node Change language:** Update the translateTo parameter in the DeepL node Modify caption format:** Edit the caption template in the Telegram node

This workflow continuously monitors the TikTok Ads Library for new creatives from specific advertisers or keyword searches, scrapes them via Apify, logs them into Google Sheets, and sends concise notifications to Telegram or Slack with the number of newly discovered ads. It is built as a safe, idempotent loop that can run on a schedule without creating duplicates in your sheet. Use Case Manually checking the TikTok Ads Library for competitor creatives is time-consuming, and it's easy to lose track of which ads you've already seen. This workflow is ideal if you want to: Track competitor creatives over time** in a structured Google Sheet. Avoid duplicates** by matching ads via their unique adId field. Get lightweight notifications* in Telegram or Slack that tell you *how many new ads appeared, without spamming you with full ad lists. Run the process on autopilot** (daily, weekly, etc.) with a single schedule. Monitor by advertiser ID or keywords** with flexible search parameters. How it Works The workflow is organized into four logical blocks: Configuration & Date Conversion Configuration:** The Set Parameters Set node stores all key request variables: Ad target country (e.g., all or specific ISO country codes), Ad published date From (automatically set to yesterday by default), Ad published To (automatically set to today by default), Advertiser name or keyword (for keyword-based searches), adv_biz_ids (advertiser business IDs for specific advertiser tracking), Ad limit (optional limit on the number of results to scrape). Date Conversion:** Convert Dates to Unix transforms the human-readable date format (DD/MM/YYYY) into Unix timestamps in milliseconds, which are required by the TikTok Ads Library API. Request Building & Data Fetching Body Construction:** Build Apify Body creates the JSON request body for the Apify actor: Builds the TikTok Ads Library URL with all search parameters (region, date range, advertiser name/keyword, advertiser IDs). Conditionally adds resultsLimit to the request body only if the Ad limit field is not empty, allowing you to scrape all results or limit them as needed. Data Fetching:** Get TT Ads through Apify executes the Apify actor (Tiktok Ads Scraper) and retrieves all matching ads from the TikTok Ads Library. Data Preparation & De-duplication Data Extraction:** Prepare Data for Sheets safely extracts nested data from the API response: Extracts the first video URL from the videos array (if available). Extracts the cover image URL from the first video object. Extracts the TikTok username from the tiktokUser object (if available). Handles cases where arrays are empty or objects are missing without throwing errors. Load Existing IDs:** Read existing IDs pulls the existing adId column from your Google Sheet (configured to read a specific column/range, e.g., column K). Collect ID list converts these into a unique, normalized string array existingIds, which represents all ads you have already logged. Attach State:** Attach existing ids (Merge node) combines, for each execution, the freshly fetched TikTok response with the historical existingIds array from Sheets. Filter New Creatives:** Filter new creatives Code node compares each ad's adId (string) against the existingIds set and builds a new array containing only ads that are not yet present in the sheet. It also protects against duplicates inside the same batch by tracking seen IDs in a local Set. Data Logging & Notification Write New Ads:** Append or update row in sheet performs an appendOrUpdate into Google Sheets, mapping core fields such as adId, adName, advertiserName, advertiserId, paidBy, impressions, regionStats, targeting, tiktokUser, startUrl, videos, and coverImageURL (using the =IMAGE() formula to display images directly in the sheet). The column mapping uses adId as the matching column so that existing rows can be updated if needed. Count:** In parallel with the write step, Filter new creatives also feeds into Count new ads. This Code node returns a single summary item with newCount = items.length, i.e., the total number of new creatives processed in this run. Guard:** Any new ads? checks whether newCount is greater than 0. If not, the workflow ends silently and no message is sent, avoiding noise. Notify:** When there are new creatives, both Send a text message (Telegram) and Send a message (Slack) send notifications to the configured channels. The message includes {{$json.newCount}} and a fixed link to the Google Sheet, giving you a quick heads-up without listing individual ads. Setup Instructions To use this template, configure the following components. Credentials Apify:** Configure the Apify account credentials used by Get TT Ads through Apify. You'll need an Apify account with access to the Tiktok Ads Scraper actor. Google Sheets:** Connect your Google account in: Read existing IDs, Append or update row in sheet. Telegram (optional):** Connect your Telegram account credentials in Send a text message. Slack (optional):** Configure your Slack credentials in Send a message. The Set Parameters Node Open the Set Parameters Set node and customize: Ad target country: Which countries to monitor (all for all countries, or specific ISO 3166 country codes like US, GB, etc.). Ad published date From: Start date for the search range (defaults to yesterday using {{ $now.minus({ days: 1 }).toFormat('dd/MM/yyyy') }}). Ad published To: End date for the search range (defaults to today using {{ $now.toFormat('dd/MM/yyyy') }}). Advertiser name or keyword: Search by advertiser name or keywords (URL-encoded format, e.g., %22Applicave%20LLC%22). adv_biz_ids: Specific advertiser business IDs to track (comma-separated if multiple). Ad limit: Optional limit on the number of results (leave empty to scrape all available results). Google Sheets Configuration Read existing IDs** Set documentId and sheetName to your tracking spreadsheet and sheet (e.g., Sheet1). Configure the range to read only the column holding the ad adId values (e.g., column K: K:K). Append or update row in sheet** Point documentId and sheetName to the same spreadsheet/sheet. Make sure your sheet has the columns expected by the node (e.g., adId, coverImageURL, adName, Impressions, regionStats, targeting, tiktokUser, advertiserID, paidBy, advertiserName, startURL, videos). Confirm that adId is included in matchingColumns so de-duplication works correctly. Notification Configuration Telegram:** In Send a text message, set: chatId: Your target Telegram chat or channel ID. text: Customize the message template as needed, but keep {{$json.newCount}} to show the number of new creatives. Slack:** In Send a message, set: channelId: Your target Slack channel ID. text: Customize the message template as needed, but keep {{$json.newCount}} to show the number of new creatives. Schedule Open Schedule Trigger and configure when you want the workflow to run (e.g., every morning). Save and activate the workflow. Further Ideas & Customization This workflow is a solid foundation for systematic TikTok competitor monitoring. You can extend it to: Track multiple advertisers** by turning adv_biz_ids into a list and iterating over it with a loop or separate executions. Enrich the log with performance data** by creating a second workflow that reads the sheet, pulls engagement metrics (likes, shares, comments) for each logged adId from TikTok's API (if available), and merges the metrics back. Add more notification channels** such as email, or send a weekly summary that aggregates new ads by advertiser, format, or country. Tag or categorize creatives** (e.g., "video vs image", "country", "language", "advertiser type") directly in the sheet to make later analysis easier. Combine with Meta Ads monitoring** by running both workflows in parallel and creating a unified competitor intelligence dashboard. Add image analysis** by integrating Google Vision API to automatically detect objects, text, and themes in the cover images, similar to the Meta Ads creative analysis workflow.

This workflow continuously monitors the Meta Ads Library for new creatives from a specific competitor pages, logs them into Google Sheets, and sends a concise Telegram notification with the number of newly discovered ads. It is built as a safe, idempotent loop that can run on a schedule without creating duplicates in your sheet. Use Case Manually checking the Meta Ads Library for competitor creatives is time‑consuming, and it’s easy to lose track of which ads you’ve already seen. This workflow is ideal if you want to: Track competitor creatives over time** in a structured Google Sheet. Avoid duplicates** by matching ads via their unique id field. Get lightweight notifications* in Telegram that tell you *how many new ads appeared, without spamming you with full ad lists. Run the process on autopilot** (daily, weekly, etc.) with a single schedule. How it Works The workflow is organized into three logical blocks: Fetch Ads & Handle Pagination Configuration:** The Add parameters Set node stores all key request variables: ad_active_status (e.g. active), search_page_ids (competitor page IDs), ad_reached_countries, access_token. Routing:** Page or keywords routes execution into one of two HTTP Request nodes: Facebook Ads API by page — the main branch that queries ads by page ID. Facebook Ads API by keywords — an optional branch for keyword‑based searches. Normalization:** Facebook Ads API by ... returns the raw ads_archive response. Check the pagination then: extracts data (array of ad objects) into a dedicated field, reads paging.next into next_url for pagination. Pagination Loop:** If checks whether next_url is not empty. Set Next URL assigns next_url to a generic url field. Facebook Ads API pagination requests the next page and feeds it back into Check the pagination. This loop continues until there is no next_url, ensuring all pages of the Ads Library response are processed. De‑duplicate Ads & Log to Google Sheets Load Existing IDs:** Read existing IDs pulls the existing id column from your Google Sheet (configured to read a specific column/range). Collect ID list converts these into a unique, normalized string array existingIds, which represents all ads you have already logged. Attach State:** Attach existing ids (Merge node) combines, for each execution, the freshly fetched Meta response (data) with the historical existingIds array from Sheets. Filter New Creatives:** Filter new creatives Code node compares each ad’s id (string) against the existingIds set and builds a new data array containing only ads that are not yet present in the sheet. It also protects against duplicates inside the same batch by tracking seen IDs in a local Set. Write New Ads:** Split Out expands the filtered data array into individual items (one item per new ad). Add to sheet then performs an appendOrUpdate into Google Sheets, mapping core fields such as id, ad_creation_time, page_name, ad_creative_bodies, ad_snapshot_url, languages, publisher_platforms, and link fields. The column mapping uses id as the matching column so that existing rows can be updated if needed. Count New Ads & Notify in Telegram Count:** In parallel with the write step, Split Out also feeds into Count new ads. This Code node returns a single summary item with newCount = items.length, i.e. the total number of new creatives processed in this run. Guard:** Any new ads? checks whether newCount is greater than 0. If not, the workflow ends silently and no message is sent, avoiding noise. Notify:** When there are new creatives, Send a text message sends a Telegram message to the configured chatId. The message includes {{$json.newCount}} and a fixed link to the Google Sheet, giving you a quick heads‑up without listing individual ads. Setup Instructions To use this template, configure the following components. Credentials Meta Ads / HTTP Header Auth:** Configure the Meta Ads HTTP Header credentials used by: Facebook Ads API by page, Facebook Ads API by keywords, Facebook Ads API pagination. Google Sheets:** Connect your Google account in: Read existing IDs, Add to sheet. Telegram:** Connect your Telegram account credentials in Send a text message. The Add parameters Node Open the Add parameters Set node and customize: ad_active_status: Which ads to monitor (active, all, etc.). search_page_ids: The numeric ID of the competitor Facebook Page you want to track. ad_reached_countries: Comma‑separated list of country codes (US, US, CA, etc.). access_token: A valid long‑lived access token with permission to query the Ads Library. Google Sheets Configuration Read existing IDs** Set documentId and sheetName to your tracking spreadsheet and sheet (e.g. an ads tab). Configure the range to read only the column holding the ad id values. Add to sheet** Point documentId and sheetName to the same spreadsheet/sheet. Make sure your sheet has the columns expected by the node (e.g. id, creation time, page, title, description, delivery_start_time, snapshot, languages, platforms, link). Confirm that id is included in matchingColumns so de‑duplication works correctly. Telegram Configuration In Send a text message, set: chatId: Your target Telegram chat or channel ID. text: Customize the message template as needed, but keep {{$json.newCount}} to show the number of new creatives. Schedule Open Schedule Trigger and configure when you want the workflow to run (e.g. every morning). Save and activate the workflow. Further Ideas & Customization This workflow is a solid foundation for systematic competitor monitoring. You can extend it to: Track multiple competitors** by turning search_page_ids into a list and iterating over it with a loop or separate executions. Enrich the log with performance data** by creating a second workflow that reads the sheet, pulls spend/impressions/CTR for each logged ad_id from Meta, and merges the metrics back. Add more notification channels** such as Slack or email, or send a weekly summary that aggregates new ads by page, format, or country. Tag or categorize creatives** (e.g. “video vs image”, “country”, “language”) directly in the sheet to make later analysis easier.

This n8n workflow automates task creation and scheduled reminders for users via a Telegram bot, ensuring timely notifications across multiple channels like email and Slack. It streamlines task management by validating inputs, storing tasks securely, and delivering reminders while updating statuses for seamless follow-up. Key Features Enables users to create tasks directly in chat via webhook integration. Triggers periodic checks for due tasks and processes them individually for accurate reminders. Routes reminders to preferred channels (Telegram, email, or Slack) based on user settings. Validates inputs, handles errors gracefully, and logs task data for persistence and auditing. Workflow Process The Webhook Entry Point node receives task creation requests from users via chat (e.g., Telegram bot), including details like user ID, task description, and channel preferences. The Input Validation node checks for required fields (e.g., user ID, task description); if validation fails, it routes to the Error Response node. The Save to Database node stores validated task data securely in a database (e.g., PostgreSQL, MongoDB, or MySQL) for persistence. The Success Response node (part of Response Handlers) returns a confirmation message to the user in JSON format. The Schedule Trigger node runs every 3 minutes to check for pending reminders (with a 5-minute buffer for every hour to avoid duplicates). The Fetch Due Tasks node queries the database for tasks due within the check window (e.g., reminders set for within 3 minutes). The Tasks Check node verifies if fetched tasks exist and are eligible for processing. The Split Items node processes each due task individually to handle them in parallel without conflicts. The Channel Router node directs reminders to the appropriate channel based on task settings (e.g., email, Slack, or Telegram). The Email Sender node sends HTML-formatted reminder emails with task details and setup instructions. The Slack Sender node delivers Slack messages using webhooks, including task formatting and user mentions. The Telegram Sender node sends Telegram messages via bot API, including task ID, bot setup, and conversation starters. The Update Task Status node marks the task as reminded in the database (e.g., updating status to "sent" with timestamp). The Workflow Complete! node finalizes the process, logging completion and preparing for the next cycle. Setup Instructions Import the workflow into n8n and configure the Webhook Entry Point with your Telegram bot's webhook URL and authentication. Set up database credentials in the Save to Database and Fetch Due Tasks nodes (e.g., connect to PostgreSQL or MongoDB). Configure channel-specific credentials: Telegram bot token for Telegram Sender, email SMTP for Email Sender, and Slack webhook for Slack Sender. Adjust the Schedule Trigger interval (e.g., every 3 minutes) and add any custom due-time logic in Fetch Due Tasks. Test the workflow by sending a sample task creation request via the webhook and simulating due tasks to verify reminders and status updates. Monitor executions in n8n dashboard and tweak validation rules or response formats as needed for your use case. Prerequisites Telegram bot setup with webhook integration for task creation and messaging. Database service (e.g., PostgreSQL, MongoDB, or MySQL) for task storage and querying. Email service (e.g., SMTP provider) and Slack workspace for multi-channel reminders. n8n instance with webhook and scheduling enabled. Basic API knowledge for bot configuration and channel routing. Modification Options Customize the Input Validation node to add fields like priority levels or recurring task flags. Extend the Channel Router to include additional channels (e.g., Microsoft Teams or SMS via Twilio). Modify the Schedule Trigger to use dynamic intervals based on task urgency or user preferences. Enhance the Update Task Status node to trigger follow-up actions, like archiving completed tasks. Adjust the Telegram Sender node for richer interactions, such as inline keyboards for task rescheduling. Explore More AI Workflows: Get in touch with us for custom n8n automation!

AI Customer Support Triage with Gmail, OpenAI, Airtable & Slack How it Works This workflow monitors your Gmail support inbox every minute, automatically sending each unread email to OpenAI for intelligent analysis. The AI evaluates sentiment (Positive/Neutral/Negative/Critical), urgency level (Low/Medium/High/Critical), categorizes requests (Technical/Billing/Feature Request/Bug Report/General), extracts key issues, and generates professional response templates. The system calculates a priority score (0-110) by combining urgency and sentiment weights, then routes tickets accordingly. Critical issues trigger immediate Slack alerts with full context and 30-minute SLA reminders, while routine tickets post to standard monitoring channels. Every ticket logs to Airtable with complete analysis and thread tracking, then updates a Google Sheets dashboard for real-time analytics. A secondary AI pass generates strategic insights (trend identification, risk assessment, actionable recommendations) and stores them back in Airtable. The entire process takes seconds from email arrival to team notification, eliminating manual triage and ensuring critical issues get immediate attention. Who is this for? Customer support teams needing automated prioritization for high email volumes SaaS companies tracking support metrics and response times Startups with lean teams requiring intelligent ticket routing E-commerce businesses managing technical, billing, and return inquiries Support managers needing data-driven insights into customer pain points Setup Steps Setup time:** 20-30 minutes Requirements:** Gmail, OpenAI API key, Airtable account, Google Sheets, Slack workspace Monitor Support Emails: Connect Gmail via OAuth2, configure INBOX monitoring for unread emails AI Analysis Engine: Add OpenAI API key, system prompt pre-configured for support analysis Parse & Enrich Data: JavaScript code automatically calculates priority scores (no changes needed) Route by Urgency: Configure routing rules for critical vs routine tickets Slack Alerts: Create Slack app, get bot token and channel IDs, replace placeholders in nodes Airtable Database: Create base with "tblSupportTickets" table, add API key and Base ID (replace appXXXXXXXXXXXXXX) Google Sheets Dashboard: Create spreadsheet, enable Sheets API, add OAuth2 credentials, replace Sheet ID (1XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX) Generate Insights: Second OpenAI call analyzes patterns, stores insights in Airtable Test: Send test email, verify Slack alerts, check Airtable/Sheets data logging Customization Guidance Priority Scoring:** Adjust urgency weight (25) and sentiment weight (10) in Code node to match your SLA requirements Categories:** Modify AI system prompt to add industry-specific categories (e.g., healthcare: appointments, prescriptions) Routing Rules:** Add paths for High urgency, VIP customers, or specific categories Auto-Responses:** Insert Gmail send node after routine tickets for automatic acknowledgment emails Multi-Language:** Add Google Translate node for non-English support VIP Detection:** Query CRM APIs or match email domains to flag enterprise customers Team Assignment:** Route different categories to dedicated Slack channels by department Cost Optimization:** Use GPT-3.5 (~$0.001/email) instead of GPT-4, self-host n8n for unlimited executions Once configured, this workflow operates as your intelligent support triage layer—analyzing every email instantly, routing urgent issues to the right team, maintaining comprehensive analytics, and generating strategic insights to improve support operations. Built by Daniel Shashko Connect on LinkedIn

🔐 n8n Workflow: Role-Based Access Control (RBAC) for Telegram Automations This n8n workflow lets you control access to your internal Telegram bots and automation systems based on user roles and departments. It ensures that only authorized team members — defined in your employee database — can interact with specific parts of your workflow. Perfect for agencies, internal tools, or multi-team organizations where permissions differ across roles (e.g., Marketing, Sales, Administration). 📌 Section 1: Trigger & Input ⚡ Receive Message (Telegram Trigger) Purpose: Captures incoming messages from users interacting with your Telegram bot. How it works: When a user sends any message to the bot, the workflow retrieves their Telegram username and triggers the process. Benefit: Provides a secure and instant entry point for validating user identity before running any internal logic. 📌 Section 2: Role Lookup 📋 Employee Database (Data Table Node) Purpose: Fetches user details such as Position and Type from your internal employee table. Structure Example: UserName===Position===Type User_1===Marketing===SEO User_2===Administration===Manager User_3===Marketing===Target Benefit: Centralized employee management — you can update access levels (roles or departments) directly in the data table without editing the workflow. 📌 Section 3: Position & Role Check 🧩 Choose Position (Switch Node) Purpose: Determines the user’s department or role level (e.g., Marketing, Sales, Administration). 🧩 Check Role Type (Switch Node) Purpose: Performs a second-level check — filters users by Type (e.g., SEO, SMM, Target). Logic: Marketing → SEO → Send to SEO workflow branch Marketing → Target → Send to Ads branch Administration → Manager → Grant full access Sales → Employee → Limited access Benefit: Allows multi-level, role-based logic with different automation paths for each team or position. 📌 Section 4: Action Routing 💬 No Operation Nodes (Placeholders) Purpose: Represent different action branches — each can later be replaced with the logic specific to that department. Examples: “Target” branch → connect to ad performance automation “SEO” branch → connect to Google Search Console reports “Sales” branch → connect to CRM updates Benefit: A flexible access framework — ready to integrate with any process per department. 📊 Workflow Overview Table Section Node Name Purpose Trigger Telegram Trigger Captures user messages Lookup Employee Database Fetches user position and type Check Choose Position / Role Switch Defines access path based on role Routing No Operation Nodes Separate workflows per department 🎯 Key Benefits 🔐 Granular Access Control: Multi-level permission logic (Position + Role). ⚙️ Dynamic Role Management: Update access directly in your data table — no redeployment needed. 🧱 Modular Design: Add or replace department branches without affecting core logic. 🚀 Scalable Foundation: Perfect base for enterprise-grade permission systems or multi-team bots. 📈 Cross-Platform Ready: Can be adapted for Slack, Discord, or internal chat tools.

🔐 n8n Workflow: Access Control for Internal Chats or Chatbots This n8n workflow helps you restrict access to your internal chats or chatbots so that only authorized team members can interact with them. It's perfect for setups using Telegram, Slack, or other corporate messengers, where you need to prevent unauthorized users from triggering internal automations. 📌 Section 1: Trigger & Input ⚡ Receive Message (Telegram Trigger) Purpose: Captures every incoming message from a user interacting with your Telegram bot (or another messenger). How it works: When a user sends a message, it instantly triggers the workflow and passes their username or ID as input data. Benefit: Acts as the entry point for verifying whether a user is allowed to proceed. 📌 Section 2: Access Table Lookup 📋 User Access Table (Data Node / Spreadsheet / DB Query) Purpose: Stores all your team members and their current access status. Structure Example: | Username | Access Status | |----------|---------------| | user1 | granted | | user2 | denied | | user3 | granted | Benefit: Centralized access control — you can easily update user permissions without editing the workflow. 📌 Section 3: Permission Check 🧩 Check Access (IF Node) Purpose: Compares the incoming user's name or ID against the access table. Logic: If status = granted → Allow message to continue If status = denied → Stop workflow execution Benefit: Ensures only approved users can interact with your automations or receive responses. 📌 Section 4: Response Handling 💬 Send Reply (Telegram Node) Purpose: Sends a message back to the user depending on their access level. Paths: ✅ Granted: Sends the normal bot response or triggers the main process. ❌ Denied: Sends no reply (or an optional "Access denied" message). Benefit: Prevents unauthorized access while maintaining a seamless experience for approved users. 📊 Workflow Overview Table | Section | Node Name | Purpose | |---------|-----------|---------| | 1. Trigger | Receive Message | Captures incoming messages | | 2. Access Table | User Access Table | Stores usernames + permissions | | 3. Check | Check Access | Verifies if user has permission | | 4. Response | Send Reply | Sends or blocks response based on status | 🎯 Key Benefits 🔐 Secure access control: Only trusted users can trigger your internal automations. ⚙️ Dynamic management: Easily update user permissions from a table or database. 🧠 Lightweight setup: Just three nodes create a fully functional access gate. 🚀 Scalable foundation: Extend it with role-based access or activity logging later.

How it works This workflow automatically generates personalized follow-up messages for leads or customers after key interactions (e.g., demos, sales calls). It enriches contact details from HubSpot (or optionally Monday.com), uses AI to draft a professional follow-up email, and distributes it across multiple communication channels (Slack, Telegram, Teams) as reminders for the sales team. Step-by-step Trigger & Input Schedule Trigger – Runs automatically at a defined interval (e.g., daily). Set Sample Data – Captures the contact’s name, email, and context from the last interaction (e.g., “had a product demo yesterday and showed strong interest”). Contact Enrichment HubSpot Contact Lookup – Searches HubSpot CRM by email to confirm or enrich contact details. Monday.com Contact Fetch (Optional) – Can pull additional CRM details if enabled. AI Message Generation AI Language Model (OpenAI) – Provides the underlying engine for message creation. Generate Follow-Up Message – Drafts a short, professional, and friendly follow-up email: References previous interaction context. Suggests clear next steps (call, resources, etc.). Ends with a standardized signature block for consistency. Multi-Channel Communication Slack Reminder – Posts the generated message as a reminder in the sales team’s Slack channel. Telegram Reminder – Sends the follow-up draft to a Telegram chat. Teams Reminder – Shares the same message in a Microsoft Teams channel. Benefits Personalized Outreach at Scale – AI ensures each follow-up feels tailored and professional. Context-Aware Messaging – Pulls in CRM details and past interactions for relevance. Cross-Platform Delivery – Distributes reminders via Slack, Teams, and Telegram so no follow-up is missed. Time-Saving for Sales Teams – Eliminates manual drafting of repetitive follow-up emails. Consistent Branding – Ensures every message includes a unified signature block.

📉 Buy the Dip Alert (Telegram/Slack/SMS) 📌 Overview This workflow automatically notifies you when Bitcoin or Ethereum drops more than a set percentage in the last 24 hours. It’s ideal for traders who want to stay ready for buy-the-dip opportunities without constantly refreshing charts. ⚙️ How it works Schedule Trigger — runs every 30 minutes (adjustable). HTTP Request (CoinGecko) — fetches BTC & ETH prices and 24h % change. Code Node (“Dip Check”) — compares changes against your dip threshold. IF Node — continues only if dip condition is true. Notification Node — sends alert via Telegram, Slack, or SMS (Twilio). Example Output: Dip Alert — BTC –3.2%, ETH –2.8% Not financial advice. 🛠 Setup Guide 1) Dip threshold Open the Code node. Change the line: const DIP = -2.5; // trigger if 24h drop <= -2.5% Set your preferred dip value (e.g., –5 for a 5% drop). 2) Choose your alert channel Telegram: add your bot token & chat ID. Slack: connect Slack API & set channel name. Twilio: configure SID, token, from/to numbers. 3) Test Temporarily set DIP to 0 to force an alert. Run once from the Code node → confirm alert message text. Execute the Notification node → confirm delivery to your channel. 🎛 Customization Cadence: change Schedule Trigger (every 5m, 15m, hourly, etc.). Coins: extend the CoinGecko call (add solana, bnb) and update Code node logic. Multiple alerts: duplicate IF → Notification branch for different thresholds (minor vs major dip). Combine with “Threshold Alerts” workflow to cover both upside breakouts and downside dips. Storage: log alerts into Google Sheets for tracking dip history. 🧩 Troubleshooting No alerts firing: check CoinGecko API response in Execution Data. Wrong %: CoinGecko returns usd_24h_change directly — no math needed. Duplicate alerts: add a debounce using a Sheet/DB to store last fired time. Telegram not posting: confirm bot has access to your channel/group.

How it works This workflow automatically pulls daily signup stats from your PostgreSQL database and shares them with your team across multiple channels. Every morning, it counts the number of new signups in the last 24 hours, formats the results into a concise report, and posts it to Slack, Microsoft Teams, and Telegram. This ensures your entire team stays updated on customer growth without manual queries or reporting. Step-by-step Daily Trigger & Data Fetching The Daily Report Trigger runs at 9:00 AM each day. The Fetch Signup Count node queries the customers table in PostgreSQL. It calculates the number of new signups in the last 24 hours using the created_at timestamp column. Report Preparation The Prepare Report Message node formats the results into a structured message: Report date Signup count A clear summary line: Daily Signup Report – New signups in the last 24h: X Multi-Channel Delivery The prepared message is sent to multiple platforms simultaneously: Slack Microsoft Teams Telegram This ensures all teams receive the update in their preferred communication tool. Why use this? Automates daily customer growth reporting. Eliminates manual SQL queries and report sharing. Keeps the whole team aligned with real-time growth metrics. Delivers updates across Slack, Teams, and Telegram at once. Provides simple, consistent reporting every day.

How it works? Send a message or a voice note on Telegram right after the meeting. n8n transcribes (if it's a voice note) and sends the text to GPT. GPT generates a structured and professional meeting minutes report. The report is automatically stored in Airtable. Your team is instantly notified in Slack. A formal email is sent via Gmail to the right recipients. 👉 Works for all types of meetings: client calls, team syncs, project updates… whether you type a message or send a quick voice memo. If you need a professional n8n automation agency to build custom workflows like this, check out Vision IA's n8n automation services. ✅ Requirements Before running this workflow, you’ll need: A Telegram account with a bot configured (to send your messages/voice notes) An OpenAI API key (for GPT and voice transcription) An Airtable account with a base containing these fields: Email Subject Report A Slack account with the target channel for notifications A Gmail account connected to n8n (OAuth2) 🔧 Step-by-step setup Step 1 – Telegram Trigger Node**: Telegram Trigger Updates**: message 👉 Captures every message or voice note sent to the bot. Step 2 – Detect text or voice Node**: Code (“Message or Voice ?”) Expected output**: { type: "text", content } if message { type: "voice", file_id } if voice note 👉 Routes the workflow based on the input type. Step 3 – IF Condition Condition**: {{$json.type}} == voice 👉 Directs to the transcription branch if it’s a voice note. Voice Branch 🎤 Step 4 – Download the voice file Node**: Telegram → Voice note Parameter**: fileId = {{$json.file_id}} Step 5 – Wait Node**: Wait (2–3s) 👉 Lets Telegram prepare the file. Step 6 – Voice note download Node**: Telegram (file download) 👉 Retrieves the audio file. Step 7 – Transcribe to text Node**: OpenAI (Transcription) Resource**: audio Operation**: transcribe 👉 Converts the voice note into plain text. Step 8 – Short wait 👉 Ensures continuity before sending to GPT. Text Branch ✍️ Step 9 – Normalize Node**: Code (“Content”) Return**: { text: $json.content } 👉 Standardizes the text as if it were already a transcription. Step 10 – Detect email Node**: Code (“Domain or Email detection”) 👉 Extracts the target email (or builds a fallback [email protected]). Step 11 – Generate meeting minutes Node**: Agent (“Generate Meeting Message”) Prompt**: specialized for “meeting minutes” Model**: GPT-4.1-mini Output**: { email, subject, body } 👉 GPT creates a clean and structured meeting report. Step 12 – Enforce clean JSON Node**: Output Parser Structured JSON Example**: json {"email": "[email protected]","subject":"Subject","body":Email"} 👉 Ensures the output is always valid JSON. Step 13 – Cleanup / Airtable mapping Node**: Code Return**: { Email, subject, Report } 👉 Prepares the correct fields aligned with your Airtable table. If you need help setting up advanced Airtable workflows and database automation, check out Vision IA's Airtable automation services. Step 14 – Store in Airtable Node**: Airtable (Create Record) Mapping**: Email = {{$json.Email}} subject = {{$json.subject}} Report = {{$json.Report}} 👉 Archives each meeting report in your Airtable base. Step 15 – Notify in Slack Node**: Slack (Send Message) Channel**: your team channel Message**: {{$json.fields.subject}}{{$json.fields.Report}} Step 16 – Send the email Node**: Gmail (Send Email) sendTo**: {{$('Create a record').item.json.fields.Email}} subject**: {{$('Create a record').item.json.fields.subject}} message**: {{$('Create a record').item.json.fields.Report}} Need Help Automating Your Communication Workflows? This n8n workflow shows how powerful email automation and AI-powered documentation can be. If you want to go further with automated email campaigns, meeting follow-ups, and team communication systems, our agency specializes in building custom solutions. 👉 Explore our email automation services: Vision IA – Email Automation Agency We help businesses automate their entire communication pipeline—from meeting notes to client follow-ups and internal notifications—all running automatically with AI assistance. Questions about this workflow or other automation solutions? Visit Vision IA or reach out for a free consultation.

Supercharge Your HighLevel CRM with the Power of GPT-5 Unleash the full potential of your HighLevel CRM by adding an intelligent GPT-5 Agent that does more than just follow commands — it understands context, retrieves the right data, and executes actions instantly. This marketplace solution transforms how you work: Act Instantly** – Create, update, and manage contacts, opportunities, tasks, and calendars with natural language commands. Work Smarter, Not Harder** – The agent pulls context from your internal documents, spreadsheets, and even the web before acting, ensuring every move is informed and precise. Never Miss a Detail** – It searches your knowledge base, Google Drive, and Supabase vectors to fill in missing info so you don’t have to. Boost Team Productivity** – Automate repetitive CRM work, cut manual data entry, and free up hours every week. Close Deals Faster** – Instantly update opportunities, schedule meetings, and follow up on leads without switching tabs. Stay Organized Effortlessly** – One AI agent orchestrates it all — from booking appointments to updating deal stages — directly inside HighLevel. Why This Is a Game-Changer Other tools require constant babysitting. This agent thinks ahead, checks context, and ensures every action in your CRM is accurate, complete, and ready to move your business forward. ⚡ Stop clicking through endless menus. Let GPT-5 + HighLevel automation work for you. ✅ Boost conversions ✅ Automate admin work ✅ Keep your CRM data flawless Get it now and watch your CRM become your smartest sales assistant.

📄 n8n RAG Ingestion & Query Workflow Overview This workflow is your all-in-one pipeline to turn any document into a powerful searchable knowledge base using RAG (Retrieval-Augmented Generation). From the moment a file lands in your Google Drive, it’s automatically processed, understood, and made ready for instant AI-powered answers. If you’re looking to unlock hidden value in your files and get answers in seconds instead of hours, this workflow is the foundation you need. What It Does for You 📥 Automatic Ingestion** – New files in a designated Google Drive folder are instantly picked up. 🔍 OCR Extraction* – Extracts all* text, whether it’s plain or inside tables. 📚 Vector Database Storage* – Keeps your documents in Supabase* for lightning-fast semantic search. 🧩 Smart Chunking** – Each page becomes a single chunk for better understanding. 💡 AI-Powered Answers** – Ask questions in natural language and get precise, context-aware responses. 🧠 Persistent Memory** – Remembers previous chats for more coherent conversations. ⚡ GPT-5 Intelligence** – Uses OpenAI’s most advanced model for deep, accurate answers. How It Works Detect → Watches your Google Drive folder for new files. Extract → Uses Mistral AI to read all text, including tables. Chunk → Splits content so one page = one chunk for better context. Embed → Generates vector embeddings with OpenAI for semantic search. Store → Inserts processed content into Supabase. Retrieve & Answer → When you ask, the system searches the database and passes the results to GPT-5. Remember → Stores conversation history in Postgres for continuity. Why You Want This Stop wasting time digging through files. Get fast, AI-driven answers from your own documents. Keep your data organized and searchable at any scale. Designed for businesses, researchers, and teams who want instant access to the right information. You get the template + setup guide and description Key Highlights End-to-End Automation** – From upload to query, no manual steps needed. Flexible** – Works with any document type. High Accuracy** – Large chunk size preserves full page context. Scalable** – Add as many files as you want without slowing down. Future-Ready** – Built to grow with your needs. 🚀 Imagine having your own private ChatGPT trained on your files. This workflow makes it happen. Upload, search, and get answers — all automatically.

🚀 AI-Powered Stock Analysis Chatbot Transform Your Investment Decisions with Advanced AI Analytics 🎯 What It Does This intelligent chatbot leverages cutting-edge financial APIs and AI-driven analysis to deliver comprehensive stock research reports. Get instant access to professional-grade investment analysis that combines multiple data sources for informed decision-making. ✨ Key Features 📊 AI-Driven Stock Scoring Powered by Danelfin's proprietary AI algorithms Real-time scoring across 5 key metrics: AI Score, Technical, Fundamental, Sentiment, and Low-Risk ratings Access to comprehensive stock rankings and sector analysis 📈 Advanced Technical Analysis Integration with TwelveData for precise technical indicators Bollinger Bands, MACD, RSI, and moving averages analysis Historical price data and trend identification 🖼️ Visual Chart Integration Automatic generation of professional candlestick charts Chart-img API integration for clear visual representations Charts embedded directly in analysis reports 📰 Sentiment Analysis Alpha Vantage news sentiment scoring Market intelligence and sentiment tracking Real-time news impact assessment 🧠 Vector-Powered Intelligence Supabase vector storage for pattern recognition Advanced data correlation and historical analysis Intelligent recommendation engine 📋 What You Get Comprehensive Markdown Reports Including: Executive Summary** with actionable insights Detailed Stock Analysis** with AI scoring breakdown Interactive Charts** for each analyzed stock Technical Indicators** and trend analysis Current Stock Prices** and market data Risk Assessment** and sentiment evaluation Investment Recommendations** tailored to your strategy 🎯 Perfect For Individual Investors** seeking professional-grade analysis Financial Advisors** needing quick research reports Portfolio Managers** requiring data-driven insights Day Traders** looking for technical analysis Long-term Investors** focused on fundamental analysis 🔧 How It Works Ask About Any Stock - Simply mention a ticker or describe your investment criteria AI Screening - The bot queries multiple APIs to gather comprehensive data Advanced Analysis - Technical indicators, sentiment, and AI scoring are processed Professional Report - Receive a detailed markdown report with charts and recommendations Instant Delivery - Get results in seconds, not hours 🛡️ Data Sources & Reliability Danelfin**: AI-powered stock scoring and rankings TwelveData**: Professional-grade market data and technical indicators Alpha Vantage**: News sentiment and market intelligence Chart-img**: High-quality financial chart generation Supabase**: Advanced vector database for pattern analysis 💡 Sample Use Cases "Analyze the top 3 tech stocks with highest AI scores" "Find low-risk dividend stocks in the utilities sector" "Compare AAPL vs MSFT with technical analysis" "Show me growth stocks with strong buy signals" "Analyze energy sector performance this week"

🎧 IT Voice Support Automation Bot – Telegram Voice Message to JIRA ticket with OpenAI Whisper > Automatically process IT support requests submitted via Telegram voice messages by transcribing, extracting structured data, creating a JIRA ticket, and notifying relevant parties. 🧑‍💼 Who’s it for Internal teams that handle IT support but want to streamline voice-based requests. Employees who prefer using mobile/voice to report incidents or ask for support. Organizations aiming to integrate conversational AI into existing support workflows. ⚙️ How it works / What it does A user sends a voice message to a Telegram bot. The system checks whether it’s an audio message. If valid, the audio is: Downloaded Transcribed via OpenAI Whisper Backed up to Google Drive The transcription and file metadata are merged. The merged content is processed through an AI Agent (GPT) to extract structured request info. A JIRA ticket is created using the extracted data. The IT team is notified via Slack (or other channels). The requester receives a Telegram confirmation message with the JIRA ticket link. If the input is not audio, a polite rejection message is sent. 📌 Key Features Supports voice-based ticket creation Accurate transcription using Whisper Context-aware request parsing using GPT-4.1 mini Fully automated ticket creation in JIRA Notifies both IT and the original requester Cloud backup of original voice messages (Google Drive) 🛠️ Setup Instructions Prerequisites | Component | Required | |----------|----------| | Telegram Bot & API Key | ✅ | | OpenAI Whisper / Transcription Model | ✅ | | Google Drive Credentials (OAuth2) | ✅ | | Google Sheets or other storage (optional) | ⬜ | | JIRA Cloud API Access | ✅ | | Slack Bot or Webhook | ✅ | Workflow Steps Telegram Voice Message Trigger: Starts the flow when a user sends a voice message. Is Audio Message?: If false → reply "only voice is supported" Download Audio: Download .oga file from Telegram. Transcribe Audio: Use OpenAI Whisper to get text transcript. Backup to Google Drive: Upload original voice file with metadata. Merge Results: Combine transcript and metadata. Pre-process Output: Clean formatting before AI extraction. Transcript Processing Agent: GPT-based agent extracts: Requester name, department Request title & description Priority & request type Submit JIRA Request Ticket: Create ticket from AI-extracted data. Setup Slack / Email / Manual Steps: Optional internal routing or approvals. Inform Reporter via Telegram: Sends confirmation message with JIRA ticket link. 🔧 How to Customize Replace JIRA with Zendesk, GitHub Issues, or other ticketing tools. Change Slack to Microsoft Teams or Email. Add Notion/Airtable logging. Enhance agent to extract department from user ID or metadata. 📦 Requirements | Integration | Notes | |-------------|-------| | Telegram Bot | Used for input/output | | Google Drive | Audio backup | | OpenAI GPT + Whisper | Transcript & Extraction | | JIRA | Ticketing platform | | Slack | Team notification | Built with ❤️ using n8n

🚀 AI OPS Agent for n8n — Stop Doing Busy Work. Start Leading. Your AI workforce is ready. Are you? 💰 What You Get: Your ROI in 30 Days Replace 10-15 hours/week of manual work with intelligent automation that actually understands your business. While your competitors copy-paste data between tools, you'll be making strategic decisions. 🧠 The Powerhouse Stack That Does Everything | Module | Core Job | Your Competitive Edge | |------------|-------------|--------------------------| | MAIN AGENT (Grok 4) | Orchestrator & brain | • Reads your message → builds execution plan• Delegates to specialized agents• Delivers results through your preferred channel | | Knowledge Agent | Company-wide research assistant | • Vector-searches your Supabase docs instantly• Runs live SQL queries for real-time numbers• Hunts & parses Drive files automatically• Pulls fresh web intelligence via Perplexity | | Google Sheets MCP Toolkit | Spreadsheet automation | Natural-language control over read/append/update/clear/create/delete operations on any tab or range | | Google Drive MCP Toolkit | File intelligence pipeline | • Auto-detects file types & extracts text from PDFs/CSVs• Transcribes audio/video content• Describes images with GPT-4o Mini | | Vector Store Loader | Long-term memory system | • Auto-chunks new files• Creates OpenAI embeddings• Stores in Supabase for instant semantic search | | Postgres Chat Memory | Conversation context | Never repeat yourself—every follow-up question builds on previous context | | Report Agent | Executive briefing machine | • Converts raw outputs → clean Markdown → HTML• Auto-emails/Slacks/Telegrams polished reports | | LinkedIn Scraper | Talent & market intelligence | Scrapes full LinkedIn profiles via Apify, delivers structured JSON for analysis | | Multi-Channel Triggers | Meet users where they work | Slack • Gmail • Telegram • WhatsApp • HTTP Webhooks | | LLM Layer | Right model, right job | Grok 4 (reasoning) • Claude Sonnet 4 (analysis) • GPT-4o Mini (speed) • Perplexity (live web) | ⚡ How It Works (The Magic in 5 Steps) Message arrives (Slack mention, email, webhook) MAIN AGENT analyzes → selects optimal tool chain Specialized toolkits execute (Sheets, Drive, SQL, Scraper...) Knowledge Agent synthesizes everything using the perfect LLM Report Agent packages & delivers results to your chosen channel 🎯 Real Commands That Save Hours Daily > "Update the Marketing-Spend sheet with last week's totals, then email me a chart." > > "Find the product-launch PDF from Drive, summarize key risks, post to Slack." > > "Scrape this LinkedIn URL, rank the candidate's skills, add them to our CRM sheet." > > "Create a new Sprint 11 tab, copy headers from Sprint 10, and ping the team." One command. Multiple systems. Zero manual work. Why Choose This Over Other Products: ✅ All Your Data, One Brain No more jumping between 12 different tools. Your AI agent connects everything. You can go further If you want to increase the Agent capabilities or make the more powerfull you can reach the dev. ✅ Vector Search Built-In Upload a 100-page document once. Search it forever with natural language. ✅ Executive-Ready Reports Your C-suite gets clean HTML briefs, not raw data dumps that waste their time. ✅ Deploy in Minutes Plug into your existing n8n setup, add credentials, watch routine ops handle themselves.

🟡 DESCRIPTION This n8n workflow automates the daily generation of comprehensive analytics reports from multiple websites, processes them using OpenAI's powerful language models, and then delivers the insights directly to your email and Slack channels. Designed for digital marketers, website administrators, and data analysts, this template streamlines the tedious process of manually collecting and interpreting website performance data, offering immediate, actionable intelligence. The core problem this workflow solves is the fragmentation and manual effort involved in monitoring numerous website analytics. Instead of logging into multiple Google Analytics accounts or properties daily, this workflow centralizes data extraction, enriches it with AI-powered summaries, and distributes it to your preferred communication platforms. This significantly reduces the time spent on routine reporting, allowing you to focus on strategy and decision-making. Users who would benefit most from this template include: Digital Marketing Agencies: Efficiently generate and share client reports across multiple properties. E-commerce Businesses: Monitor performance of various product sites or regional domains. Content Creators: Track the success of different blogs or content platforms. Anyone managing a portfolio of websites: Gain a unified view of their digital assets' performance. 🟡 SETUP Before importing and running this workflow, ensure you have the following prerequisites in place: ► Google Analytics API Setup: Go to the Google Cloud Console (https://console.cloud.google.com/). Create a new project or select an existing one. Navigate to "APIs & Services" > "Enabled APIs & services." Search for and enable the "Google Analytics Data API" (for GA4) or "Google Analytics Reporting API" (for Universal Analytics, if still in use). Go to "APIs & Services" > "Credentials." Create "OAuth client ID" credentials for a "Web application." Copy your client ID and client secret. In n8n, add a new Google Analytics credential using the "OAuth2" authentication method. Provide the Client ID and Client Secret. You will need to authorize n8n to access your Google Analytics data. Scopes https://www.googleapis.com/auth/analytics.readonly (read-only) or https://www.googleapis.com/auth/analytics (manage) OAuth Redirect URL Already pre-filled by n8n (copy this when creating the Google client) Click Sign in with Google, choose the GA account, and approve the requested scopes. Click Save – n8n tests the token and stores it encrypted. For each yourwebsite.com node, select these credentials and specify the correct Google Analytics View ID (for Universal Analytics) or Property ID (for GA4). ► Email Credentials (SMTP): In n8n, add a new SMTP credential. Provide your SMTP host, port, username, and password. This will be used to send the aggregated reports. ► Slack Credentials: In n8n, add a new Slack credential. Follow the instructions to create a Slack App and generate a Bot User OAuth Token. This token will allow n8n to post messages to your Slack channels. ► OpenAI Credentials: Sign up for an OpenAI account (https://platform.openai.com/). Generate an API Key from your account dashboard. In n8n, add a new OpenAI credential and paste your API Key. ► Website Configuration: The workflow currently includes nodes for yourwebsite.com (1 to 8). For each "Get Report" node (e.g., yourwebsite.com, yourwebsite.com 2, etc.), duplicate or remove them as needed to match the number of Google Analytics properties you wish to monitor. Replace the names and number of websites inside the report maker agent. 🟡 Usage Once you have configured the credentials, you can customize the workflow to fit your specific needs, including leveraging various alternative nodes for sending notifications and reports. This flexibility allows you to integrate seamlessly with your preferred communication tools such as Gmail, Telegram, Outlook, or any other service supported by n8n's extensive node library.

AI Blog Automation System Description This comprehensive N8N automation template revolutionizes content creation by delivering a complete end-to-end solution for AI-powered blog generation. Transform simple ideas into fully SEO-optimized, WordPress-ready articles that rank higher and drive organic traffic to your website. The system accepts blog requests from multiple communication channels (Telegram, WhatsApp, Slack, Gmail) and automatically processes them through an intelligent pipeline that includes advanced keyword research, competitor analysis, and market insights. Using cutting-edge AI models like GPT-4 and OpenRouter, the workflow generates detailed content outlines, conducts comprehensive research, and produces high-quality, engaging blog posts that are automatically formatted and published directly to your WordPress website. What sets this template apart is its focus on SEO excellence - every piece of content is optimized for search engines with proper keyword density, meta descriptions, internal linking strategies, and content structure that search engines love. The integrated content tracking system maintains a database of all published articles, enabling smart internal linking recommendations and content performance monitoring. Key Features 🤖 Advanced AI Content Generation GPT-4 & OpenRouter Integration** - Leverage the most powerful AI models for superior content quality Multi-stage content refinement** - From outline to final polish, ensuring professional-grade articles Topic research and fact-checking** - AI conducts deep research to create authoritative, well-sourced content 🎯 SEO Optimization at Every Step Intelligent keyword research** - Automatic discovery of high-volume, low-competition keywords Competitor analysis** - Analyze top-ranking content to identify content gaps and opportunities On-page SEO optimization** - Perfect keyword density, meta descriptions, and heading structure Internal linking strategy** - Smart recommendations for linking to existing content SEO-friendly URL generation** - Automatically create search-engine optimized permalinks 🔌 Seamless WordPress Integration Direct publishing** - Articles go live on your WordPress site without manual intervention Custom post formatting** - Proper heading tags, featured images, and category assignment Draft and scheduling options** - Choose immediate publishing or schedule for optimal timing Media handling** - Automatic image optimization and alt-text generation 📱 Multi-Platform Input System Telegram, WhatsApp, Slack, Gmail support** - Accept blog ideas from your preferred communication channels Voice message transcription** - Convert audio ideas into written blog requests Email parsing** - Extract blog topics from client emails or team communications Priority queue management** - Handle multiple requests efficiently with smart prioritization 📊 Content Management & Analytics Comprehensive content database** - Track all published articles, keywords, and performance metrics Internal linking opportunities** - Automatic suggestions for connecting related content Publishing schedule optimization** - AI-recommended posting times for maximum engagement Performance tracking** - Monitor which topics and keywords drive the most traffic 📋 Complete Setup Guide Included This template comes with a comprehensive step-by-step setup guide that walks you through: N8N workflow installation and configuration** API key setup** for all integrated services (OpenAI, WordPress, communication platforms) WordPress plugin installation** and permissions configuration Database setup** for content tracking and analytics Custom field configuration** for SEO optimization Webhook configuration** for multi-platform input Testing procedures** to ensure everything works perfectly Troubleshooting guide** for common issues Best practices** for content optimization and workflow management Perfect for content creators, digital marketers, SEO specialists, and enterprises looking to scale their content production while maintaining high quality and search engine visibility. Whether you're managing a single blog or multiple WordPress sites, this automation system transforms your content workflow from manual labor to intelligent automation.

Who is this for? This workflow is designed for developers, DevOps engineers, and automation specialists who manage multiple n8n workflows and need a reliable way to monitor for failures and receive alerts in real time. What problem is this workflow solving? Monitoring multiple workflows can be challenging, especially when silent failures occur. This workflow helps ensure you're immediately informed whenever another workflow fails, reducing downtime and improving system reliability. What this workflow does The solution consists of two parts: ERROR NOTIFIER: A centralized workflow that sends alerts through your chosen communication channel (e.g., Telegram, WhatsApp, Gmail). ERROR ALERTER: A node snippet to be added to any workflow you want to monitor. It captures errors and triggers the ERROR NOTIFIER workflow. Once set up, this system provides real-time error alerts for all integrated workflows. Setup Import both workflows: ERROR NOTIFIER (centralized alert handler) ERROR ALERTER (to be added to your monitored workflows) Add credentials for your preferred alert channel: WhatsApp (OAuth or API) Telegram Gmail Discord Slack Activate the workflows: Ensure ERROR NOTIFIER is active and ready to receive triggers. Paste ERROR ALERTER at the end of each workflow you want to monitor, connecting it to the error branch. Sign up for a free consultation and find out how n8n can help you.