Microsoft Teams and Slack integration

Who Is This For? This workflow is designed for Google Ads advertisers, PPC managers, and marketing teams who want to automatically monitor and optimize their search term performance. It's particularly valuable for those running brand campaigns who need to identify and eliminate wasteful ad spend on non-brand keywords. What This Workflow Does This workflow functions as an automated Google Ads performance monitoring and optimization system that: Fetches search term data from active Google Ads campaigns daily Filters out brand terms and excluded search terms automatically Analyzes performance metrics using AI to identify wasteful keywords Generates optimization recommendations for negative keyword lists Sends detailed reports through multiple communication platforms Calculates ad wastage in USD for better budget management Key Features Automated Daily Monitoring** – Runs every day at 8 AM to check campaign performance AI-Powered Analysis** – Uses multiple AI models (DeepSeek, OpenAI, xAI, Anthropic) for intelligent keyword categorization Performance Metrics Calculation** – Automatically calculates CTR, CPC, conversions, and ad wastage Multi-Channel Reporting** – Sends reports to Slack, Microsoft Teams, WhatsApp, and Discord Smart Filtering** – Automatically excludes brand terms and excluded search terms Cost Analysis** – Calculates total ad wastage in USD for budget optimization 14-Day Data Window** – Analyzes search terms from the past 14 days for comprehensive insights Requirements & Setup Google Ads API**: Required for fetching campaign and search term data AI Model APIs**: DeepSeek, OpenAI, xAI, or Anthropic for keyword analysis Communication APIs**: Slack, Microsoft Teams, WhatsApp (Rapiwa), Discord for report distribution Scheduled Trigger**: Configured to run daily at 8 AM Google Ads Manager and Client IDs**: For accessing specific campaign data How It Works Data Collection: Fetches active campaigns and extracts search term data from the past 14 days Data Processing: Cleans and aggregates metrics by search term, campaign, and ad group AI Analysis: Uses AI to categorize keywords into wasteful (zero conversions) and review-worthy (has conversions) Report Generation: Creates structured reports with recommendations and cost analysis Multi-Platform Distribution: Sends formatted reports to all configured communication channels Support & Help WhatsApp**: Chat on WhatsApp Discord**: SpaGreen Community Facebook Group**: SpaGreen Support Website**: https://spagreen.net Developer Portfolio**: Codecanyon SpaGreen

Who it's for This advanced n8n workflow is designed for SEO specialists, digital agency owners, webmasters, and marketing managers who need a comprehensive, automated solution to track and improve their website's search engine performance. It acts as a virtual SEO analyst, automatically gathering data from multiple sources (Google Analytics, Search Console, PageSpeed Insights, and technical audits), analyzing them with AI agents, and delivering actionable insights via various communication channels. Features Multi-Source Data Collection**: Automatically fetches data from Google Analytics (GA4), Google Search Console, PageSpeed Insights, and performs on-page technical audits. Dual Trigger Modes**: Run the report automatically on a monthly schedule or trigger it instantly via Telegram by sending an "SEO Analysis" command. AI-Powered Analysis**: Utilizes specialized LangChain Agents (Analytics, Performance, SEO, Technical) to analyze raw data and generate human-readable insights. History Tracking**: Reads and writes historical data to Google Sheets, allowing AI agents to compare current performance against past data for trend analysis. Technical SEO Audit**: Crawls the website homepage to extract meta tags, headings (H1), and image alt attributes to calculate an on-page SEO score. Executive Summaries**: Generates a comprehensive "Master Analyst" report that aggregates findings from all agents into a unified action plan. Multi-Channel Reporting**: Sends the final SEO report simultaneously to Slack, Microsoft Teams, Discord, WhatsApp (via Rapiwa), and Telegram. Smart Filtering**: Includes Telegram verification logic to restrict report generation to authorized admins or alert the admin when a user requests an analysis. Requirements Google APIs**: Credentials for Google Analytics (GA4), Google Search Console, and Google Sheets OAuth2. OpenAI API**: Required for the LangChain Agents (using models like gpt-4.1-mini and gpt-4.1-nano) to process data and generate insights. Telegram API**: For triggering the workflow and receiving the final report. Slack API**: To post messages to a specific Slack channel. Microsoft Teams API**: To send notifications to a Team or channel. Discord Bot API**: To post rich embed updates to a Discord server. Rapiwa (WhatsApp)**: To send the report via WhatsApp messages. Important Notes Permissions**: Ensure your Google Cloud Project has access to the specific View ID for Analytics and the Site URL for Search Console. Telegram Setup**: You must update the Chat ID in the "Send SEO Report Message" node to ensure the report goes to the correct recipient. The workflow includes a check to validate the user ID against an admin list. Data Aggregation**: The workflow uses a "Merge" node to combine outputs from four different AI agents. Ensure all agents complete successfully before the merge step. Sheet ID**: The Google Sheets nodes (Append row, Get GA History, etc.) require the specific Document ID and Sheet Name to be populated to read/write history correctly. Target Domain**: Update the Edit Fields (Add Your Target Website URL) node with your specific domain (e.g., https://yourwebsite.com) before activating. Support & Help WhatsApp**: Chat on WhatsApp Discord**: SpaGreen Community Facebook Group**: SpaGreen Support Website**: spagreen.net Developer Portfolio**: Codecanyon SpaGreen

Who it's for This n8n workflow is designed for SEO managers, content creators, and blog administrators who want to automate their blog publishing pipeline. The workflow creates an end-to-end AI-powered system that can fetch content ideas from a Google Sheet, scrape existing competitor URLs, analyze SEO structure, generate high-quality articles, validate SEO scores, create thumbnail images, and automatically publish the final content to Webflow. Features Automated Content Scheduling** – Runs every 2 hours (or manually) to process pending blog ideas from Google Sheets. HTML Scraping & Cleaning** – Fetches competitor URLs and removes headers, scripts, and iframes to get clean content. AI SEO Structure Analysis** – Uses gpt-4.1-mini to extract key sections and SEO bullet points. AI Content Writer** – Uses o4-mini to rewrite articles with proper SEO, H2/H3 tags, and keyword optimization. Output Parser Fixing** – Ensures the AI always returns clean, structured JSON (article + summary). Internal Linking** – Pulls existing Webflow posts and adds relevant internal links automatically. SEO Validation** – Checks SEO scores via sub-workflow before publishing. AI Thumbnail Generation** – Creates a 16:9 cover image based on the article topic using DALL·E. Auto-Publishing** – Publishes content to Webflow CMS with title, image, article, summary, and read time. Sheet Update** – Marks the processed row as “Completed” in Google Sheets. Error Notifications** – Sends alerts via Slack, Discord, Teams, Telegram, and WhatsApp if something fails. Requirements OpenAI API Credentials**: For powering the content writer (o4-mini), structure analyzer (gpt-4.1-mini), prompt generator (o4-mini), and image generation (DALL-E 3). Google Sheets API**: For reading pending blog ideas and updating their completion status. Webflow OAuth2 API**: For fetching existing posts (for internal linking) and publishing new CMS items. n8n Sub-Workflow**: A secondary workflow ID (7FHTcSuCIjHvvBfe) is called to evaluate the SEO score percentages of the generated content. Communication Platform Credentials (Optional but recommended)**: API tokens for Slack, Discord, Microsoft Teams, Telegram, and Rapiwa for error notifications. Configure Credentials OpenAI API**: Ensure your account has access to o4-mini, gpt-4.1-mini, and DALL-E 3 models. Google Sheets**: Configure with read/write permissions for the specific spreadsheet and tab (Blogs (ideas)). Webflow API**: Set up OAuth2 with access to the specific Site ID and Collection ID where your blog is hosted. Error Channels**: Add your specific Channel IDs, Chat IDs, and phone numbers to the respective notification nodes. Important Notes Content Looping & Error Handling**: If the SEO score doesn't pass the validation check (e.g., required percentages aren't met), the workflow loops the content back to the AI writer for regeneration. Competitor Name Replacement**: The AI prompt is strictly instructed to replace competitor names (like PixelCut, CreatorKit) with "ProductAI" to maintain brand consistency. CTA Linking**: All Call-to-Action links within the generated articles are hard-coded in the prompt to point to create.productai.photo. Image Processing Delay**: There is a 20-second "Wait" node implemented before publishing to Webflow to ensure the DALL-E generated image URL is active and accessible. Dynamic Title Extraction**: The workflow uses a Regex code snippet to extract the first `` tag from the generated article to use as the Webflow post title (since H1 is omitted per SEO best practices). Data Routing**: The Execute Once feature is enabled on error notification nodes to ensure you only receive one alert per failure, rather than spamming all connected channels simultaneously. Support & Help WhatsApp**: Chat on WhatsApp Discord**: SpaGreen Community Facebook Group**: SpaGreen Support Website**: spagreen.net Developer Portfolio**: Codecanyon SpaGreen

Who Is This For? This workflow is designed for business analysts, market researchers, lead generation specialists, and sales teams who need to gather detailed business intelligence from Google Maps. It's particularly valuable for anyone conducting competitor analysis, building prospect lists, or researching local business landscapes. What This Workflow Does This workflow functions as an automated Google Maps data extraction and intelligence system that: Searches for businesses on Google Maps based on a specific query and location Extracts comprehensive data for each listing, including name, rating, address, phone, website, and reviews Structures the raw data into a clean, usable format for analysis Programmatically initiates the scraping process using a dedicated, cloud-based scraping tool Monitors the scraping job until completion, ensuring all data is captured Delivers the final dataset in a structured JSON format, ready for integration into CRMs, spreadsheets, or other applications Key Features On-Demand Data Extraction** – Can be triggered anytime to scrape fresh data from Google Maps Comprehensive Data Points** – Captures a wide range of information including ratings, reviews, contact details, and URLs Cloud-Powered Scraping** – Leverages a specialized, pre-built actor (crawler-google-places) from the Apify platform for reliable and efficient scraping Automated Job Management** – Automatically starts, monitors, and waits for the scraping task to complete Structured Output** – Delivers clean, structured JSON data that is easy to parse and use Programmatic Control** – Manages the entire process through API calls, making it easy to integrate into other workflows Requirements & Setup Apify Account & API Token**: Required to access and run the Google Maps scraping actor. Apify Actor ID**: The specific ID for the crawler-google-places actor (nwua9GuXXXXDL7ZDj). Apify Task ID**: An optional pre-configured task (IldouXXXQalCKQpfO) for consistent scraping parameters. Input Parameters**: You need to provide the searchString (e.g., "restaurants near Islamic University") and other scraping options. Support & Help WhatsApp**: Chat on WhatsApp Discord**: SpaGreen Community Facebook Group**: SpaGreen Support Website**: https://spagreen.net Developer Portfolio**: Codecanyon SpaGreen

Employee Directory Sync – Microsoft Teams & Coda ⚠️ COMMUNITY TEMPLATE DISCLAIMER: This is a community-contributed template that uses ScrapeGraphAI (a community node). Please ensure you have the ScrapeGraphAI community node installed in your n8n instance before using this template. This workflow keeps your employee directory perfectly synchronized across your HRIS (or any REST-compatible HR database), Microsoft Teams, Coda docs, and Slack channels. It automatically polls the HR system on a schedule, detects additions or updates, and propagates those changes to downstream tools so everyone always has the latest employee information. Pre-conditions/Requirements Prerequisites An active n8n instance (self-hosted or n8n cloud) ScrapeGraphAI community node installed A reachable HRIS API (BambooHR, Workday, Personio, or any custom REST endpoint) Existing Microsoft Teams workspace and a team/channel for announcements A Coda account with an employee directory table A Slack workspace and channel where directory updates will be posted Required Credentials Microsoft Teams OAuth2** – To post adaptive cards or messages Coda API Token** – To insert/update rows in your Coda doc Slack OAuth2** – To push notifications into a Slack channel HTTP Basic / Bearer Token** – For your HRIS REST endpoint ScrapeGraphAI API Key** – (Only required if you scrape public profile data) HRIS Field Mapping | HRIS Field | Coda Column | Teams/Slack Field | |------------|-------------|-------------------| | firstName| First Name| First Name | | lastName | Last Name | Last Name | | email | Email | Email | | title | Job Title | Job Title | | department| Department| Department | (Adjust the mapping in the Set and Code nodes as needed.) How it works This workflow keeps your employee directory perfectly synchronized across your HRIS (or any REST-compatible HR database), Microsoft Teams, Coda docs, and Slack channels. It automatically polls the HR system on a schedule, detects additions or updates, and propagates those changes to downstream tools so everyone always has the latest employee information. Key Steps: Schedule Trigger**: Fires daily (or at your chosen interval) to start the sync routine. HTTP Request**: Fetches the full list of employees from your HRIS API. Code (Delta Detector)**: Compares fetched data with a cached snapshot to identify new hires, departures, or updates. IF Node**: Branches based on whether changes were detected. Split In Batches**: Processes employees in manageable sets to respect API rate limits. Set Node**: Maps HRIS fields to Coda columns and Teams/Slack message fields. Coda Node**: Upserts rows in the employee directory table. Microsoft Teams Node**: Posts an adaptive card summarizing changes to a selected channel. Slack Node**: Sends a formatted message with the same update. Sticky Note**: Provides inline documentation within the workflow for maintainers. Set up steps Setup Time: 10-15 minutes Import the workflow into your n8n instance. Open Credentials tab and create: Microsoft Teams OAuth2 credential. Coda API credential. Slack OAuth2 credential. HRIS HTTP credential (Basic or Bearer). Configure the HRIS HTTP Request node Replace the placeholder URL with your HRIS endpoint (e.g., https://api.yourhr.com/v1/employees). Add query parameters or headers as required by your HRIS. Map Coda Doc & Table IDs in the Coda node. Select Teams & Slack channels in their respective nodes. Adjust the Schedule Trigger to your desired frequency. Optional: Edit the Code node to tweak field mapping or add custom delta-comparison logic. Execute the workflow manually once to verify proper end-to-end operation. Activate the workflow. Node Descriptions Core Workflow Nodes: Schedule Trigger** – Initiates the sync routine at set intervals. HTTP Request (Get Employees)** – Pulls the latest employee list from the HRIS. Code (Delta Detector)** – Stores the previous run’s data in workflow static data and identifies changes. IF (Has Changes?)** – Skips downstream steps when no changes were detected, saving resources. Split In Batches** – Iterates through employees in chunks (default 50) to avoid API throttling. Set (Field Mapper)** – Renames and restructures data for Coda, Teams, and Slack. Coda (Upsert Rows)** – Inserts new rows or updates existing ones based on email match. Microsoft Teams (Post Message)** – Sends a rich adaptive card with the update summary. Slack (Post Message)** – Delivers a concise change log to a Slack channel. Sticky Note** – Embedded documentation for quick reference. Data Flow: Schedule Trigger → HTTP Request → Code (Delta Detector) Code → IF (Has Changes?) If No → End If Yes → Split In Batches → Set → Coda → Teams → Slack Customization Examples Change Sync Frequency // Inside Schedule Trigger { "mode": "everyDay", "hour": 6, "minute": 0 } Extend Field Mapping // Inside Set node items[0].json.phone = item.phoneNumber ?? ''; items[0].json.location = item.officeLocation ?? ''; return items; Data Output Format The workflow outputs structured JSON data: { "employee": { "id": "123", "firstName": "Jane", "lastName": "Doe", "email": "[email protected]", "title": "Senior Engineer", "department": "R&D", "status": "New Hire", "syncedAt": "2024-05-08T10:15:23.000Z" }, "destination": { "codaRowId": "row_abc123", "teamsMessageId": "msg_987654", "slackTs": "1715158523.000200" } } Troubleshooting Common Issues HTTP 401 from HRIS API – Verify token validity and that the credential is attached to the HTTP Request node. Coda duplicates rows – Ensure the key column in Coda is set to “Email” and the Upsert option is enabled. Performance Tips Cache HRIS responses in static data to minimize API calls. Increase the Split In Batches size only if your API rate limits allow. Pro Tips: Use n8n’s built-in Version Control to track mapping changes over time. Add a second IF node to differentiate between “new hires” and “updates” for tailored announcements. Enable Slack’s “threaded replies” to keep your #hr-updates channel tidy.

How It Works Aggregates communication data from Slack, Microsoft Teams, Gmail, GitHub, and Confluence into a single, unified AI-powered analysis workflow designed for quality review and automated documentation updates. This solution is specifically aimed at teams managing distributed content and knowledge workflows across multiple platforms. It addresses the challenges of fragmented communication and isolated information silos that often prevent rapid content review and timely decision-making. The workflow begins with a scheduled trigger, followed by multi-source data collection, merging and normalizing inputs, Claude AI-powered analysis, validation and quality checks, formatting, and finally publishing updates to Notion and Confluence, accompanied by Slack notifications to ensure stakeholders are promptly informed. Setup Steps -Connect credentials: Slack API, Teams, Gmail OAuth, GitHub PAT. -Confluence API, Anthropic API key, Notion Integration. -Configure monitored channels/repositories. -Set schedule frequency. -Map output destinations (Notion/Confluence). -Test merged output before enabling automation. Prerequisites Slack workspace, Teams account, Gmail access, GitHub repository, Confluence space, Anthropic API key, Notion workspace, n8n instance. Use Cases Content review teams processing feedback, documentation teams aggregating updates, QA teams reviewing communications Customization Add/remove source nodes, adjust Claude prompts for analysis type, modify output destinations Benefits Saves 6+ hours weekly, eliminates missed content, AI-driven quality assurance