Notion and Google Sheets integration

📘 Description This workflow automates the employee onboarding process by creating Jira accounts, generating Notion onboarding checklists, crafting AI-generated welcome messages, and sending personalized welcome emails — all automatically. It provides a complete hands-free onboarding experience for HR and IT teams by connecting Jira, Notion, Google Sheets, Gmail, and Azure OpenAI. Failures (like Jira account creation errors) are logged into Google Sheets to ensure full transparency and no missed onboardings. ⚙️ What This Workflow Does (Step-by-Step) 🟢 When Clicking “Execute Workflow” Manually triggers the entire onboarding automation. Useful for testing or initiating onboarding on demand for a new hire. 👤 Define New Hire Profile Data Structures all essential employee information into a clean dataset including name, email, start date, buddy, and access links (Slack, GitHub, Jira, Notion). Acts as the single source of truth for all downstream systems ensuring consistent, error-free onboarding data. 🎫 Create Jira User Account Automatically creates a Jira account for the new employee using REST API calls. Includes email, display name, username, and product access (Jira Software). Removes the need for manual admin setup and ensures immediate access to project boards. ✅ Validate Jira Account Creation Success: Checks if the Jira API response contains a valid accountId. If successful → continues onboarding. If failed → logs error to Google Sheets. Ensures downstream steps don’t continue if Jira setup fails. 📊 Log Jira Provisioning Failures to Error Sheet Appends any account creation errors (duplicate emails, invalid permissions, or API issues) into an “error log sheet” in Google Sheets. Helps HR/IT monitor issues and manually resolve them. Guarantees no silent onboarding failures. 📋 Generate Notion Onboarding Checklist Creates a personalized Notion page titled “{Name} - Onboarding Checklist” that includes: Welcome message Access links (Slack, GitHub, Jira) Assigned buddy details Start date and status Optionally, embedded videos or docs Gives each new hire a structured hub to manage onboarding tasks independently. 🤖 AI-Generated Welcome Message Creator Uses GPT-4o (Azure OpenAI) to craft a friendly, motivational welcome message for the new employee. Incorporates name, buddy, and access details with emojis and warm tone. Ensures every message feels human and engaging — not robotic. 🧠 GPT-4o Language Model Configuration Configures the AI assistant persona for personalized onboarding messages. Ensures tone consistency, friendliness, and empathy across all communications. 🔗 Consolidate Onboarding Data Streams Merges data from Jira, Notion, and AI message generation into a single payload. This ensures the final email contains every onboarding element — access links, checklist URL, and the AI-generated message. 📧 Format Comprehensive Welcome Email Generates a complete HTML-formatted email with: Personalized greeting AI-generated welcome message Clickable links (Jira, Notion, Slack, GitHub) Buddy info and start date Designed for mobile responsiveness and branded presentation. 📬 Send Welcome Email to New Hire Sends the final welcome email to the employee’s inbox with the subject: “Welcome to Techdome, {Name}! 🎉” Includes all essential access information, links, and team introductions — ensuring the new hire starts strong on Day 1. 🧩 Prerequisites Jira Admin API credentials Notion API integration Gmail OAuth2 credentials Azure OpenAI (GPT-4o) access Google Sheets document for logging errors 💡 Key Benefits ✅ Fully automated new hire onboarding ✅ AI-generated personalized communications ✅ Real-time error logging for IT transparency ✅ Seamless integration across Jira, Notion, and Gmail ✅ Professional first-day experience with zero manual work 👥 Perfect For HR teams managing multiple onboardings IT admins automating access provisioning Startups scaling employee onboarding Organizations using Jira + Notion + Gmail stack

Description Candidate Engagement | Resume Screening | AI Voice Interviews | Applicant Insights This intelligent n8n workflow automates the process of extracting and scoring resumes received through a company career page, populating a Notion database with AI insights where the recruiter or hiring manager can automatically invite the applicant to an instant interview with an Elevenlabs AI voice agent. After the agent conducts the behavior-based interview, the workflow scores the overall interview against customizable evaluation criteria and updates the Notion database with AI insights about the applicant. AI Powered Resume Screening & Voice AI that interviews like a Recruiter! AI Insights in Notion dashboard Who is this for? HR teams, recruiters, and talent acquisition professionals This workflow is ideal for HR teams, recruiters, and talent acquisition professionals looking for a foundational, extensible framework to automate early stage recruiting. Whether you're exploring AI for the first time or scaling automation across your hiring process, this template provides a base for screening, interviewing, and tracking candidates—powered entirely by n8n, Elevenlabs, Notion, and LLM integrations. Be sure to consult State and Country regulations with respect to AI Compliance, AI Bias Audits, AI Risk Assessment, and disclosure requirements. What problem is this workflow solving? Manually screening resumes and conducting initial interviews slows down hiring. This template automates: Resume assessment against job description. Scheduling first and second round interviews. First-round AI-led behavioral interviews with AI scoring assessment. Centralized tracking of AI assessments in Notion. What this does This customizable tool, configured to manage 3 requisitions in parallel, automates the application process, resume screen, and first round behavioral interviews. Pre-screen Applicants with AI Immediately screens and scores applicant’s resume against the job description. The AI Agent generates a score and an AI assessment, adding both to the applicant's profile in Notion. Notion automatically notifies hiring manager when a resume receives a score of 8 or higher. Voice AI that Interviews like a Recruiter AI Voice agent adapts probing questions based on applicant’s response and intelligently dives deeper into skill and experience to assess answers against a scoring rubric for each question. AI Applicant Insights in Notion Get detailed post-interview AI analysis, including interview recordings and question-by-question scoring breakdowns to help identify who you should advance to the next stage in the process. AI insight provided in Notion ATS dashboard with drag and drop to advance top candidates to the next interview stage. How it works Link to Notion Template Notion Career Page: Notion Career Page published to web, can be integrated with your preferred job board posting system. Notion Job Posting: Gateway for applicants to apply to active requisitions with ‘Click to Apply’ button. Application Form: N8N webform embedded into Notion job posting captures applicant information and routes for AI processing. AI Agent evaluates resume against job description AI Agent evaluates resume against the job description, stored in Notion, and scores the applicant on a scale of 1 to 10, providing rationale for score. Creates ATS record in Notion with assessment and score Workflow creates the applicant record in the Notion ATS where Recruiters and Hiring Managers see applicants in a filtered view, sorted by AI generated resume score. Users can automatically advance applicants to the next step in process (AI Conversation interview) with drag and drop functionality. Invites applicant to an Instant AI Interview Dragging the applicant to AI Interview step in the Notion ATS dashboard triggers Notion automation that sends the applicant an email with a link to the Elevenlabs Conversation AI Agent. The AI Conversation Agent is provided with instructions on how to conduct the behavior-based interview, including probing questions, for the specific role. AI Conversation Agent Behavior Based Interview The email link resolves to an ElevenLabs AI Conversation agent that has been instructed to interview applicants using pre-defined interview questions, scoring rubric, job description, and company profile. The Elevenlabs agent assesses the applicant on a scale of 1 to 5 for each interview question and provides an overall assessment of the interview based on established evaluation criteria. Click to hear AI Voice Agent in action Example: Role: IT Support Analyst Mark: Elevenlabs AI Agent instructed to interview applicants for specific role Gemini: Google AI coached to answer questions as an IT Support Analyst being interviewed Updates Notion record with Interview Assessment and Score All results—including the conversation transcript, interview scores, and rationale for assessment are automatically added back to the applicant’s profile in Notion where the Hiring Manager can validate the AI assessment by skimming through the embedded audio file. AI Interview Overall Score: 1 to 5 based on response to all questions and probes. AI Agent confirms that it was able to evaluate the interview using the assigned rubric. AI Interview Criteria Score: Success/Failure based on response to individual interview questions. Invites applicant to second interview with Hiring Manager Dragging the applicant to the ‘Hiring Manager Interview’ step in the Notion ATS dashboard triggers a Notion automation that sends an email with a link to the Hiring Manager’s calendar scheduling solution. Configuration and Set Up Accounts & API Keys You wil need accounts and credentials for: n8n (hosted or self-hosted) Elevenlabs (for AI Conversation Agent) Gemini (for LLM model access) Google Drive (to back up applicant data) Calendly (to automate interview scheduling) Gmail (to automate interview scheduling) Data / Documents to implement Job Descriptions for each role Interview questions for each role Evaluation criteria for each interview question Notion Set Up Customize your Notion Career Page Link to Free Notion Template that enables workflow: Update Notion job description database -update job description(s) for each role -add interview questions to the job description database page in Notion -add evaluation criteria to the job description database page in Notion -edit each ‘Click to Apply’ button in the job description template so it resolves to the corresponding N8N 'Application Form' webform production URL (detail provided below) Notion Applicant Tracker In the Applicant Tracker database, update position titles, tab headings, in the custom database view (Notion) so it reflects the title of the position you are posting. Edit the filter for each tab so it matches the position title. Notion Email Automation Update Notion automation templates used to invite applicants to the AI Interview and Hiring Manager interview. Note: Trigger email automation by dragging applicant profile to the next Applicant Comm Status in the Applicant Tracker. AI Interview invite template: revise position title to reflect the title of the role you are posting; include the link to your Conversation AI Agent for that role in the email body. Note: each unique role will use an Elevenlabs AI conversation agent designed for that role. Hiring Manager Interview invite template: revise position title to reflect the title of the role you are posting; include the link to your Calendly page or similar solution provider to automate interview scheduling. N8N Configuration Workflow 1 Application Forms (3 Nodes - one for each job) Update the N8N form title and description to match the job description you configured in Notion. Confirm Job Code in Applicant Form node matches Job Code in Notion for that position. Edit the Form Response to customize the message you want displayed after applicant clicks submit. Upload CV - Google Drive Authenticate your Google Drive account and select the folder that will be used to store resumes Get Job Description - Notion Authenticate your Notion account and select your Career Page from the list of databases that contain your job descriptions. Applicant Data Backup - Google Sheet Create a Google Sheet where you will track applicant data for AI Compliance reporting requirements. Open the node in n8n and use the field names in the node as Google Sheet column headings. Workflow 2 Elevenlabs Web Hook (Node 1) Edit the Web Hook POST node and copy your production URL that is displayed in the Node. This URL is entered into the Elevenlabs AI Conversation Agent post-call webhook described below. AI Agent Authenticate your LLM model (Gemini in this example) and add your Notion database as a tool to pull the evaluation_criteria hosted in Notion for the specific role. Extract Audio Create an Elevenlabs API key for your conversation agent and enter that key as a json header for the Extract Audio node Upload Audio to Drive - Google Drive Authenticate your Google Drive account and select the folder that will be used to store the audio file. Elevenlabs Configuration Create an Elevenlabs account Create Conversation AI Agent Add First Message and Systems Prompt: Design your ‘First Message’ and ‘Systems Prompt’ that guides the AI agent conducting the interview. Tool Tip: provide instruction that limits the number of probes per interview question. Knowledge Base: Upload your role specific interview questions and job description, using the same text that is stored in your Notion Career page for the role. You can also add a document about your company and instruct the Elevenlabs agent to answer questions about culture, strategy, and company growth. Analysis: Evaluation Criteria: Add your evaluation criteria, less than 2000 characters, for each interview question / competency. Analysis: Data Collection: Add the following elements, using the exact character string represented below. phone_number_AI_screen "capture applicant's phone number provided at the start of the conversation and share this as a string, integers only." full_name "capture applicant's full name provided at the start of the conversation." Advanced: Max Duration Set the max duration for interview in seconds. The AI Agent will timeout at the max duration. Conversation AI Widget: Customize your AI Conversation Agent landing page, including the position tile and company name. AI Conversation Agent URL: Copy the AI Conversation Agent URL and add it to your Notion email template triggered by the AI Interview email automation. Use a custom AI Agent URL for each distinct job description. Enable your Elevenlabs Post-Call Webhook for your Conversation Agent: Log into your Elevenlabs account and go to Conversational AI Settings and click on Post-Call Web Hook. This is where you enter the production URL from the N8N Web Hook node (Workflow 2). This sends the AI Voice Agent output to your n8n workflow which feeds back to your Notion dashboard.

Who is this for Product managers, customer success teams, and small business owners who collect feedback via Google Forms and want automated sentiment analysis without manual review. Ideal for teams processing 10-100+ responses weekly. What this workflow does This workflow reads new Google Forms responses from a linked Google Sheets spreadsheet, sends them to Gemini AI for sentiment analysis and topic categorization, then writes results back to the sheet, logs weekly insights in a Notion database, and emails an HTML summary report to your team. Each response gets a sentiment label (positive, neutral, negative), a 1-10 score, a category tag, and a key theme extraction. How to set up Create a Google Form and link responses to a Google Sheet. Add four columns to the sheet: Processed, Sentiment, Category, Score. Connect your Google Sheets OAuth2 credential and select the responses sheet. Connect your Google Gemini API credential (requires a Google AI Studio API key). Create a Notion database with columns: Date, Total Responses, Positive Rate, Top Themes, Recommendation. Connect your Notion API credential. Connect your Gmail OAuth2 credential and set the recipient email address. Activate the workflow. Requirements Google Sheets OAuth2 credentials (linked to a Google Form) Google Gemini API key (Google AI Studio) Notion API integration token Gmail OAuth2 credentials How to customize Change the schedule trigger interval for more or less frequent analysis runs. Edit the AI prompt in the Analyze feedback node to add custom categories relevant to your product. Modify the email HTML template in the Parse results node to match your branding. Add a Slack notification node after the email for real-time team alerts.

Who’s it for Teams that monitor multiple news sources and want an automated, tagged, and prioritized briefing—PMM, PR/Comms, Sales/CS, founders, and research ops. What it does / How it works Each morning the workflow reads your RSS feeds, summarizes articles with an LLM, assigns tags from a maintained dictionary, saves structured records to Notion, and posts a concise Slack digest of top items. Core steps: Daily Morning Trigger → Workflow Configuration (Set) → Read RSS Feeds → Get Tag Dictionary → AI Summarizer and Tagger → Parse AI Output → Write to Notion Database → Sort by Priority → Top 3 Headlines → Format Slack Message → Post to Slack. How to set up Open Workflow Configuration (Set) and edit: rssFeeds (array of URLs), notionDatabaseId, slackChannel. Connect your own credentials in n8n for Notion, Slack, Google Sheets (if used for the tag dictionary), and your LLM provider. Adjust the trigger time in Daily Morning Trigger (e.g., weekdays at 09:00). Requirements n8n (Cloud or self-hosted) Slack app with chat:write to the target channel Notion database with properties: summary (rich_text), tags (multi_select), priority (number), url (url), publishedDate (date) Optional Google Sheet for the tag dictionary (or replace with another source) How to customize the workflow Scoring & selection: Change priority rules, increase “Top N” items, or sort by recency. Taxonomy: Extend the tag dictionary; refine the AI prompt for stricter tagging. Outputs: Post per-tag Slack threads, send DMs, or create Notion relations to initiatives. Sources: Add more feeds or mix in APIs/newsletters. Security: Do not hardcode API keys in HTTP nodes; keep credentials in n8n.

This n8n workflow orchestrates a powerful suite of AI Agents and automations to manage and optimize various aspects of an e-commerce operation, particularly for platforms like Shopify. It leverages Langchain AI Agents powered by OpenAI, along with a variety of integrated services, to handle customer support, product recommendations, abandoned cart recovery, inventory management, post-purchase engagement, review monitoring, marketing campaigns, and operational alerts. Tools & Services Used n8n:** Core automation and orchestration platform. Langchain AI Agents:** For intelligent decision-making, task execution, and natural language processing across multiple modules. OpenAI (e.g., GPT-4o Mini):** Powers the AI Agents and direct LLM calls for tasks like sentiment analysis and content generation. Shopify (Conceptual - requires specific API/Webhook setup):** For triggers (abandoned cart, order delivered) and actions (fetching products/inventory, creating discounts). Google Sheets:** Used as a data store for FAQs, logging low stock, review databases, and campaign outcomes. Slack:** For internal team notifications (escalations, low stock, negative reviews). Twilio (or similar SMS service):** For sending SMS alerts (cart recovery, restock notifications). Email (Generic SMTP/API):** For sending various emails (AI responses, recovery emails, review requests, campaign emails). Notion:** For logging customer interactions. HTTP Request Nodes:** For generic API interactions (fetching customer info, product search, CRM, campaign tracking). Webhook Nodes:** For receiving external triggers (incoming messages, product inquiries, review submissions, restock signals). Cron Nodes:** For scheduled tasks (hourly inventory checks, daily campaigns). Workflow Overview This workflow is a collection of interconnected sub-workflows, each designed to automate a specific e-commerce process: Customer Support & Escalation Handles incoming customer messages, attempts to answer with FAQs or order status using an AI Agent, and escalates to a human agent via Slack if necessary. Logs interactions to Notion. Product Inquiry & Recommendation Processes product inquiries, searches a product catalog, filters/sorts results, uses an AI Agent for selection refinement, and can build a product carousel for user response. Abandoned Cart Recovery Detects abandoned carts, fetches customer data, uses an AI Agent to strategize recovery (e.g., offer discounts), and sends follow-up communications via email/SMS. Inventory Management (Low Stock Alert) Periodically checks inventory levels, identifies low-stock items, uses an AI Agent to format reports, and notifies relevant teams via Slack/email, logging to Google Sheets. Post-Purchase Review Request After a set period post-delivery, an AI Agent drafts and initiates sending a personalized product review request email to the customer. Review Monitoring & Flagging Listens for new product reviews, uses an AI model for sentiment analysis, alerts a support team for negative reviews via Slack, and logs all reviews. Scheduled Marketing Campaigns Fetches target audiences, segments them, uses AI Agents to generate tailored email content, sends campaigns, tracks basic metrics, and employs another AI Agent to suggest campaign adjustments. Manual Restock Alert & Logging Allows triggering a restock notification via webhook, sends an SMS alert, and uses an LLM to log the event. Prerequisites Ensure you have active accounts and necessary API keys/credentials for: OpenAI Shopify (or your e-commerce platform API) Google Cloud (for Google Sheets API) Slack (Bot Token) Twilio (Account SID, Auth Token, From Number) Your Email Sending Service (SMTP details or API key) Notion (Integration Token) Any other external APIs used (e.g., CRM, Product Search, Customer Info, Campaign Tracking) How to Use This Template Step 1: Import the Template Open your n8n instance. Go to “Workflows” > “Create Workflow”. Click the three dots (…) > “Import from File”. Upload the downloaded JSON file of this workflow. Step 2: Configure Critical Nodes & Credentials This is the most crucial step. Systematically go through each of the 8 sections outlined in the Sticky Notes within the workflow and configure the relevant nodes: SECTION 1 (Customer Support):** Get FAQs Data (Google Sheets): Set sheetId to YOUR_SHEET_ID_HERE and configure Google API credentials. Lookup Order API (HTTP Request): Set url to YOUR_ORDER_LOOKUP_API_ENDPOINT_HERE. Notify Human Agent (Slack): Configure Slack API credentials and channel. Send AI Response to Customer (HTTP Request): Set url to YOUR_CUSTOMER_RESPONSE_API_ENDPOINT_HERE. Store to Notion (Notion): Set pageId (Database ID) to YOUR_NOTION_DATABASE_URL_OR_ID_HERE and Notion API credentials. SECTION 2 (Product Inquiry):** Search Products API (HTTP Request): Set url to YOUR_PRODUCT_SEARCH_API_ENDPOINT_HERE. Build Product Carousel (Function): Update YOUR_DEFAULT_PRODUCT_IMAGE_URL_HERE and YOUR_FALLBACK_PRODUCT_URL_HERE. Respond to User with Carousel (HTTP Request): Set url for sending carousel data. SECTION 3 (Abandoned Cart):** Detect Abandoned Cart (Shopify Trigger): Configure Shopify credentials and ensure the correct trigger event. Fetch Customer Info (HTTP Request): Set url to YOUR_CUSTOMER_INFO_API_ENDPOINT_HERE. Create Discount (if applicable) (Shopify): Configure Shopify credentials and review discount creation parameters. Send Recovery Email (HTTP Request/Email Send): Set email API endpoint or SMTP credentials. Send SMS Reminder (Twilio): Configure Twilio credentials and from number (YOUR_TWILIO_PHONE_NUMBER_HERE). SECTION 4 (Low Stock Alerts):** Fetch Inventory (Shopify): Configure Shopify credentials. Notify Slack (Low Stock) (Slack): Configure Slack API credentials and channel. Generate Email Report (Low Stock) (Email Send): Configure SMTP/email credentials and to address. Export to Sheets (Low Stock Log) (Google Sheets): Set sheetId to YOUR_INVENTORY_LOG_SHEET_ID_HERE and Google API credentials. SECTION 5 (Review Request):** Order Delivered Trigger (Shopify Trigger): Configure Shopify credentials. Fetch Customer Data (for Review) (HTTP Request): Set url to YOUR_CUSTOMER_INFO_API_ENDPOINT_HERE. DraftReviewRequestEmail (Tool): Update YOUR_PRODUCT_PAGE_URL_BASE_HERE and YOUR_WEBSITE_URL_HERE. Send Review Request Email (Email Send): Configure SMTP/email credentials. SECTION 6 (Review Monitoring):** OpenAI node (currently Assistant Create): IMPORTANT: For sentiment analysis, change this node type to @n8n/n8n-nodes-langchain.lmChatOpenAi. Then configure its prompt for sentiment analysis (e.g., System: "Analyze sentiment. Respond with positive, negative, or neutral." User: "Review: {{ $('Listen for Review Webhook').first().json.body.review_text }}"). Set OpenAI credentials. Notify Support Team (Negative Review) (Slack): Configure Slack API credentials and channel. Add Review to Database (Google Sheets): Set sheetId to YOUR_REVIEWS_DATABASE_SHEET_ID_HERE and Google API credentials. SECTION 7 (Marketing Campaigns):** Fetch Target Audience API (HTTP Request): Set url to YOUR_CRM_API_FOR_AUDIENCE_HERE. GenerateCampaignEmailVariant (Tool): Update YOUR_CAMPAIGN_LANDING_PAGE_HERE. Send Campaign Email (Email Send): Configure SMTP/email credentials. Track Campaign Metrics API (HTTP Request): Set url for YOUR_CAMPAIGN_TRACKING_API_ENDPOINT_HERE. Log Campaign Outcome & Adjustments (Google Sheets): Set sheetId to YOUR_CAMPAIGN_LOG_SHEET_ID_HERE and Google API credentials. SECTION 8 (Manual Restock):** Send SMS Alert (Restock) (Twilio): Configure Twilio credentials, from number (YOUR_TWILIO_PHONE_NUMBER_HERE), and to (WAREHOUSE_MANAGER_PHONE_NUMBER_HERE). OpenAI Chat Model (for Basic LLM Chain): Configure OpenAI credentials. Send restock Request Email1 (Email Send): Configure SMTP/email credentials and to address. Step 3: Implement Tool Logic Go into each @n8n/n8n-nodes-langchain.toolCode node (e.g., SearchFAQs, RefineProductSelection, DetermineDiscount, etc.). The current JavaScript is placeholder. You MUST replace this with actual JavaScript logic that performs the intended action for each tool, often by making API calls or processing data based on the agent's input. Step 4: Review AI Agent Prompts & Tool Connections Carefully review the systemMessage for each AI Agent node to ensure it accurately reflects its role and how it should use its tools. CRITICAL:** Verify the index for tools connected to each AI Agent. Each tool connected to a single agent must have a unique, sequential index (0, 1, 2, ...). AI Agent (ID cd71629d-... in your JSON): SearchFAQs tool should be index: 0, LookupOrderStatus tool should be index: 1. (Please double-check and correct the connection indices in your actual workflow file if they are still both pointing to index 0). AI Agent6 (ID 4c24879b-... in your JSON): AnalyzeCampaignPerformance tool should be index: 0, SuggestCampaignAdjustments tool should be index: 1. (Please double-check and correct the connection indices in your actual workflow file if they are still both pointing to index 0). Initial Test Run Disable most of the workflow sections initially. Focus on one section at a time (e.g., Section 1: Customer Support). Manually trigger the first node (e.g., simulate an incoming webhook). Execute node by node, checking the output and debugging configurations and tool logic. For time-based triggers (Cron, Wait nodes), temporarily shorten the durations for faster testing. Once a section is working, move to the next. Use Cases E-commerce Businesses (Shopify, etc.):** To automate customer service, marketing, sales recovery, and operations. Digital Marketing Agencies:** To offer advanced automation services to e-commerce clients. Freelancers & Consultants:** To build and deploy sophisticated AI-driven e-commerce solutions. n8n Developers:** As a comprehensive template and learning resource for building complex multi-agent systems.

AI Twitter Content Machine – Write, Refine & Publish Tweets on Autopilot This workflow is perfect for creators, solopreneurs, and personal brands who want to consistently publish bold, high-performing content on X (Twitter) — without writing a single line themselves. After a one-time setup, it automatically generates tweet ideas, writes in your voice, evaluates post quality, avoids duplicates, and publishes directly to Twitter. All approvals and rewrites are handled in a conversational loop powered by OpenAI, Discord, and Google Sheets. Whether you’re building a personal brand or growing your startup audience, this tool will help you stay active, edgy, and relevant — with zero friction. How it works Distill what your flow does in a few high-level steps. Loads your brand brief from a sub-workflow. Generates a tweet idea aligned with your tone. Checks Google Sheets to ensure the idea hasn’t been used. Writes the post. Evaluates it using a feedback sub-workflow — if the quality score is below 0.7, it rewrites the post. Refines tone and voice using a Rewriter Agent that mimics your past content (from a Google Sheet). Sends the final post to a Discord channel for manual approval. On approval, posts directly to Twitter (X) and logs it to Google Sheets (History and Examples tabs). Set up steps Give users an idea of how long setup will take. Don’t describe every detail. Keep detailed descriptions in sticky notes inside your workflow. Key benefits No burnout, no block – Stop spending energy thinking what to tweet. AI handles everything. Style-matching – Posts sound like you, not a generic robot. Based on your real writing. Fast & scalable – Publish once or five times a day — it’s up to you. Avoid duplicates – Each idea is checked against your post history. Human-in-the-loop – You approve final posts via Discord. No rogue tweets. Integrations required n8n OpenAI API Google Sheets Twitter (OAuth2) Discord (for approval) Notion (optional for brand brief storage)

How it works: This template turns rows in a Google Sheet into polished newsletter drafts in Notion using an AI writing agent. You click Execute workflow in n8n. It fetches all rows marked N8n Status = Pending, generates a draft from Newsletter Title and About the Newsletter, creates a Notion page, writes the full draft, then flips the sheet row to Done before moving to the next one. Before you start (use your own credentials): Create and select your credentials in n8n: Google Sheets (OAuth2 or Service Account) with access to the target spreadsheet. Notion (Internal Integration) with access to the target database. OpenAI (API Key) for the Chat Model. Replace any placeholders in nodes: Spreadsheet ID/URL and sheet/tab name (e.g., newsletter). Notion Database ID / Parent and any page or block IDs used by HTTP Request nodes. OpenAI model name if you prefer a different model. Give the Notion integration access to the database (Share → Invite the integration). Do not hard-code secrets in nodes. Store them in n8n Credentials. Step-by-step: Manual Trigger Start the run with When clicking ‘Execute workflow’. Fetch pending input (Google Sheets → Get row(s) in sheet) Read the newsletter tab and pull only rows where N8n Status = Pending. Iterate (Split In Batches → Loop Over Items) Process one sheet row at a time for stable memory use and pacing. Generate the newsletter (AI Agent + OpenAI Chat Model) AI Agent loads the “System Role Instructions” that define style, sections, and format. Pass Newsletter Title and About the Newsletter to the OpenAI Chat Model to produce the draft. Create a Notion page (Notion → Create Page) Create a page in your Newsletter Automation database with the page title set from Newsletter Title. Prepare long content for Notion (Code) Split the AI output into \~1,800-character chunks and wrap as Notion paragraph blocks to avoid payload limits. Write content blocks to Notion (HTTP Request → UpdateNotionBlock) Send a PATCH request to append all generated blocks so the full draft appears on the page. Mark the sheet row as done (Google Sheets → Update row in sheet) Update N8n Status = Done for the processed Newsletter Title. Continue the loop Return to Split In Batches for the next pending row until none remain. Tools integration: Google Sheets** — input queue and status tracking (Pending → Done) OpenAI** — LLM that writes the draft from provided fields Notion** — destination database for each draft page n8n Code + HTTP Request** — chunking and Notion API block updates Want auto-runs? Add a Cron trigger before step 2 and keep the flow unchanged.

AI Social Media Content Automation – n8n Workflow This workflow is built for creators, solopreneurs, SaaS founders, and agencies looking to automate their social media content process from idea to publication. It combines the power of OpenAI, Google Sheets, and official APIs for Instagram, Facebook, X (Twitter), and LinkedIn to deliver fully automated, brand-consistent social media posts — including text, images, hashtags, CTAs, and scheduling. No more switching tools, rewriting content, or forgetting to post. Just set it up once and let your brand grow automatically. 🔧 What the Workflow Does Generates platform-specific post ideas based on your brand tone. Selects the best idea (or lets you manually input one). Writes tailored posts for Instagram, Facebook, X, and LinkedIn. Auto-generates platform-specific visuals using OpenAI (DALL·E) and uploads to Cloudinary. Publishes content directly using official platform APIs. Logs all actions to Google Sheets and optionally sends a summary email via Gmail. ⚙️ How It Works Trigger the workflow manually, on a schedule, or from a chatbot. AI generates multiple post ideas and filters the best one. Based on the selected idea, it generates full posts for each platform. Custom visuals are created using OpenAI and uploaded to Cloudinary. Final post content is merged and sent to Instagram, Facebook, X, and LinkedIn. Logs and optional reports are created in Google Sheets and Gmail. 🛠️ Setup Steps Set up your accounts and credentials: OpenAI, Cloudinary, Gmail, Meta, LinkedIn, X, and Google Sheets. Import the workflow and subworkflow (Get Brand Brief) into n8n. Replace all placeholders (sheet IDs, access tokens, profile/page IDs, brand brief URLs). Optionally personalize prompts and output templates to match your brand voice. Setup time: ~30–45 minutes (including credentials and testing). Detailed configuration notes are included in sticky nodes throughout the workflow. 📦 Included in Your Package JSON workflow file (main flow + brand brief subflow) Google Sheets templates for history logging Setup documentation (Markdown & PDF) Placeholder reference sheet

🚀 AI Blog & Social Media Publisher – Fully Automated Workflow This workflow is ideal for individuals, marketers, agencies, and brands who want to effortlessly automate the entire blogging and social media process—from idea generation to promotion. Its primary goal is to consistently deliver engaging, SEO-optimized blog posts directly to WordPress, accompanied by professionally crafted social media content ready for Instagram, Facebook, and X (Twitter). No writers, editors, designers, or social media managers required. Save countless hours and resources while boosting your brand's online presence. 🔧 Workflow Capabilities: -Automated Blog Topic Generation: Instantly generates unique, high-value blog ideas tailored to your brand. -SEO Content Creation: Produces comprehensive, 2000–2500 word articles optimized for search engines. -Real-Time Research: Integrates Perplexity AI to ensure factually accurate, authoritative content. -Visual Content Generation: Creates custom, AI-generated featured images via GPT-4, with automatic fallback to Pexels. -WordPress Publishing: Automatically publishes articles directly to WordPress with complete formatting (HTML), meta descriptions, featured images, and proper categorization. -Social Media Automation: Generates and schedules engaging, platform-specific posts for Instagram, Facebook, and X, complete with relevant hashtags, calls-to-action, and links. -Detailed Logging & Reporting: Logs every step transparently into Google Sheets and optionally sends publication reports to Gmail. ⚙️ How It Works: When activated, the workflow checks your content calendar in Google Sheets to avoid duplicate topics. It generates fresh, brand-aligned blog ideas, conducts live research, and creates complete, ready-to-publish articles. It then automatically designs and sources appropriate visuals, publishes content seamlessly to WordPress, and prepares engaging social media posts optimized for each platform. 🛠️ Easy Setup Steps: -Connect your APIs: OpenAI, WordPress, Google Sheets, Gmail, and optionally Pexels. -Replace placeholders (WordPress URLs, Google Sheets ID/tab, workflow IDs). -Customize AI prompts with your brand’s tone, keywords, and CTAs for personalized content. -Configure scheduling to automate daily, weekly, or custom publishing intervals. 📌 Additional Features: -Modular workflow design for easy customization and scalability. -Comprehensive Markdown and PDF setup guides included. -Bonus: Reference placeholders and quick-edit Sticky Notes for effortless adjustments. Launch today. Automate permanently. Amplify your reach effortlessly.

Who is this for? This is for marketers, educators, HR teams, startups, and freelancers who use Google Forms to collect information and want to automatically send it to Notion while emailing the respondent. What problem does it solve? Manual data entry from Google Forms into CRMs is time-consuming. This template eliminates that, ensuring leads are captured in your Notion database in real time and respondents are notified instantly — improving speed and accuracy. What this workflow does? Node 1 – Google Sheets Trigger**: Listens for new rows in the spreadsheet connected to your Google Form. Node 2 – Notion**: Creates a new entry in your CRM-style Notion database. Node 3 – Gmail**: Sends a confirmation email to the person who filled the form. 🛠 Setup Guide Prepare Google Form and Sheets Create your Google Form. Connect it to a Google Sheet (Responses tab > "Link to Sheets"). n8n - Google Sheets Trigger Setup Add Google Sheets Trigger node. Authentication: Use OAuth2 (preferred). Select your spreadsheet and worksheet. Trigger type: On new row (not "updated"). n8n - Notion Node Add Notion node (action: "Create Page"). Connect your Notion integration: In Notion, create a new integration and copy the token. Share your CRM database with that integration. In the node, map form responses to your database properties: e.g., Name → Title, Email → Email, etc. Use {{$json["Full Name"]}} for mapped fields. Common error: Check Notion property types (email must be set to type: email). n8n - Gmail Node (Optional Auto Reply) Add Gmail node (action: "Send Email"). Auth: OAuth2 with your Gmail account. To: {{$json["Email Address"]}} Subject: "Thanks for contacting us!" Body: Hi {{$json["Full Name"]}}, Thanks for reaching out via the form. We’ve received your info and will follow up soon! 🧩 How to Customize Replace Gmail with Outlook or SendGrid if needed. Map more fields into Notion like phone, tags, etc. Add Slack or Discord notifications for internal alerts. 🧾 SEO Optimized Title Suggestions Auto-sync Google Forms with Notion CRM and send a confirmation email Add Google Form leads to Notion and auto-send thank-you email via Gmail 📎 Required Permissions / Dependencies Google Sheets and Gmail authenticated in n8n Notion integration shared with your CRM database Enable “Impersonate User” if using Google Service Account

AI Blog Publisher – Automated Blog Content Workflow This workflow is designed for individuals and teams who regularly publish content on their blog and want to automate the entire process from start to finish. Its main goal is to generate long-form, SEO-optimized blog posts and publish them directly to WordPress — without needing a copywriter, editor, or someone to handle CMS uploads. The workflow generates a topic, writes a full article based on your brand guidelines, pulls a featured image from Pexels, publishes the post to WordPress, and logs the publication details to Google Sheets, creating a complete archive of published content. This allows users to deliver high-quality, search-optimized content every day while saving significant time. The whole process — from idea to publication — runs fully automatically and can be scheduled to execute without any manual input. It works just as well for solo creators as for marketing teams or agencies producing content at scale. How it works When triggered, the workflow generates a new blog post idea and checks your Google Sheet to see if the topic has already been published. If the topic is unique, it calls a sub-workflow that contains your brand’s writing style, tone, and blog goals. It then uses Perplexity AI to gather supporting research and context. Based on all this input, a complete 2000–2500 word article is generated in clean HTML, ready for WordPress. The workflow then searches Pexels for a relevant image and sets it as the featured image. Finally, it publishes the post to WordPress, including the proper title, meta description, and category. All relevant data — such as title, link, and publish date — is logged in your Google Sheet. How to set up To get this workflow running, all you need to do is connect the required APIs — OpenAI, WordPress, Google Sheets, and Pexels — and make a few basic adjustments. Replace the placeholder URLs in the HTTP request nodes with your actual WordPress address. In the Google Sheets nodes, add your own spreadsheet ID and tab name. In the node that fetches brand data, insert the workflow ID of your brand brief sub-workflow. You can also personalize the AI prompts by entering your blog name, company name, and a call-to-action to give the content a more tailored voice. Once that’s done, you can trigger the workflow manually or schedule it using the Schedule Trigger node.

Automatically store Retell transcripts in Google Sheets/Airtable/Notion from webhook Overview This workflow stores the results of a Retell voice call (transcript, analysis, etc.) once it has ended and been analyzed. It listens for call_analyzed webhook events from Retell and stores the data in Airtable, Google Sheets, and Notion (choose based on your stack). Useful for anyone building Retell agents who want to keep a detailed history of analyzed calls in structured tools. Who is it for For builders of Retell's Voice Agents who want to store call history and essential analytic data. Prerequisites Have a Retell AI Account Create a Retell agent Associate a phone number with your Retell agent Set up one of the following: An Airtable base and table (example: "Transcripts") A Google Sheet with a “Transcripts” tab A Notion database with columns to match the transcript fields Templates: Airtable Google Sheets Notion How it works Receives a webhook POST request from Retell when a call has been analyzed. Filters out any event that is not call_analyzed (Retell sends webhooks for call_started, call_ended and call_analyzed) Extracts useful fields like: Call ID, start/end time, duration, total cost Transcript, summary, sentiment Stores this data in your preferred tool: Airtable Google Sheets Notion How to use it Copy the webhook URL (e.g., https://your-instance.app.n8n.cloud/webhook/poc-retell-analysis) and paste it in your Retell agent under "Webhook settings" then "Agent Level Webhook URL". Make sure your Airtable, Google Sheet, or Notion databases are correctly configured to receive the fields. After each call, once Retell finishes the analysis, this workflow will automatically log the results. Extension If you use any "Post-Call Analysis" fields, you can add columns to your Airtable, Google Sheet, or Notion database. Then fetch the data from the call.call_analysis.custom_analysis_data object. Additional Notes Phone numbers are extracted depending on the call direction (from_number or to_number). Cost is converted from cents to dollars before saving. Dates are converted from timestamps to local ISO strings. You can remove any of the outputs (Airtable, Google Sheets, Notion) if you're only using one. 👉 Reach out to us if you're interested in analysing your Retell Agent conversations.

Who is this for? This template is perfect for Gumroad creators, solopreneurs, digital product sellers, and freelancers who want to track and thank customers automatically — without spending time on manual work. What problem does this solve? Every sale is a moment to build trust. But manually checking your inbox for new orders, logging clients, and remembering to send a thank-you note? It’s time-consuming and inconsistent. This workflow handles it all: From sale → to sheet → to ping → to personalized “thank you” — all fully automated. What this workflow does: ✅ Triggers on each new sale on Gumroad 📋 Extracts buyer details, amount paid, and product purchased 📈 Logs the sale to a Google Sheet for tracking 📲 Sends a Telegram approval message to notify you 💌 (Optional) Sends a Gmail thank-you email to the buyer 🔁 Keeps your workflow organized with color-coded notes and sample data ⚙️ Setup Instructions: Create Gumroad API and connect the trigger node Authenticate with Google Sheets to store each client Connect your Telegram bot for real-time alerts (Optional) Setup Gmail API for sending thank-you emails Customize the email copy & sheet headers (e.g. % cut, timestamps) 🗒 Color-coded workflow notes: To make customization smooth, the workflow includes a color-coded sticky note system: 🟩 Green Notes – Main building blocks (trigger, logging, ping, email) 🟦 Blue Notes – Setup guidance and editable fields (e.g. your email or brand name) 🟨 Yellow Notes – Optional upgrades (e.g. swap Gmail, use AI email generator, change to WhatsApp) Each step has comments or hints to make your setup easy — whether you're new to n8n or a seasoned automator. 🔧 How to customize this workflow? 🎯 Swap Gmail with Outlook, SMTP, or Mailgun 🤖 Use AI (e.g. OpenAI or Claude) to draft personalized emails dynamically 📞 Replace Telegram with WhatsApp, Discord, or Slack 🗃️ Log to Airtable or Notion instead of Google Sheets 🧠 Add approval logic or advanced tagging in Gmail 🧾 Licensing & Support This template is built by Velebit from Innovatio. External links (Gumroad store or support email) are included in the notes for optional help and upgrades. A separate license applies to the paid version on Gumroad, which includes additional modules and commercial use rights. 📩 Support & customization: [email protected]

CallForge - AI Gong Sales Call Processor Streamline your sales call analysis with CallForge, an automated workflow that extracts, enriches, and refines Gong.io call data for AI-driven insights. Who is This For? This workflow is designed for: ✅ Sales teams looking to automate sales call insights. ✅ Revenue operations (RevOps) professionals optimizing call data processing. ✅ Businesses using Gong.io to analyze and enhance sales call transcripts. What Problem Does This Workflow Solve? Manually analyzing sales calls is time-consuming and prone to inconsistencies. While Gong provides raw call data, interpreting these conversations and improving AI-generated summaries can be challenging. With CallForge, you can: ✔️ Automate transcript extraction from Gong.io. ✔️ Enhance AI insights by adding product and competitor data. ✔️ Reduce errors from AI-generated summaries by correcting mispronunciations. ✔️ Eliminate duplicate calls to prevent redundant processing. What This Workflow Does Extracts Gong Call Data Retrieves call recordings, metadata, meeting links, and duration from Gong. Removes Duplicate Entries Queries Notion** to ensure that already processed calls are not duplicated. Enriches Call Data Fetches integration details** from Google Sheets. Retrieves competitor insights** from Notion. Merges data** to provide AI with a more comprehensive context. Prepares AI-Friendly Transcripts Cleans up transcripts** for structured AI processing. Reduces prompt complexity** for more accurate OpenAI outputs. Sends Processed Data to an AI Call Processor Delivers the cleaned and enriched transcript** to an AI-powered workflow for generating structured call summaries. How to Set Up This Workflow Connect Your APIs 🔹 Gong API Access – Set up your Gong API credentials in n8n. 🔹 Google Sheets Credentials – Provide API access for retrieving integration data. 🔹 Notion API Setup – Connect Notion to fetch competitor insights and store processed data. 🔹 AI Processing Workflow – Ensure an OpenAI-powered workflow is in place for structured summaries. CallForge - 01 - Filter Gong Calls Synced to Salesforce by Opportunity Stage CallForge - 02 - Prep Gong Calls with Sheets & Notion for AI Summarization CallForge - 03 - Gong Transcript Processor and Salesforce Enricher CallForge - 04 - AI Workflow for Gong.io Sales Calls CallForge - 05 - Gong.io Call Analysis with Azure AI & CRM Sync CallForge - 06 - Automate Sales Insights with Gong.io, Notion & AI CallForge - 07 - AI Marketing Data Processing with Gong & Notion CallForge - 08 - AI Product Insights from Sales Calls with Notion Customize to Fit Your Needs 💡 Modify Data Sources – Update connections if using a different CRM, database, or analytics tool. 💡 Adjust AI Processing Logic – Optimize transcript formatting based on your preferred AI model. 💡 Expand Data Enrichment – Integrate CRM data, industry benchmarks, or other insights. Why Use CallForge? By automating Gong call processing, CallForge empowers sales teams to: 📈 Gain valuable AI-driven insights from calls. ⚡ Speed up decision-making with cleaner, structured data. 🛠 Improve sales strategies based on enriched, accurate transcripts. 🚀 Start automating your Gong call analysis today!

WhatsApp AI Chatbot with Evolution API + Notion CRM What this template does This workflow turns your WhatsApp Business number into a 24/7 AI-powered customer assistant — without any third-party chatbot platform. It receives incoming WhatsApp messages via Evolution API, understands the customer's intent, generates a conversational response using Claude AI, and sends it back — all within seconds. When the conversation requires human attention, the bot alerts you on Telegram and automatically pauses itself for that contact in your Notion CRM so you can take over seamlessly. This is a production-ready workflow built to handle real inbound traffic. It has been tested with cold outreach leads, inbound inquiries, and voice messages. Key features Multi-modal input Handles both text messages and voice notes. Voice messages are transcribed via OpenAI Whisper before being processed by the AI. Smart auto-reply filter A Sentiment Analysis node detects automatic replies (out-of-office bots, delivery confirmations) and silently discards them before the AI agent triggers — preventing the bot from responding to other bots. Notion CRM integration Every incoming message is matched against your Notion database by phone number. Known leads get their status updated. New contacts are created automatically. The bot also checks a WA ChatBot Status field (Active/Paused) before responding — so you can pause the bot per contact directly from Notion. Outreach-aware responses If you use WhatsApp for cold outreach (paired with an outreach workflow), this bot reads the lead's personalization_note and pain_point from Notion and uses them to personalize replies. The AI knows who contacted whom first and adjusts its tone accordingly. Human-in-the-loop escalation When the AI detects buying intent, frustration, or a request it cannot handle, it: Sends a full-context alert to your Telegram Sets WA ChatBot Status = Paused in Notion for that lead Stops auto-replying until you manually re-activate it Dynamic knowledge base (Google Sheets) Business info, products/services, and FAQs live in a Google Sheet with 3 tabs. Update your sheet — the bot adapts instantly. No redeployment needed. Format Cleaner AI responses are automatically stripped of markdown before sending (WhatsApp renders bold as literal asterisks — this node fixes that). Conversation memory Uses n8n's buffer window memory with phone number as session key. Remembers the last 10 message exchanges per contact. How it works WhatsApp Message ↓ Evolution API Webhook ↓ Detect Message Type (normalize payload) ↓ Skip Event? (groups, fromMe, empty text) → skip silently ↓ Is Voice? → Prepare Audio → Transcribe (Whisper) ↓ Sentiment Analysis → Automatic Reply? → skip silently ↓ Check Leads (Notion DB lookup by phone) ↓ Normalize & Match → is_known_lead, bot_status, outreach context ↓ Bot Status = Paused? → skip silently ↓ Information Extractor (intent, reply_sentiment, urgency, needs_human) ↓ Read Business Info + Products + FAQs (Google Sheets) ↓ Build Context (combines KB + lead context) ↓ Wait 10s (avoids responding before user finishes typing) ↓ Generate Response (Claude Haiku, conversation memory) ↓ Format Cleaner (strip markdown) ↓ Send WhatsApp Reply (Evolution API) ↓ Format for Log → Log Conversation (Google Sheets) ↓ Alert Owner? → IF needs_human: → Telegram alert → Pause ChatBot (Notion update: WA ChatBot Status = Paused) ↓ Phone Match (known lead?) → Update Lead Status (Last Contact + WA Status) → Create New Lead (if new contact) ↓ Respond 200 OK What you need Infrastructure Evolution API** (self-hosted or cloud) — WhatsApp messaging layer n8n** (self-hosted or cloud) — this workflow runs here Credentials (configure in n8n) | Credential | Used for | |---|---| | Anthropic API | Information Extractor + Response Generation (Claude Haiku) | | OpenAI API | Voice transcription (Whisper) — optional if no audio support needed | | Google Sheets OAuth2 | Knowledge base reads + conversation log | | Notion API | Lead lookup, BotStatus check, lead update/create | | Telegram Bot | Human-in-the-loop alerts | Google Sheets — 4 tabs required Copy the template sheet and fill in your data: Get your FREE Sheets Template Business_Info (columns: business_info, value) Rows: business_name, business_description, website, email, hours, coverage_area, booking_url, response_tone Products (columns: product_id, name, description, category, available, highlight) FAQs (columns: question, answer, category) Conversation_Log (columns: timestamp, channel, user_id, username, user_name, message_type, message, response, intent, needs_human) Notion Database — required fields | Field | Type | |---|---| | Name (title) | Title | | Phone | Phone number | | Status | Status | | WA ChatBot Status | Select (options: Active, Paused) | | WA Status | Select (options: Positive Reply, Negative Reply, Neutral Reply) | | Lead Source | Select | | Last Contact | Date | | Personalization Note | Rich text | | Pain Point | Rich text | > 💡 A ready-to-use Notion CRM template pre-configured for this workflow is available separately. Setup steps Import this workflow into your n8n instance Configure credentials for all 5 services listed above Create your Google Sheet with the 4 required tabs and fill in your business data Set up your Notion database with the required fields (or purchase the pre-built Notion template Get Notion Template ) Update the Evolution API URL in the Send WhatsApp Reply node: https://YOUR-EVOLUTION-DOMAIN/message/sendText/YOUR-INSTANCE-NAME Add your Evolution API key to the Send WhatsApp Reply node header Configure your Telegram Chat ID in the Alert Owner node (send a message to @userinfobot to get your ID) Register the webhook in Evolution Manager: URL = https://YOUR-N8N-URL/webhook/evo-inbound, events: MESSAGES_UPSERT + CONNECTION_UPDATE, Base64: ON, webhookByEvents: OFF Activate the workflow Test by sending a WhatsApp message to your number Customizing the AI The system prompt in the Generate Response node is where you define your bot's personality and conversation rules. It already includes: Role and business context (pulled dynamically from your Sheets) Formatting rules (no markdown, WhatsApp-friendly style) One-idea-per-message conversation discipline Outreach context awareness Pricing and booking redirect logic Negative sentiment handling (polite close, no insistence) Handoff escalation triggers Edit it to match your industry, tone, and specific business logic. Compatible with outreach workflows This chatbot is designed to work as the inbound layer of a complete WhatsApp automation stack: Outreach Workflow** — sends cold outreach messages and writes lead data to Notion Follow-up Workflow** — sends follow-up sequences to non-responders This Chatbot** — handles inbound replies intelligently using the outreach context from Notion When all three are connected, your entire WhatsApp funnel runs on autopilot. Notes The Check Leads node fetches all leads with a phone number from Notion and matches in JavaScript. This works well for databases up to ~1,000 leads. For larger CRMs, consider filtering by phone number directly in the Notion query. Voice message transcription requires OpenAI Whisper. If you don't need audio support, you can disable the Is Voice? branch entirely. The 10-second Wait node before response generation reduces the chance of sending a reply while the user is still typing. Adjust or remove it based on your needs. About the creator Mark Cifral — System Sales Engineer turned automation founder. I build production-grade n8n workflows for B2B lead enrichment, WhatsApp AI agents, and proposal automation. Founder @ Cifral Solutions (cifral.io).

Description Paste any webinar, training, or lecture recording URL into a simple form along with the title, speaker name, topic category, and date and the workflow builds your knowledge base automatically. WayinVideo transcribes the full session with speaker labels and timestamps, then GPT-4o-mini identifies 3 to 8 distinct topics covered and writes a complete structured page for each one — summary, key insights, action items, notable quotes, timestamps, and tags. One Notion page is created per topic and every page is logged to Google Sheets with its Notion URL for easy team access. Built for teams, educators, consultants, and agencies who want a searchable knowledge base from every webinar without watching recordings or taking notes manually. What This Workflow Does Transcribes webinars with speaker labels** — WayinVideo processes the full session and returns every segment attributed to the correct speaker with timestamps, giving GPT full context Identifies 3 to 8 distinct topics automatically** — GPT-4o-mini reads the transcript and determines how many meaningful topics were covered — no manual segmentation needed Writes a complete knowledge page per topic** — Each topic gets a summary, up to five key insights, action items with checkboxes, notable quotes, timestamp range, and relevant tags Creates one Notion page per topic** — Each knowledge page is published directly to your Notion database with the webinar title and topic title as the page name Polls automatically until transcription is ready** — Waits 90 seconds then checks every 30 seconds until the transcript is available, with no manual monitoring required Logs every created page to Google Sheets** — Appends a row with the Notion page ID, Notion page URL, topic title, speaker, tags, and Status set to Published Saves all webinar metadata to every page** — Speaker name, webinar date, duration, target team, and recording URL are embedded in every Notion page for full context Setup Requirements Tools Needed n8n instance (self-hosted or cloud) WayinVideo account with API access OpenAI account with GPT-4o-mini API access Notion account with a connected database Google Sheets (one sheet with a tab named Knowledge Base Log) Credentials Required WayinVideo API key (pasted into 2. WayinVideo — Submit Transcription and 4. WayinVideo — Get Transcript Results) OpenAI API key Notion OAuth credential Google Sheets OAuth2 > ⚠️ WayinVideo API key appears in 2 steps — replace YOUR_WAYINVIDEO_API_KEY in both 2. WayinVideo — Submit Transcription and 4. WayinVideo — Get Transcript Results. Missing either one will cause the workflow to fail. Estimated Setup Time: 20–25 minutes Step-by-Step Setup Import the workflow — Open n8n → Workflows → Import from JSON → paste the workflow JSON → click Import Get your WayinVideo API key — Log in to your WayinVideo account → go to Account Settings → copy your API key Add your WayinVideo API key to node 2 — Open node 2. WayinVideo — Submit Transcription → find the Authorization header value Bearer YOUR_WAYINVIDEO_API_KEY → replace YOUR_WAYINVIDEO_API_KEY with your actual key Add your WayinVideo API key to node 4 — Open node 4. WayinVideo — Get Transcript Results → find the same Authorization header → replace YOUR_WAYINVIDEO_API_KEY with the same key Connect OpenAI — Open node 9. OpenAI — GPT-4o-mini Model → click the credential dropdown → add your OpenAI API key → test the connection Set up your Notion database — In Notion, create a database (or use an existing one) where the knowledge pages will be created → open the database in a browser → copy the database ID from the URL (the 32-character string after your workspace name and before the ?) Connect Notion — Open node 11. Notion — Create Topic Page → click the credential dropdown → add Notion OAuth → complete the OAuth flow to authorize n8n access → in the pageId field, paste your Notion database URL or ID Create your Google Sheet tab — Open your Google Sheet → add a tab named exactly Knowledge Base Log → add these 10 column headers in row 1: Webinar Title, Topic Title, Speaker, Topic Category, Webinar Date, Notion Page ID, Notion Page URL, Tags, Created On, Status Connect Google Sheets — Open node 12. Google Sheets — Log Created Pages → click the document field → replace YOUR_GOOGLE_SHEET_LOG_ID by selecting your spreadsheet or entering the Sheet ID (the string between /d/ and /edit in your Sheet URL) → click the credential dropdown → add Google Sheets OAuth2 → authorize access Activate the workflow — Toggle the workflow to Active → copy the Form URL from node 1. Form — Webinar URL + Details → open it in a browser to submit your first webinar How It Works (Step by Step) Step 1 — Form: Webinar URL + Details You open the form URL in a browser and fill in six fields: the webinar or recording URL (Zoom, YouTube, Vimeo, or any direct link), the webinar title, the speaker or presenter name, the topic category (e.g. SEO, Marketing, AI), the webinar date, and optionally the target team or department. Submitting the form starts the workflow. Step 2 — HTTP: WayinVideo — Submit Transcription The webinar URL is sent to the WayinVideo transcription API with the target language set to English. WayinVideo accepts the job and returns a task ID confirming transcription has started. Step 3 — Wait: 90 Seconds The workflow pauses for 90 seconds before the first status check. This is longer than shorter video workflows because webinar recordings are typically 45–90 minutes and need more initial processing time. Step 4 — HTTP: WayinVideo — Get Transcript Results A GET request checks the WayinVideo results endpoint using the task ID from step 2. It returns the current processing status and, once complete, the full speaker-labeled transcript. Step 5 — IF: Transcription Complete? This is the polling gate. If the status equals SUCCEEDED (YES path), the transcript is ready and the workflow moves forward to formatting. If still processing (NO path), the workflow routes to 6. Wait — 30 Seconds Retry which pauses 30 seconds then loops back to step 4 to check again. This repeats until SUCCEEDED. Step 6 — Wait: 30 Seconds Retry When the transcript is not yet ready, the workflow waits 30 seconds then returns to step 4 for another check. The loop continues automatically. Step 7 — Code: Format Transcript Each segment is formatted as [Speaker Name | MM:SS] text. Total duration in minutes, word count, and unique speaker names are calculated. All form inputs — webinar title, speaker name, topic category, webinar date, target team, and recording URL — are packaged here for the AI prompt. Step 8 — AI Agent: Extract Knowledge Topics GPT-4o-mini receives the formatted transcript and a detailed system prompt. It identifies between 3 and 8 distinct topics from the webinar and for each topic returns a structured JSON object with: a 5–8 word topic title, a 2–3 sentence summary, up to five key insights, action items, notable quotes, an approximate timestamp range, and 2–4 tags. The output is a clean JSON array. GPT is instructed to write only from what was actually said in the transcript. Step 9 — OpenAI: GPT-4o-mini Model This is the language model powering the knowledge extraction. It runs with default settings for consistent, structured output. Step 10 — Code: Parse Topics and Build Notion Content The AI output JSON is cleaned (any accidental markdown backticks removed) and parsed. If parsing fails, the step throws a clear error. Each topic in the array is returned as an individual row. For each topic, a full Notion-ready markdown page is assembled with sections for Summary, Key Insights, Action Items (with checkbox syntax), Notable Quotes (in blockquote format), and Webinar Details. All webinar metadata is embedded in every page. Step 11 — Notion: Create Topic Page One Notion page is created per topic. The page title is formatted as "Webinar Title — Topic Title". The full markdown content built in step 10 is written into the page body. Notion returns the new page's ID and URL. Step 12 — Google Sheets: Log Created Pages After each Notion page is created, one row is appended to your Knowledge Base Log tab. The row includes webinar title, topic title, speaker, topic category, webinar date, the Notion page ID, the Notion page URL, the tags as a comma-separated string, the creation timestamp, and Status set to Published. Your team now has a direct link to every knowledge page from one sheet. Key Features ✅ 90-second initial wait for long recordings — The workflow uses a longer first pause suited to webinar-length content rather than short video clips ✅ 3 to 8 topics per webinar — auto-detected — GPT decides how many meaningful topics are present based on the actual content, not a fixed number ✅ Action items formatted as Notion checkboxes — Every action item is written with - [ ] syntax so they render as real checkboxes in Notion — ready to assign and complete ✅ Notable quotes in blockquote format — Speaker quotes are wrapped in Notion blockquote syntax so they visually stand out on the page ✅ Webinar metadata embedded in every page — Speaker, date, duration, target team, and recording URL are written into each page so the context is always visible without referencing a separate document ✅ Notion page URL logged immediately — Every page URL is saved to Google Sheets the moment it is created so your team can access any page directly without opening Notion ✅ JSON parsing with fallback protection — The code step strips any accidental markdown formatting from GPT output before parsing, reducing the chance of a JSON parse failure on well-formed responses Customisation Options Increase the maximum number of topics — In node 8. AI Agent — Extract Knowledge Topics, change "maximum 8 topics" in the system prompt to a higher number — useful for long full-day workshop recordings that cover more than 8 distinct areas. Add a Slack notification after all pages are created — After node 12. Google Sheets — Log Created Pages (on the last topic row), add a Slack step that posts the webinar title, number of pages created, and a link to your Knowledge Base Log sheet so your team is notified without checking Sheets. Filter which topics get a Notion page — After node 10. Code — Parse Topics and Build Notion Content, add an IF check that only proceeds to Notion creation if the number of key insights is 3 or more — skipping thin topics that GPT extracted with limited content. Add a Notion tag property — In node 11. Notion — Create Topic Page, add a multi-select property mapping that sends the tags array to a Tags property in your Notion database — making pages filterable and searchable by tag directly in Notion. Send a summary email after all pages are created — After node 12. Google Sheets — Log Created Pages (last row only), add a Gmail step that sends an email with the webinar title, number of pages created, and a direct link to the Knowledge Base Log sheet so the submitter gets a confirmation. Troubleshooting WayinVideo returning an error on submission: Confirm YOUR_WAYINVIDEO_API_KEY in node 2. WayinVideo — Submit Transcription is replaced with your actual API key — not the placeholder text Confirm the same replacement was made in node 4. WayinVideo — Get Transcript Results — both steps require the key Check the execution log of node 2 for the raw error — a 401 means wrong key, a 422 means the URL format is not supported by WayinVideo Workflow stuck in the polling loop: Check that the webinar URL is publicly accessible — Zoom recordings with password protection, private YouTube videos, or expired Zoom links will not be processed Open the execution log of node 4. WayinVideo — Get Transcript Results and check the raw response — WayinVideo may have returned a FAILED status with a specific error message Very long recordings (over 2 hours) may take longer than the polling loop can handle — consider increasing the retry wait from 30 to 60 seconds in node 6. Wait — 30 Seconds Retry GPT not returning valid JSON or extracting zero topics: Confirm the API key is connected in node 9. OpenAI — GPT-4o-mini Model and your account has available credits Check the execution log of node 8. AI Agent — Extract Knowledge Topics for the raw GPT output — the code step in node 10 will show a parse error with the first 200 characters of the bad output If GPT is consistently returning markdown-wrapped JSON (with backticks), node 10 strips these automatically — but if the output has additional explanation text before the array, the JSON extraction regex should still find it Notion pages not being created: Confirm the Notion OAuth credential in node 11. Notion — Create Topic Page is connected and that the integration has been added to the target database in Notion — go to your Notion database → three-dot menu → Add connections → find your n8n integration Confirm the pageId field in node 11 points to a valid Notion database URL — this must be a database, not a regular page Check the execution log of node 11 for the Notion API error — a 404 means the database ID is incorrect Google Sheets not logging rows: Confirm YOUR_GOOGLE_SHEET_LOG_ID in node 12. Google Sheets — Log Created Pages is replaced with your actual sheet ID from the URL Confirm the tab is named Knowledge Base Log exactly and all 10 column headers in row 1 match exactly Check that the Google Sheets OAuth2 credential is connected and not expired — re-authorize if needed Support Need help setting this up or want a custom version built for your team or agency? 📧 Email: [email protected] 🌐 Website: https://isawow.com/

Deliver your product updates in a modern, accessible format. This workflow automatically transforms GitHub releases into podcast-style audio announcements and distributes them via email and Slack. 🎯 What This Workflow Does This template bridges your development cycle with your marketing and communication channels. 🐙 Step 1 — GitHub Trigger & Notion Synthesis GitHub Trigger:** Fires when a new release is published Parsing:** Converts raw markdown into structured categories (features, fixes, improvements) Notion Merge:** Enriches data with additional context from your Notion changelog database 🎙️ Step 2 — AI Scriptwriting & Professional TTS Script Generation:** OpenAI converts technical notes into a conversational 60–90 sec script Voice Generation:** ElevenLabs turns the script into high-quality audio CDN Hosting:** Uploads MP3 via UploadToURL to generate a public URL 📧 Step 3 — Multimedia Newsletter Delivery Subscriber Fetch:** Loads email list from Google Sheets Email Creation:** Builds a rich HTML email with embedded audio player Distribution:** Sends via Gmail using BCC list 💬 Step 4 — Internal Sync & Database Update Slack Alert:** Posts update with audio preview to team channel Notion Update:** Marks entry as published and stores audio URL ✨ Key Features Bidirectional Notion Sync:** Reads and updates changelog entries Conversational AI:** Converts technical updates into human-friendly audio Dynamic HTML Emails:** Includes inline audio playback High-Quality Voice:** Uses ElevenLabs for realistic narration 🔧 Setup Requirements Required Integrations GitHub:** Personal Access Token (repo read scope) Notion:** Integration token + changelog database ElevenLabs:** API key + Voice ID OpenAI:** API key UploadToURL:** For MP3 hosting Slack:** Bot token Environment Variables NOTION_DATABASE_ID APPROVER_EMAIL DISCORD_WEBHOOK_URL SLACK_CHANNEL_ID Humanize your software updates. Import this template and start broadcasting your product journey with audio.

How it works This workflow monitors a Notion database for new or updated tasks and checks if the scheduled time is available in Google Calendar. It logs every task into Google Sheets for tracking and auditing. Based on availability, it either creates a calendar event or sends a conflict notification email. The workflow also updates the task status in Sheets to reflect success or failure. Step-by-step Trigger task updates from Notion** Get Task – Watches for new or updated tasks in the Notion database. Check Availability – Queries Google Calendar to check if the selected time slot is free. Log data and evaluate availability** Record – Stores task details in Google Sheets for tracking. If – Checks whether the time slot is available based on calendar results. Create calendar event if available** Create an event – Adds the task as an event in Google Calendar. Update Status – Marks the task as successfully scheduled in Google Sheets. Handle scheduling conflicts** Send Error – Sends an email notification about the calendar conflict. Update Status1 – Updates the task status as failed or unavailable in Google Sheets. Why use this? Prevents double-booking by checking calendar availability automatically Keeps a centralized log of all tasks and their scheduling status Sends instant alerts when scheduling conflicts occur Reduces manual effort in managing tasks across tools Improves visibility and reliability of task scheduling workflows

How it works This workflow triggers when a HubSpot deal stage changes to Closed Won and automatically generates an invoice. It collects deal and contact data, builds a styled invoice, converts it into a PDF, and sends it to the client. The system logs all invoices and alerts the team, then monitors payment status with automated reminders. If payment is delayed, it escalates the issue and handles errors separately. Step-by-step Trigger and data collection** HubSpot - Deal Trigger – Starts workflow on deal stage change. IF - Is Deal Closed Won? – Filters only Closed Won deals. HTTP - Get Deal Details – Fetches deal information. HTTP - Get Deal Associations – Retrieves linked contacts. Code - Extract Contact ID – Extracts and formats data. HTTP - Get Contact Details – Gets customer details. Invoice generation** Code - Build Invoice + HTML – Creates invoice data and HTML layout. Send and store invoice** HTTP - Generate PDF – Converts HTML into PDF. Google Sheets - Log Invoice – Stores invoice records. Notion - Create Invoice Record – Tracks invoice internally. Gmail - Send Invoice Email – Sends invoice to client. Slack - Invoice Sent Alert – Notifies team. Payment tracking and follow-up** Wait - 7 Day Payment Window – Waits before checking payment. HTTP - Recheck Deal Stage – Checks payment status. IF - Payment Received? – Branches based on payment. Gmail - Follow-up Email #1 – Sends reminder if unpaid. Wait - 5 More Days – Adds extra delay. HTTP - Final Payment Check – Verifies final status. Slack - Payment Confirmed – Confirms successful payment. Escalation handling** IF - Still Unpaid? (Escalate) – Detects overdue invoices. Slack - Escalation Alert – Alerts team for action. Notion - Flag as Overdue – Updates record status. Slack - Late Payment Confirmed – Handles delayed payments. Error handling (separate flow)** Error Trigger – Captures workflow failures. Slack - Workflow Error Alert – Sends error notification. Why use this? Fully automates invoicing from deal closure to payment tracking Reduces manual billing work and human errors Improves payment collection with automated reminders Provides clear visibility with logs and team alerts Ensures reliability with built-in error monitoring

Forecast sales trends and generate reports with Stripe, Sheets, and Gemini AI Who is this for Revenue operations teams, SaaS growth managers, and sales directors who need automated weekly insights from their Stripe payment data. Perfect for small to medium businesses tracking subscription revenue, one-time charges, and refund patterns without manual spreadsheet work. How it works Every Monday morning, the workflow pulls the previous week's charges, subscriptions, and refunds from Stripe's API. It merges this fresh data with historical sales records stored in Google Sheets, then calculates key metrics like week-over-week growth, moving averages, and MRR estimates. Google Gemini AI analyzes the compiled data to identify trends, predict next week's performance, and flag unusual revenue patterns. When significant changes are detected (20%+ variance), the system triggers targeted alerts through a separate Slack channel. All insights get logged to a Google Sheets history for tracking, while a comprehensive dashboard page updates automatically in Notion. The weekly summary posts to your main sales Slack channel, and executives receive detailed email reports with strategic recommendations. How to set up Configure Stripe API credentials with read access to charges, subscriptions, and refunds. Set up Google Sheets OAuth for both reading historical data and writing analysis logs. Create a Notion integration with page update permissions for your sales dashboard. Add Slack OAuth credentials for posting to your chosen sales and alerts channels. Configure Gmail SMTP for executive email delivery. Update the Configuration Settings node with your specific IDs, channels, and email addresses. Requirements Stripe account with API access Google Sheets with historical sales data Notion workspace for dashboard Slack workspace with posting permissions Gmail account for executive reports Google Gemini API access How to customize Adjust the anomaly detection threshold in the Calculate Trends code node (currently 50% variance triggers alerts). Modify the Slack message templates, email formatting, or add additional metrics to the Notion dashboard. Change the schedule trigger from weekly to daily or monthly based on your reporting needs.

Description This n8n template gives ecommerce brands a fully automated review intelligence system — running every morning to scrape, analyze, and report on what customers are actually saying across every platform. It uses MrScraper to collect reviews from Tokopedia, Shopee, Lazada, Bukalapak, Amazon, and more, then GPT-4o-mini to extract 15 brand intelligence signals per review including sentiment, emotion, viral risk, competitor mentions, and CS response suggestions. The result is a daily Brand Awareness Score (BAS) delivered to Slack, every review archived in Notion, and urgent alerts fired the moment a critical review is detected — before it goes viral. How It Works Phase 1 – Trigger & Config:** A Schedule Trigger fires daily at 6AM. The workflow reads your product list from Google Sheets — each row is one product SKU across any platform — and loops through them one by one. Phase 2 – Review URL Discovery:** For each product, the Map Agent crawls the product page and discovers review section URLs or paginated review pages. A smart fallback ensures reviews embedded directly on the product page (common on Tokopedia and Shopee) are still captured even when no separate review URL exists. Phase 3 – Review Extraction & Filtering:** Each review URL is processed by the General Agent, which extracts the full review text, star rating, reviewer name, date, photo count, helpful votes, verified purchase status, and any existing seller reply. Short reviews under 10 words are skipped — unless the rating is 1 or 2 stars, where even brief negative feedback is treated as a valuable signal. A deduplication hash is generated per review to prevent double-processing on re-runs. Phase 4 – AI Brand Sentiment Analysis:** Every valid review is sent to GPT-4o-mini with a structured prompt that returns 15 brand intelligence fields: sentiment label and score, emotion tags (frustration, delight, anger, loyalty, etc.), the most impacted product dimension (quality, delivery, packaging, pricing, authenticity), a CX score out of 10, competitor brand mentions, viral risk assessment, urgency level, and a ready-to-use customer service response suggestion. Phase 5 – Storage, Alerts & Daily Digest:** Reviews flagged as action-required trigger an immediate Slack alert to your #brand-alerts channel. Every review is saved to Notion with all 27 metadata fields. At the end of each run, a Daily Brand Health Digest is compiled — including the Brand Awareness Score (BAS) out of 100, sentiment breakdown, top praises and complaints, emotion trends, competitor mentions, viral risk list, and action items — then posted to your #brand-monitoring Slack channel. How to Set Up Prepare your Google Sheet with these columns: Platform, Product_URL, Brand_Name, SKU_Code, Category, Active (Y/N). Add one row per product SKU you want to monitor. Create 2 scrapers in your MrScraper account: Review List Scraper (Map Agent) — crawls product pages and discovers review URLs Review Detail Scraper (General Agent) — extracts review_text, rating, reviewer_name, review_date, photo_count, helpful_votes, verified_purchase, seller_reply Copy the scraperId for each and paste into the corresponding n8n nodes. Enable AI Scraper API access in your MrScraper account settings. Add your credentials in n8n: MrScraper API key OpenAI API key Slack OAuth Notion OAuth Google Sheets OAuth2 Configure your Notion database with all 27 properties listed in the setup note inside the workflow (Title, SKU Code, Platform, Sentiment, Sentiment Score, Emotion Tags, CX Score, Viral Risk, Action Required, and more). Update config values inside the Filter & Enrich Review Data node: slackChannel (e.g. #brand-monitoring) slackAlertChannel (e.g. #brand-alerts) notionDatabaseId (from your Notion database URL) competitorKeywords (comma-separated competitor brand names to detect) alertThreshold (default: 2.5 stars) Adjust the Map Agent node include/exclude patterns for your target platform (e.g. /review, /ulasan for Indonesian platforms, paginated review paths for Amazon). Set your trigger time in the Schedule node to match your timezone (default: every 24 hours). Requirements MrScraper** account with API access enabled OpenAI** account (GPT-4o-mini used by default) Slack** workspace with OAuth connected (two channels recommended: one for digest, one for urgent alerts) Notion** workspace with a database configured and OAuth connected Google Sheets** (OAuth2 connected) for your product SKU list Good to Know The Brand Awareness Score (BAS) is calculated using a weighted formula combining average star rating (30%), positive review rate (25%), sentiment score (20%), brand loyalty signals (10%), and a viral risk penalty (up to -10 points). It gives you a single number to track brand health over time. GPT-4o-mini processes each review for approximately $0.0001 — making it extremely cost-effective even for catalogs with hundreds of SKUs. Short 1–2 star reviews are never skipped, even if they contain only a few words — a single-word complaint like "rusak" (broken) or "fake" carries strong signal and is always analyzed. The workflow has two independent Slack outputs: an instant urgent alert fires the moment a critical review is detected, while the Daily Digest posts a full brand health report after all reviews for the day have been processed. Reviews from platforms where feedback is embedded on the product page (no separate review URL) are handled automatically via the smart URL fallback in the Extract Review URLs node. Customising This Workflow Multi-brand monitoring:** Duplicate the workflow and point it at a different Google Sheet to run separate brand intelligence pipelines for different product lines or client brands. Auto CS ticket creation:** Add a Jira, Asana, or Trello node after the Notion save step to automatically create customer service tickets for every critical or high-urgency review. Email reporting:** Insert a Gmail node after the Slack Daily Digest to also deliver the Brand Health Report as a formatted email to your marketing or brand team each morning. Visual dashboards:** Connect your Notion database to Google Looker Studio or Metabase to build BAS trend charts, sentiment heatmaps by platform, and weekly brand health dashboards. Competitor switch alerts:** Extend the competitor keyword list and add a dedicated Slack message branch specifically for reviews where a competitor switch is mentioned — a high-priority signal for retention teams.

Description This n8n template automatically monitors news sources daily, analyzes article sentiment using AI, and delivers structured intelligence reports to your team — all without any manual reading. It uses MrScraper to discover and extract articles, GPT-4o-mini to score sentiment and flag urgent issues, and delivers results to both Notion (for archiving) and Slack (for real-time alerts and daily digests). Whether you're tracking brand reputation, monitoring a competitor, or staying on top of industry trends, this workflow turns the open web into a fully automated radar system that runs every morning before your team starts their day. How It Works Phase 1 – Trigger & Config:** A Schedule Trigger fires daily at 8AM. The workflow reads your list of target news source URLs from a Google Sheet, then loops through each source one by one. Phase 2 – URL Discovery:** For each news source, the Map Agent crawls the page and extracts individual article URLs. URLs are filtered using include patterns to keep only actual article links, deduplicated, and capped at your configured maxArticles limit. Phase 3 – Article Extraction:** Each article URL is processed by the General Agent, which extracts the full content including title, body text, author, and publication date. Articles with fewer than 50 words or that don't mention your defined brand/topic keywords are automatically filtered out and skipped. Phase 4 – AI Sentiment Analysis:** Each relevant article is sent to GPT-4o-mini with a structured prompt. The model returns a complete JSON analysis including sentiment label (positive/neutral/negative), a sentiment score from -1 to 1, a 2–3 sentence summary, key topics, tone classification, the most impactful quote, and whether the article requires an urgent response. Phase 5 – Storage & Reporting:** Every analyzed article is saved as a page in your Notion database with full metadata. If an article is flagged as action-required, an immediate Slack alert is fired. At the end of each run, a Daily Digest is compiled with sentiment breakdowns, average scores, flagged items, and top article summaries — then posted to your Slack channel. How to Set Up Create 2 scrapers in your MrScraper account: Map Agent Scraper (for discovering article URLs from news pages) General Agent Scraper (for extracting full article content: title, body, date, author) Copy the scraperId for each. Enable AI Scraper API access in your MrScraper account settings. Prepare your Google Sheet: Create a sheet with a Domain column listing the news source URLs you want to monitor Add as many sources as needed — each will be looped through on every run Add your credentials in n8n: MrScraper API token OpenAI API key Slack OAuth Notion OAuth Configure your Notion database with these properties: Title, Source URL, Sentiment (select), Sentiment Score (number), Tone (select), Key Topics (text), Summary (text), Action Required (checkbox), Action Reason (text), Published At (text), Scraped At (text) Update the workflow settings: Set your brandName and brandKeywords (comma-separated keywords to filter relevant articles) Set your mapScraperId and generalScraperId Set your slackChannel name (e.g. #brand-monitoring) Set your notionDatabaseId (from your Notion database URL) Set maxArticles to control how many articles are processed per source per run Adjust the Schedule Trigger to your preferred run time (default: every 24 hours) Customize the topic/brand keywords inside the Pick Best Content + Filter Irrelevant code node to match your monitoring targets Requirements MrScraper** account with API access enabled OpenAI** account (GPT-4o-mini used by default) Slack** workspace with OAuth connected Notion** workspace with a database set up and OAuth connected Google Sheets** (OAuth2 connected) for storing your list of news sources Good to Know GPT-4o-mini is used by default to keep costs low — processing costs approximately $0.0001 per article. Switch to GPT-4o only if you need higher analysis quality. The workflow has two distinct Slack outputs: an immediate urgent alert fires the moment a high-priority article is detected, while the Daily Digest summarizes the entire run at the end. Articles that are too short (under 50 words) or don't match your defined keywords are silently skipped — the workflow never breaks even if a source returns no usable content. Sentiment scores range from -1.0 (strongly negative) to 1.0 (strongly positive), making it easy to track trends over time in Notion or a connected dashboard. Customising This Workflow Track multiple brands or topics:** Duplicate the keyword filter and AI prompt steps to run parallel analysis pipelines for different subjects in a single workflow. Add email reporting:** Insert a Gmail node after the Slack Daily Digest step to also send the daily summary as a formatted email report. Connect to a dashboard:** Pipe the Notion database into a tool like Google Looker Studio or Retool to visualize sentiment trends over time with charts and filters. Adjust scrape frequency:** Change the Schedule Trigger from daily to hourly for breaking news monitoring, or weekly for slower trend tracking. Expand news sources:** Add Google News search URLs (e.g. https://news.google.com/search?q=YOUR_BRAND) to your input sheet for broader coverage beyond specific news sites.

🤖 Automated AI content researcher: YouTube & RSS to Notion via Gemini This workflow is basically my shortcut for researching popular topics to create podcast content on without spending all day on YouTube, scrolling X and reading websites. It grabs the latest videos and articles from the last 24 hours, runs them through Gemini Pro (with SerpAPI to double-check inputs), and then spits out actual content hooks and thumbnail ideas. Everything gets cleaned up into a neat Notion database so I can just log in, see what's hot, and start working on the podcast. What you need To use this workflow, you need credentials for the following services: Google Gemini API: (Free tier available via Google AI Studio) for the LLM. SerpAPI: To allow the AI Agent to browse live Google search results. Google Sheets: To maintain your list of target RSS feeds. Notion: For storing the researched content. Telegram: For mobile notifications. Resources Video Tutorial: https://youtu.be/IoHayi68Ckk Created by: Scalo Labs

Generate market research reports from news and competitor sites to Notion and Slack This workflow automates market research and competitive intelligence by collecting industry news and competitor website updates, analyzing them with AI, and publishing structured insights to Notion and Slack. It replaces manual monitoring and summarization with a repeatable, scalable workflow suitable for daily or weekly use. Who’s it for Marketing teams** who want to track industry trends and competitor messaging in one place Product managers** looking for early signals to inform roadmap and prioritization decisions Founders and analysts** who need automated market briefings without manual research How it works A scheduled trigger starts the workflow (daily by default). Industry news is fetched via NewsAPI while competitor websites are scraped in parallel. All collected content is consolidated and sent to OpenAI (GPT-4o) for analysis. The AI generates a structured report including trends, SWOT insights, and recommended actions. The full Markdown report is saved to a Notion database, and an executive summary is posted to Slack. If any API call or scraping step fails, an error notification is sent to Slack. How to set up Add API credentials for OpenAI, NewsAPI, Notion, and Slack. Configure keywords and competitor URLs in the Research Configuration node. Select your Notion database and Slack channels in the relevant nodes. Requirements OpenAI API key (GPT-4o access) NewsAPI account Notion and Slack accounts How to customize the workflow Change the trigger to run weekly or on demand Modify the AI prompt to focus on pricing, features, or specific competitors Add additional sources such as RSS feeds or more competitor sites

Intelligent Multi-Source Document Orchestrator: AI Triage & Multi-Tier Routing 🎯 Description This is an enterprise-grade Intelligent Document Processing (IDP) hub designed to handle high-volume document ingestion, classification, and departmental routing. It transforms monolithic bulk scans into actionable data streams by leveraging a "Split-Extract-Route" architecture. ✨ The Orchestration Lifecycle Intake Layer - Aggregates document triggers from Google Drive, Webhooks, and Scheduled Tasks. It implements a strict file integrity check to ensure only healthy binaries enter the pipeline. Document Atomization - Utilizes the HTML to PDF (Split) node to explode multi-page bulk scans into individual, manageable pages. This ensures that a single PDF containing an invoice, a contract, and a payroll slip is correctly decomposed for separate processing. AI Extraction & Intelligence - A sophisticated Code Node acts as the "Brain," using regex and keyword logic to classify documents (Invoices, Payroll, Legal, POs) and extract structured metadata (Amounts, Vendors, Due Dates) with confidence scoring. Smart Routing Matrix - Documents are contextually routed based on department and value: Invoices & POs: High-value items (>$5,000) trigger a priority escalation track. Legal & Payroll: Grouped and logged for standard departmental audit. High-Value Escalation - For critical financial items, the system creates an approval task in Notion and sends an urgent escalation email via Gmail to the CFO/Manager. Quality Assurance & Alerts - Low-confidence extractions (<85%) are automatically quarantined, triggering a Slack alert for immediate manual team review. Forensic Audit Logging - Every action, confidence score, and routing decision is appended to a Google Sheets master audit log for total transparency and compliance. 💡 Key Technical Features Conditional Gating:** Multi-tier IF nodes ensure that documents only proceed once they meet specific quality and value thresholds. Binary Integrity Guard:** Prevents workflow crashes by validating file data before intensive AI processing. Bi-Directional Governance:** Simultaneously updates Notion for task management and Google Sheets for historical reporting. 🚀 Benefits ✅ Zero Manual Sorting - Automates the transition from "Bulk Scan" to "Departmental Action." ✅ Risk Mitigation - High-value items and low-confidence data are surfaced immediately for human oversight. ✅ Regulatory Compliance - Every document lifecycle is tracked with a permanent, immutable audit trail. Tags: #IDP #AI #document-intelligence #notion #slack #automation #fintech Category: Finance & Operations | Difficulty: Advanced

Employee Onboarding Automation with Multi-System Provisioning What this workflow does This workflow automates the end-to-end employee onboarding process by provisioning new hires across multiple internal systems and delivering a personalized welcome experience. Upon receiving new employee data via a webhook or form submission, it creates user accounts in Google Workspace, invites the employee to Slack, sets up a Notion onboarding page, generates an AI-powered welcome package, and notifies relevant stakeholders. All onboarding activities are logged for tracking and audit purposes. This template helps HR and People Operations teams reduce manual work, ensure consistency, and deliver a smooth onboarding experience from day one. How it works Employee data intake Triggered by a webhook or form submission. Collects employee details such as name, email, department, role, start date, and manager. Data preparation Generates a company email address. Assigns a unique onboarding ID. Standardizes employee information for downstream systems. Parallel account provisioning Creates a Google Workspace user account. Sends an invitation to the Slack workspace. Creates a dedicated Notion onboarding page. Executes these steps in parallel to minimize onboarding time. Provisioning result compilation Consolidates account creation statuses. Produces a single onboarding summary object. AI-powered welcome package Generates: A personalized welcome message A suggested first-week schedule Practical tips for success in the role Formats content for email delivery. Notifications & communication Sends a welcome email to the employee (if a personal email is provided). Notifies HR or People Ops via Slack. Logs onboarding details to Google Sheets. Webhook response Returns a structured JSON response confirming onboarding initiation. Setup requirements Before activating this workflow, ensure the following are configured: Enable the webhook endpoint and connect it to your form or HR system. Configure Google Workspace Admin API access. Set up Slack workspace permissions for user invitations. Define a parent Notion page for onboarding content. Prepare Google Sheets for onboarding logs. Customize email templates, departments, and org unit paths as needed. Required credentials This workflow requires the following credentials to be configured in n8n: Google API** (Google Workspace user provisioning) Slack** (workspace invitations and HR notifications) Notion** (onboarding page creation) OpenAI** (AI-generated welcome content) Gmail** (sending welcome emails) Google Sheets** (onboarding tracking and logs) Customization ideas Add role-based access provisioning (VPN, GitHub, Jira, etc.). Delay account creation until a specific start date. Generate localized onboarding content by region or language. Integrate with HRIS tools such as BambooHR or Workday. Add approval steps for managers or IT before provisioning. Who this is for HR & People Operations teams IT & Identity management teams Startups and scaling organizations Companies seeking consistent, automated onboarding This template provides a scalable, repeatable onboarding foundation that connects HR systems, IT provisioning, and AI-driven communication into a single automated workflow.

📘 Description This workflow automates end-to-end AI-driven inventory intelligence, transforming Airtable stock data into optimized reorder recommendations, daily operational summaries, and instant Slack alerts. It fetches all inventory rows, validates structure, computes reorder and safety-stock metrics using strict formulas, merges multi-batch AI output into a unified dataset, and distributes actionable insights across Email and Slack. Invalid or corrupted Airtable rows are logged to Google Sheets for audit and cleanup. The workflow ensures deterministic inventory math (zero improvisation), strict JSON compliance, and reliable multi-channel reporting for operations teams. ⚙️ What This Workflow Does (Step-by-Step) ▶️ Manual Trigger – Start Inventory Optimization Runs the full optimization and reporting pipeline on demand. 📦 Fetch Inventory Records from Airtable Retrieves all SKU records (ID, ItemName, SKU, quantities, reorder levels) from the Airtable Inventory table. 🔍 Validate Inventory Record Structure (IF) Ensures each record contains a valid id. Valid → routed to AI optimization Invalid → saved to Google Sheets. 📄 Log Invalid Inventory Rows to Google Sheet Captures malformed or incomplete Airtable items for audit checks and data hygiene. 🧠 Configure GPT-4o — Inventory Optimization Model Defines the AI model for stock-level calculations using strict formulas: SuggestedReorderPoint = ReorderLevel × 1.2 SuggestedSafetyStock = ReorderLevel × 0.5 StockStatus logic: Critical if QuantityInStock ≤ SuggestedSafetyStock Needs Reorder if QuantityInStock ≤ SuggestedReorderPoint OK otherwise 🤖 Generate Inventory Optimization Output (AI) The AI engine analyzes each SKU and returns: Suggested reorder point Suggested safety stock Updated stock status Clean structured JSON for each item All without markdown, hallucination, or additional logic. 🧩 Merge AI Optimization Results (Code) Consolidates all partial AI responses into one complete JSON dataset containing all SKUs. 🧠 Configure GPT-4o – Email Summary Model Prepares the AI model used for generating a professional operations-team email. 📧 Generate Inventory Email Summary (AI) Creates a manager-ready email including: High-level inventory health Detailed SKU summaries Alerts for low, reorder-level, or critical stock Recommended actions for today’s operations 📨 Email Inventory Summary to Manager (Gmail) Sends the completed inventory summary to the operations manager. 🧠 Configure GPT-4o – Slack Summary Model Sets up GPT-4o to produce a compact, emoji-supported Slack summary. 💬 Generate Inventory Slack Summary (AI) Builds a Slack-optimized message containing: One-line inventory health Bullet list of SKUs with stock status Clear alerts for reorder-level or critical items One recommended action line 📡 Notify Operations Team on Slack Delivers the optimized Slack summary to the operations Slack user/channel for real-time visibility. 🧩 Prerequisites Airtable access token Azure OpenAI GPT-4o credentials Google Sheets OAuth Slack API credentials Gmail OAuth 💡 Key Benefits ✔ AI-powered stock calculations with strict formulas ✔ Reliable reorder and safety-stock predictions ✔ Instant multi-channel reporting (Email + Slack) ✔ Full audit logging for invalid data ✔ Zero hallucinations—pure structured JSON ✔ Faster decision-making for operations teams 👥 Perfect For Operations & supply-chain teams Inventory managers Retail & e-commerce units Businesses using Airtable for stock tracking

Description Automatically triage Product UAT feedback using AI, route it to the right tools and teams, and close the feedback loop with testers, all in one workflow. This workflow analyzes raw UAT feedback, classifies it (critical bug, feature request, UX improvement, or noise), validates AI confidence, escalates when human review is needed, and synchronizes everything across Jira, Slack, Notion, Google Sheets, and email. Context Product teams often receive unstructured UAT feedback from multiple sources (forms, Slack, internal tools), making triage slow, inconsistent, and error-prone. This workflow ensures: Faster bug detection Consistent categorization Zero feedback lost Clear accountability between Product, Engineering, and Design It combines AI automation with human-in-the-loop control, making it safe for real production environments. Who is this for? Product Managers running UAT or beta programs Project Managers coordinating QA and release validation Product Ops / PMO teams Engineering teams who want faster, cleaner bug escalation Any team managing high-volume UAT feedback Perfect for teams that want speed without sacrificing control. Requirements Webhook trigger (form, internal tool, Slack integration, etc.) OpenAI account (for AI triage) Jira (bug tracking) Slack (team notifications) Notion (product roadmap / UX backlog) Google Sheets (UAT feedback log) Gmail (tester & manual review notifications) How it works Trigger The workflow starts when UAT feedback is submitted via a webhook (form, Slack, or internal tool). Normalize & Clean Incoming data is normalized into a consistent structure (tester, build, page, message) and cleaned to be AI-ready. AI Triage An AI model analyzes the feedback and returns: Type (Critical Bug, Feature Request, UX Improvement, Noise) Severity & sentiment Summary and suggested title Confidence score Quality Control If the AI output is unreliable (low confidence or parsing error), the feedback is automatically routed to manual review via email and Slack. Routing & Actions If confidence is sufficient: Critical Bugs → Jira issue + Engineering Slack alert Feature Requests → Notion roadmap UX Improvements → Design / UX tracking Noise → Archived but traceable Closed Loop The tester is notified via Slack or email, and the workflow responds to the original webhook with a structured status payload. What you get One unified UAT triage system Faster bug escalation Clean product and UX backlogs Full traceability of every feedback Automatic tester communication Safe AI usage with human fallback About me : I’m Yassin a Product Manager Scaling tech products with a data-driven mindset. 📬 Feel free to connect with me on Linkedin

This workflow converts raw ClickUp task updates—received directly through a webhook—into fully automated release documentation. It validates incoming payloads, fetches and cleans task details, enriches them with AI-generated metadata, produces structured release notes using GPT-4o, publishes them to Notion, notifies stakeholders on Slack, emails a formatted summary, and logs the release into Google Sheets. The system handles malformed events gracefully by logging invalid payloads and continues only when a valid task_id is present. It extracts structured fields (title, description, links, priority, assignee), then augments them with AI-driven classifications such as risk level, change type, module, and impact score. GPT-4o generates polished release notes following a strict template. Finally, the workflow distributes the release across multiple channels while maintaining an auditable, centralized history. ⚙️ What This Workflow Does (Step-by-Step) 🟢 Webhook — Receive ClickUp Task Update Captures incoming events from ClickUp via POST and forwards the raw body for parsing. 🧹 Code in JavaScript — Extract task_id Parses the raw webhook body and safely extracts task_id. Invalid JSON → forwarded to error logging. 🔍 Validate Incoming ClickUp Task Event Checks if task_id exists. Valid → continue workflow Invalid → log error to Google Sheets 📄 Fetch Full Task Details from ClickUp Retrieves full task metadata: title, description, status, priority, links, assignee details, and due date. 🧩 Extract Clean Task Fields from ClickUp Data Normalizes and structures the task fields into a clean, usable JSON object. 🧠 Provide GPT-4o Model for Metadata Extraction Loads the language model for metadata generation. 🔍 Generate Release Metadata via AI AI generates structured metadata including: • risk_level • change_type • module • impact_score • requires_testing 🧹 Parse AI Metadata JSON Output Parses stringified JSON from the AI node into valid structured JSON. Malformed metadata → returned as an error object. 🔀 Merge Task Details with Metadata Combines clean task fields with AI-generated metadata into a complete release-ready object. 🧠 Provide GPT-4o Model for Release Notes Supplies the language model needed to generate formal release notes. ✍️ Generate Structured Release Notes via AI Produces uniform release notes containing: • Summary • Improvements & Features • Bug Fixes • Impact Analysis • Known Issues 📝 Extract Release Notes Title & Final Output Extracts title from markdown and prepares final content for publishing. 📘 Create Release Notes Page in Notion Saves the release notes as a new page in the Notion Release Notes database. 💬 Post Release Announcement to Slack Sends formatted release notes + Notion link to the specified Slack user/channel. 📧 Send Release Summary Email Sends a structured HTML email with the release summary, full notes, and Notion link. 📊 Append Release Log Entry to Google Sheet Writes a complete release log entry including: • task ID • title • priority • module • risk level • Notion URL • Slack message URL • release date 🛑 Log Invalid ClickUp Events to Google Sheet Stores any invalid or incomplete webhook payload for debugging and auditing. 🧩 Prerequisites • ClickUp API token • Public webhook endpoint in n8n • Azure OpenAI GPT-4o credentials • Notion API integration • Slack API token • Google Sheets OAuth • Gmail OAuth 💡 Key Benefits ✔ Converts ClickUp updates directly into finished release documentation ✔ AI-powered metadata ensures consistent classification ✔ Instant multi-channel dissemination: Slack + Email + Notion ✔ Automatic logging for audit, QA, and release governance ✔ Eliminates manual writing, formatting, and cross-platform updates 👥 Perfect For Product teams running constant sprints Engineering teams needing reliable release documentation Teams using ClickUp as their primary task manager Organizations with multi-channel release communication needs

Who is this for? This template is perfect for agencies, consultancies, freelancers, and project-based teams who want to eliminate repetitive onboarding tasks. If you're tired of manually creating folders, Slack channels, and project pages every time a new client signs a contract, this automation will save you hours. What this workflow does When a new contract PDF is uploaded to a designated Google Drive folder, this workflow automatically: Parses the filename to extract client name, project name, and contact email Creates a project folder structure in Google Drive with organized subfolders Creates a dedicated Slack channel for project communication Sets up a Notion project page with initial kickoff tasks Logs project details to a master Google Sheet for tracking Drafts a personalized welcome email using OpenAI GPT-4o-mini Notifies your team on Slack with all relevant links when complete Setup steps Time required: ~15 minutes Configure OAuth credentials for Google Drive, Gmail, Google Sheets, Slack, and Notion Add your OpenAI API key for AI-powered email drafting Update the "Set Config Variables" node with your specific IDs: Google Drive parent folder ID Notion database ID Google Sheet ID Slack notification channel ID Set up the trigger folder in Google Drive where contracts will be uploaded Prepare your Google Sheet with columns: Client, Project Code, Notion Link, Slack Channel, Drive Folder Requirements Google Workspace account (Drive, Gmail, Sheets) Slack workspace with bot permissions to create channels Notion workspace with API integration OpenAI API key File naming convention Upload PDF files using this format: [email protected] Example: [email protected] How to customize Add more subfolders: Duplicate the "Create Deliverables Subfolder" node Customize the email prompt: Edit the "AI Draft Welcome Email" node Add more Notion properties: Extend the "Create Notion Project Page" node Change notification format: Modify the "Notify Team on Slack" message

Description This workflow turns scattered user feedback into a structured product backlog pipeline. It collects feedback from three channels (Telegram bot, Google Form/Sheets, and Gmail), normalizes it, and sends it to an AI model that: Classifies the feedback (bug, feature request, question, etc.) Extracts sentiment and pain level Estimates business impact and implementation effort Generates a short summary Then a custom RICE-style priority score is computed, a Jira ticket is created automatically, a Notion page is generated for documentation, and a monthly product report is sent by email to stakeholders. It helps product & support teams move from “random feedback in multiple tools” to a repeatable, data-driven product intake process with zero manual triage. Context In most teams, feedback is: spread across emails, forms, and chat messages manually copy–pasted into Jira (when someone remembers) hard to prioritize objectively nearly impossible to review at the end of the month This workflow solves that by: Centralizing feedback from Telegram, Google Forms/Sheets, and Gmail Automatically normalizing all inputs into the same JSON structure Using AI to categorize, tag, summarize, and score each request Calculating a RICE-based priority adapted to your tiers (free / pro / enterprise) Creating a Jira issue with all the context and acceptance criteria Generating a Notion page for each feedback+ticket pair Sending a monthly “Product Intelligence Report” by email with insights & recommendations The result: less manual work, better prioritization, and a clear story of what users are asking for. Target Users This template is designed for: Product Managers and Product Owners SaaS teams with multiple feedback channels Support / CS teams that need a structured escalation path Project Managers who want objective, data-driven prioritization Any team that wants “feedback → backlog” automation without building a custom platform Technical Requirements You’ll need: Google Sheets credential Gmail credential Telegram Bot + Chat ID Google Form connected to a Google Sheet Jira credential (Jira Cloud) Notion credential OpenAI/ Anthropic credential for the AI analysis node An existing Jira project where tickets will be created A Notion database or parent page where feedback pages will be stored Workflow Steps The workflow is organized into four main sections: 1) Triggers (Multi-channel Intake) Telegram Trigger – Listens for new messages sent to your bot Google Form / Sheet Trigger – Listens for new form responses / rows Gmail Trigger – Listens for new emails matching your filter (e.g. [Feedback] in subject) All three paths send their payloads into a “Data Normalizer” node that outputs a unified structure: 2) Request Treated and Enriched (AI Analysis) Instant Reply (Telegram only) – Sends a quick “Thanks, we’re analysing your feedback” message User Enrichment – Enriches user tier based on mapping Message a Model (AI) classifies the feedback extracts tags scores sentiment, pain, business impact, effort generates a short summary & acceptance criteria JSON Parse / Merge – Merges AI output back into the original feedback object 3) Priority Calculation & Jira Ticket Creation Priority Calculator applies a RICE-style formula using: pain level business impact implementation effort user tier weight assigns internal priority: P0 / P1 / P2 / P3 maps to Jira priority: Highest / High / Medium / Low Create Jira Issue – Creates a ticket with: summary from AI description including raw feedback, AI analysis, and RICE breakdown labels based on tags priority based on the calculator Post-processing – Prepares a clean payload for notifications & logging IF (Source = Telegram) – Sends a rich Telegram message back to the user with: Jira key + URL category, priority, RICE score, tags, and estimated handling time Append to Google Sheet (Analytics Log) – Logs each feedback with: source, user, category, sentiment, RICE score, priority, Jira key, Jira URL Create Notion Page – Creates a documentation page linking: the feedback the Jira ticket AI analysis acceptance criteria 4) Monthly Reporting (Product Intelligence Report) Monthly Trigger – Runs once a month Query Google Sheet – Fetches all feedback logs for the previous month Aggregate Monthly Stats – Computes: feedback volume breakdown by category / sentiment / source / tier / priority average RICE, pain, and impact top P0/P1 issues and top feature requests Message a Model (AI) – Generates a written “Product Intelligence Report” with: executive summary key insights & trends top pain points strategic recommendations Parse Response: Extracts structured insights + short summary Create Notion Report Page with: metrics, charts-ready tables, insights, and recommendations Append Monthly Log to Google Sheet – Stores high-level stats for historical tracking Send Email with a formatted HTML report to stakeholders with: key metrics top issues recommendations link to the full Notion report Key Features Multi-channel intake: Telegram + Google Forms/Sheets + Gmail AI-powered triage: automatic category, sentiment, tags, and summary RICE-style priority scoring with tier weighting Automatic Jira ticket creation with full context Notion documentation for each feedback and for monthly reports Google Sheets analytics log for exploration and dashboards Monthly “Product Intelligence Report” sent automatically by email Designed to be adaptable: you can plug in your own labels, tiers, and scoring rules Expected Output When the workflow is running, you can expect: A Jira issue created automatically for each relevant feedback A confirmation email A Telegram confirmation message when the feedback comes from Telegram A Google Sheet filled with normalized feedback and scoring data A Notion page per feedback/ticket with AI analysis and acceptance criteria Every month: a Notion “Monthly Product Intelligence Report” page a summary email with key metrics and insights for your stakeholders How it works Trigger – Listens to Telegram / Google Forms / Gmail Normalize – Converts all inputs to a unified feedback format Enrich with AI – Category, sentiment, pain, impact, effort, tags, summary Score – Computes RICE-style priority and maps to Jira priority Create Ticket – Opens a Jira issue + Notion page + logs to Google Sheets Notify – Sends Telegram confirmation (if source is Telegram) Report – Once a month, aggregates everything and sends a Product Intelligence Report Tutorial Video Tutorial video: Watch the Youtube Tutorial video About me I’m Yassin a Project & Product Manager Scaling tech products with data-driven project management. 📬 Feel free to connect with me on Linkedin

Description Automate your weekly social media analytics with this end-to-end AI reporting workflow. 📊🤖 This system collects real-time Twitter (X) and Facebook metrics, merges and validates data, formats it with JavaScript, generates an AI-powered HTML report via GPT-4o, saves structured insights in Notion, and shares visual summaries via Slack and Gmail. Perfect for marketing teams tracking engagement trends and performance growth. 🚀💬 What This Template Does 1️⃣ Starts manually or on-demand to fetch the latest analytics data. 🕹️ 2️⃣ Retrieves follower, engagement, and post metrics from both X (Twitter) and Facebook APIs. 🐦📘 3️⃣ Merges and validates responses to ensure clean, complete datasets. 🔍 4️⃣ Runs custom JavaScript to normalize and format metrics into a unified JSON structure. 🧩 5️⃣ Uses Azure OpenAI GPT-4o to generate a visually rich HTML performance report with tables, emojis, and insights. 🧠📈 6️⃣ Saves the processed analytics into a Notion “Growth Chart” database for centralized trend tracking. 🗂️ 7️⃣ Sends an email summary report to the marketing team, complete with formatted HTML insights. 📧 8️⃣ Posts a concise Slack update comparing platform performance and engagement deltas. 💬 9️⃣ Logs any validation or API errors automatically into Google Sheets for debugging and traceability. 🧾 Key Benefits ✅ Centralizes all social metrics into a single automated flow. ✅ Delivers AI-generated HTML reports ready for email and dashboard embedding. ✅ Reduces manual tracking with Notion and Slack syncs. ✅ Ensures data reliability with built-in validation and error logging. ✅ Gives instant, visual insights for weekly marketing reviews. Features Multi-platform analytics integration (Twitter X + Facebook Graph API). JavaScript node for dynamic data normalization. Azure OpenAI GPT-4o for HTML report generation. Notion database update for long-term trend storage. Slack and Gmail nodes for instant sharing and communication. Automated error capture to Google Sheets for workflow reliability. Visual, emoji-enhanced reporting with HTML formatting and insights. Requirements Twitter OAuth2 API credentials for access to public metrics. Facebook Graph API access token for page insights. Azure OpenAI API key for GPT-4o report generation. Notion API credentials with write access to “Growth Chart” database. Gmail OAuth2 credentials for report dispatch. Slack Bot Token with chat:write permission for posting analytics summaries. Google Sheets OAuth2 credentials for maintaining the error log. Environment Variables TWITTER_API_KEY FACEBOOK_ACCESS_TOKEN AZURE_OPENAI_API_KEY NOTION_GROWTH_DB_ID GMAIL_REPORT_RECIPIENTS SLACK_REPORT_CHANNEL_ID GOOGLE_SHEET_ERROR_LOG_ID Target Audience 📈 Marketing and growth teams tracking cross-platform performance 💡 Social media managers needing automated reporting 🧠 Data analysts compiling weekly engagement metrics 💬 Digital agencies managing multiple brand accounts 🧾 Operations and analytics teams monitoring performance KPIs Step-by-Step Setup Instructions 1️⃣ Connect all API credentials (Twitter, Facebook, Notion, Gmail, Slack, and Sheets). 2️⃣ Paste your Facebook Page ID and Twitter handle in respective API nodes. 3️⃣ Verify your Azure OpenAI GPT-4o connection and prompt text for HTML report generation. 4️⃣ Update your Notion database structure to match “Growth Chart” property names. 5️⃣ Add your marketing email in the Gmail node and test delivery. 6️⃣ Specify the Slack channel ID where summaries will be posted. 7️⃣ Optionally, connect a Google Sheet tab for error tracking (error_id, message). 8️⃣ Execute the workflow once manually to validate data flow. 9️⃣ Activate or schedule it for weekly or daily analytics automation. ✅

Description: Make your SDK documentation localization-ready before translation with this n8n automation template. The workflow pulls FAQ content from Notion, evaluates each entry using Azure OpenAI GPT-4o-mini, and scores its localization readiness based on jargon density, cultural context, and translation risk. It logs results into Google Sheets and notifies your team on Slack if an FAQ scores poorly (≤5). Perfect for developer documentation teams, localization managers, and globalization leads who want to identify high-risk content early and ensure smooth translation for multi-language SDKs. ✅ What This Template Does (Step-by-Step) ⚙️ Step 1: Fetch FAQs from Notion Retrieves all FAQ entries from your Notion database, including question, answer, and unique ID fields for tracking. 🤖 Step 2: AI Localization Review (GPT-4o-mini) Uses Azure OpenAI GPT-4o-mini to evaluate each FAQ for localization challenges such as: Heavy use of technical or cultural jargon Region-specific policy or legal references Non-inclusive or ambiguous phrasing Potential mistranslation risk Outputs a detailed report including: Score (1–10) – overall localization readiness Detected Issues – list of problematic elements Priority – high, medium, or low for translation sequencing Recommendations – actionable rewrite suggestions 🧩 Step 3: Parse AI Response Converts the raw AI output into structured JSON (score, issues, priority, recommendations) for clean logging and filtering. 📊 Step 4: Log Results to Google Sheets Appends one row per FAQ, storing fields like Question, Score, Priority, and Recommendations — creating a long-term localization quality tracker. 🚦 Step 5: Filter High-Risk Content (Score ≤5) Flags FAQs with low localization readiness for further review, ensuring that potential translation blockers are addressed first. 📢 Step 6: Send Slack Alerts Sends a Slack message with summary details for all high-risk FAQs — including their score and key issues — keeping localization teams informed in real time. 🧠 Key Features 🌍 AI-powered localization scoring for SDK FAQs 🤖 Azure OpenAI GPT-4o-mini integration 📊 Google Sheets-based performance logging 📢 Slack notifications for at-risk FAQs ⚙️ Automated Notion-to-AI-to-Sheets pipeline 💼 Use Cases 🧾 Audit SDK documentation before translation 🌐 Prioritize localization tasks based on content risk 🧠 Identify FAQs that need rewriting for non-native audiences 📢 Keep global documentation teams aligned on translation readiness 📦 Required Integrations Notion API – to fetch FAQ entries Azure OpenAI (GPT-4o-mini) – for AI evaluation Google Sheets API – for logging structured results Slack API – for sending alerts on high-risk FAQs 🎯 Why Use This Template? ✅ Detect localization blockers early in your SDK documentation ✅ Automate readiness scoring across hundreds of FAQs ✅ Reduce translation rework and cultural misinterpretation ✅ Ensure a globally inclusive developer experience

Description Keep your internal knowledge base fresh and reliable with this automated FAQ freshness monitoring system. 🧠📅 This workflow tracks FAQ update dates in Notion, calculates SLA compliance, logs results in Google Sheets, and sends Slack alerts for outdated items. Perfect for documentation teams ensuring content accuracy and operational visibility across platforms. 🚀💬 What This Template Does 1️⃣ Triggers every Monday at 10:00 AM to start freshness checks. ⏰ 2️⃣ Fetches FAQ entries from your Notion database. 📚 3️⃣ Computes SLA status based on the last edited date (30-day threshold). 📆 4️⃣ Updates a Google Sheet with current FAQ details and freshness status. 📊 5️⃣ Filters out overdue FAQs that need review. 🔍 6️⃣ Aggregates all overdue items into one report. 🧾 7️⃣ Sends a consolidated Slack alert with direct Notion links and priority tags. 💬 Key Benefits ✅ Maintains documentation freshness across systems. ✅ Reduces support friction from outdated FAQs. ✅ Centralizes visibility with Google Sheets reporting. ✅ Notifies your team in real time via Slack. ✅ Enables SLA-based documentation governance. Features Weekly automated schedule (every Monday at 10 AM). Notion database integration for FAQ retrieval. SLA computation and overdue filtering logic. Google Sheets sync for audit logging. Slack notification for overdue FAQ alerts. Fully configurable thresholds and alerting logic. Requirements Notion API credentials with database read access. Google Sheets OAuth2 credentials with edit access. Slack Bot Token with chat:write permission. Environment variables : NOTION_FAQ_DATABASE_ID GOOGLE_SHEET_FAQ_ID SLACK_FAQ_ALERT_CHANNEL_ID Target Audience Knowledge management and documentation teams 🧾 SaaS product teams maintaining FAQ accuracy 💡 Support operations and customer success teams 💬 QA and compliance teams monitoring SLA adherence 📅 Step-by-Step Setup Instructions 1️⃣ Connect Notion credentials and set your FAQ database ID. 2️⃣ Create a Google Sheet with required headers (Title, lastEdited, slaStatus, etc.). 3️⃣ Add your Slack credentials and specify the alert channel ID. 4️⃣ Configure the cron schedule (0 10 * * 1) for Monday 10:00 AM checks. 5️⃣ Run once manually to verify credentials and mappings. 6️⃣ Activate for ongoing weekly freshness monitoring. ✅

📘 Description: This end-to-end automation transforms developer support emails into actionable FAQs and sentiment insights using Azure OpenAI GPT-4o, Gmail, Notion, Slack, and Google Sheets. It not only classifies and summarizes each email into a Notion knowledge base but also detects sentiment and urgency, alerts the team on Slack for critical messages, and automatically replies to users with acknowledgment emails. Every failed or malformed payload is transparently logged in Google Sheets — ensuring zero message loss and full visibility into the AI pipeline. The result is a complete AI-driven customer support loop, from inbox to Notion and back to the sender. ⚙️ What This Workflow Does (Step-by-Step) 🟢 Gmail Polling Trigger – Developer Support Inbox Continuously monitors the developer support Gmail inbox every minute for new messages. Extracts the subject, sender, and snippet to initiate AI analysis. 🔍 Validate Email Payload (IF Node) Checks if each incoming email contains valid message data (like message ID and subject). ✅ True Path: continues to AI analysis ❌ False Path: logs error details in Google Sheets for debugging. 🧠 Configure GPT-4o Model (Azure OpenAI) Initializes GPT-4o as the reasoning model for semantic classification of developer support content. 🤖 Analyze & Classify Developer Email (AI Agent) Interprets each email and produces a structured JSON with: Problem summary FAQ category (e.g., API, Billing, UI) 2–3 line solution “Is recurring” flag for common issues. 🧹 Parse & Clean AI JSON Output (Code Node) Removes code formatting (json) and safely parses GPT-4o’s output into clean JSON. If parsing fails, the raw text and error message are sent to Google Sheets for review. 📘 Save FAQ Entry to Notion Database Creates a new FAQ record inside Notion’s “Release Notes” database. Stores the problem, category, and solution as searchable structured fields. 💬 Announce New FAQ in Slack Posts a summary of the new FAQ in Slack with title, category, and answer preview. Includes a link to view the Notion record instantly for team visibility. 🧠 Configure GPT-4o Model (Sentiment Analysis) Sets up another GPT-4o instance focused on understanding tone, emotion, and urgency of each email. ❤️ Analyze Email Sentiment & Urgency (AI Agent) Analyzes the email content to determine: Urgency: Low, Medium, High, Critical Sentiment: Positive, Neutral, Frustrated, Angry Immediate response required? (Yes/No) Provides a short “reason” explaining the classification. 🧹 Parse AI JSON Output – Sentiment Analysis Cleans and validates the JSON from sentiment AI for consistent field names (urgency, sentiment, reason). ⚖️ Filter Critical or High-Urgency Emails (IF Node) Checks if urgency == High or Critical. ✅ True Path: triggers escalation to Slack ❌ False Path: ends quietly to avoid unnecessary noise. 🚨 Alert Team in Slack – Critical Issue Sends an immediate Slack alert with: Email snippet Detected urgency and sentiment Short justification (reason) CTA for urgent action. Ensures fast team response to high-priority issues. 📨 Send Acknowledgment Email to Sender (Gmail Node) Automatically replies to the customer confirming receipt and providing a short AI-generated solution summary. Thanks the user and links the response back to the knowledge base — creating a closed-loop support experience. 🪶 Log Workflow Errors to Google Sheets Appends all failed validations, missing fields, or JSON parsing issues to the “error log sheet.” Provides a live audit trail for monitoring workflow health. 🧩 Prerequisites Gmail account with API access Azure OpenAI (GPT-4o) credentials Notion API integration (for FAQ database) Slack API access (for team alerts) Google Sheets (for logging errors) 💡 Key Benefits ✅ Converts support emails into structured FAQs automatically ✅ Detects sentiment & urgency for faster triage ✅ Keeps Notion knowledge base continuously updated ✅ Sends Slack alerts for critical issues instantly ✅ Maintains transparent error logs in Google Sheets 👥 Perfect For Developer Relations or Product Support Teams SaaS companies managing large support volumes Teams using Gmail, Notion, and Slack for internal comms Startups automating customer response and knowledge creation

📊 Description This workflow automatically classifies new Stack Overflow questions by topic, generates structured FAQ content using GPT-4o-mini, logs each entry in Google Sheets, saves formatted FAQs in Notion, and notifies your team on Slack — ensuring your product and support teams stay aligned with real-world developer discussions. 🤖💬📚 ⚙️ What This Template Does Step 1: Monitors Stack Overflow RSS feeds for new questions related to your selected tags. ⏱️ Step 2: Filters out irrelevant or incomplete questions before processing. 🧹 Step 3: Uses OpenAI GPT-4o-mini to classify each question into a topic category (Frontend, Backend, DevOps, etc.). 🧠 Step 4: Generates structured FAQ content including summaries, technical insights, and internal guidance. 📄 Step 5: Saves formatted entries into your Notion knowledge-base database. 📚 Step 6: Logs all FAQ data into a connected Google Sheet for analytics and tracking. 📊 Step 7: Sends real-time Slack notifications with quick links to the new FAQ and the original Stack Overflow post. 🔔 Step 8: Provides automatic error detection — any failed AI or Notion step triggers an instant Slack alert. 🚨 💡 Key Benefits ✅ Builds a continuously updated, AI-driven knowledge base ✅ Reduces repetitive support and documentation work ✅ Keeps product and dev teams aware of trending community issues ✅ Enhances internal docs with verified Stack Overflow insights ✅ Maintains an audit trail via Google Sheets ✅ Alerts your team instantly on errors or new FAQs 🧩 Features Automatic Stack Overflow RSS monitoring Dual-layer OpenAI integration (Topic Classification + FAQ Generation) Structured Notion database integration Google Sheets logging for analytics Slack notifications for new FAQs and error alerts Custom tag-based question filtering Near real-time updates (every minute) Built-in error handling for reliability 🔐 Requirements OpenAI API Key (GPT-4o-mini access) Notion API credentials with database access Google Sheets OAuth2 credentials Slack bot token with chat:write permissions Stack Overflow RSS feed URL for your preferred tags 👥 Target Audience SaaS or product teams building internal FAQ and knowledge systems Developer relations and documentation teams Customer-support teams automating knowledge reuse Technical communities curating content from Stack Overflow 🧭 Setup Instructions Add your OpenAI API credentials in n8n. Connect your Notion database and update the page or database ID. Connect Google Sheets credentials and select your tracking sheet. Connect your Slack account and specify your notification channel. Update the RSS Feed URL with your chosen Stack Overflow tags. Run the workflow manually once to test connectivity, then enable automation.

📘 Description: This workflow automates the entire release note creation and announcement process whenever a task status changes in ClickUp. Using Azure OpenAI GPT-4o, Notion, Slack, Gmail, and Google Sheets, it converts technical task data into clear, structured, and branded release notes — ready for documentation and team broadcast. The flow captures task details, generates Markdown-formatted FAQs, documents them in Notion, formats professional Slack messages, and notifies the task owner via HTML email. Any failed payloads or validation errors are logged automatically to Google Sheets for full traceability. The result is a zero-touch release workflow that saves time, keeps communication consistent, and ensures every completed feature is clearly documented and shared. ⚙️ What This Workflow Does (Step-by-Step) 🟢 ClickUp Task Status Trigger Listens for task status updates (e.g., In Review → Complete) within the specified ClickUp team. Whenever a task reaches a completion state, this node starts the release note workflow automatically. 🔍 Validate ClickUp Payload (IF Node) Checks that the incoming ClickUp webhook contains a valid task_id. ✅ True Path: Proceeds to fetch task details. ❌ False Path: Logs the invalid payload to Google Sheets for review. 📋 Fetch Task Details from ClickUp Retrieves full information about the task using the task_id, including title, description, status, assignee, priority, and custom fields. Provides complete task context for AI processing. 🧩 Parse Task Details in JavaScript Cleans and standardizes task data into JSON format with fields like title, description, priority, owner, due date, and task URL. Also extracts optional links (e.g., GitHub references). Ensures consistent, structured input for the AI model. 🧠 Configure GPT-4o Model (Azure OpenAI) Initializes GPT-4o as the core reasoning engine for FAQ and release-note generation, ensuring context-aware and concise output. 🤖 Generate Release Notes FAQ (AI Agent) Transforms task details into a Markdown-formatted release note under four standardized sections: 1️⃣ What changed 2️⃣ Why 3️⃣ How to use 4️⃣ Known issues Each section is written clearly and briefly for internal and external readers. 📘 Save Release Notes to Notion Creates a new page in the Notion “Release Notes” database. Includes task URL, owner, status, priority, and the full AI-generated FAQ content. Serves as the single source of truth for changelogs and release documentation. 💬 Configure GPT-4o Model (Slack Formatting) Prepares another GPT-4o model instance for formatting Slack-ready announcements in a professional and brand-consistent tone. 🎨 Generate Slack Release Announcement (AI Agent) Converts the Notion release information into a polished Slack message. Adds emojis, bullet points, and a clickable task URL — optimized for quick team consumption. 📢 Announce Release in Slack Posts the AI-formatted message directly to the internal Slack channel, notifying the team of the latest feature release. Keeps everyone aligned without manual drafting or posting. 📨 Send Acknowledgment Email to Assignee (Gmail Node) Sends an automated HTML email to the task owner confirming that their release is live. Includes task name, status, priority, release date, quick links to Notion and ClickUp, and a preview of the AI-generated FAQ. Delivers a professional confirmation while closing the communication loop. 🚨 Log Errors in Google Sheets Captures all payload validation errors, API failures, or processing exceptions into an “Error Log Sheet.” Ensures complete auditability and smooth maintenance of the workflow. 🧩 Prerequisites ClickUp API credentials (for task triggers & data fetch) Azure OpenAI (GPT-4o) credentials Notion API integration (for release documentation) Slack API connection (for announcements) Gmail API access (for acknowledgment emails) Google Sheets API access (for error logging) 💡 Key Benefits ✅ Converts completed tasks into professional release notes automatically ✅ Publishes directly to Notion with consistent documentation ✅ Broadcasts updates to Slack in clean, branded format ✅ Notifies assignees instantly via personalized HTML email ✅ Maintains transparent error tracking in Google Sheets 👥 Perfect For Product & Engineering Teams managing frequent feature releases SaaS companies automating changelog and release documentation Project managers maintaining internal knowledge bases Teams using ClickUp, Notion, Slack, and Gmail for daily operations

📘 Description: This workflow automates the Developer Q&A Classification and Documentation process using Slack, Azure OpenAI GPT-4o, Notion, Airtable, and Google Sheets. Whenever a new message is posted in a specific Slack channel, the workflow automatically: Captures and validates the message data Uses GPT-4o (Azure OpenAI) to check if the question matches any existing internal FAQs Logs answered questions into Notion as new FAQ entries Sends unanswered ones to Airtable for human follow-up Records any workflow or API errors into Google Sheets This ensures that every developer query is instantly categorized, documented, and tracked, turning daily Slack discussions into a continuously improving knowledge base. ⚙️ What This Workflow Does (Step-by-Step) 🟢 Slack Channel Trigger – Developer Q&A Triggers the workflow whenever a new message is posted in a specific Slack channel. Captures message text, user ID, timestamp, and channel info. 🧩 Validate Slack Message Payload (IF Node) Ensures the incoming message payload contains valid user and text data. ✅ True Path → Continues to extract and process the message ❌ False Path → Logs error to Google Sheets 💻 Extract Question Metadata (JavaScript) Cleans and structures the Slack message into a standardized JSON format — removing unnecessary characters and preparing a clean “question object” for AI processing. 🧠 Classify Developer Question (AI) (Powered by Azure OpenAI GPT-4o) Uses GPT-4o to semantically compare the question with an internal FAQ dataset. If a match is found → Marks as answered and generates a canonical response If not → Flags it as unanswered 🧾 Parse AI JSON Output (Code Node) Converts GPT-4o’s text output into structured JSON so that workflow logic can reference fields like status, answer_quality, and canonical_answer. ⚖️ Check If Question Was Answered (IF Node) If status == "answered", the question is routed to Notion for documentation; otherwise, it’s logged in Airtable for review. 📘 Save Answered Question to Notion FAQ Creates a new Notion page under the “FAQ” database containing the question, AI’s canonical answer, and answer quality rating — automatically building a self-updating internal FAQ. 📋 Log Unanswered Question to Airtable Adds unresolved or new questions into Airtable for manual review by the developer support team. These records later feed back into the FAQ training loop. 🚨 Log Workflow Errors to Google Sheets Any missing payloads, parsing errors, or failed integrations are logged in Google Sheets (error log sheet) for transparent tracking and debugging. 🧩 Prerequisites: Slack API credentials (for message trigger) Azure OpenAI GPT-4o API credentials Notion API connection (for FAQ database) Airtable API credentials (for unresolved questions) Google Sheets OAuth connection (for error logging) 💡 Key Benefits: ✅ Automates Slack Q&A classification ✅ Builds and updates internal FAQs with zero manual input ✅ Ensures all developer queries are tracked ✅ Reduces redundant questions in Slack ✅ Maintains transparency with error logs 👥 Perfect For: Engineering or support teams using Slack for developer communication Organizations maintaining internal FAQs in Notion Teams wanting to automatically capture and reuse knowledge from real developer interactions

📊 Description Automatically track SDK releases from GitHub, compare documentation freshness in Notion, and send Slack alerts when docs lag behind. This workflow ensures documentation stays in sync with releases, improves visibility, and reduces version drift across teams. 🚀📚💬 What This Template Does Step 1: Listens to GitHub repository events to detect new SDK releases. 🧩 Step 2: Fetches release metadata including version, tag, and publish date. 📦 Step 3: Logs release data into Google Sheets for record-keeping and analysis. 📊 Step 4: Retrieves FAQ or documentation data from Notion. 📚 Step 5: Merges GitHub and Notion data to calculate documentation drift. 🔍 Step 6: Flags SDKs whose documentation is over 30 days out of date. ⚠️ Step 7: Sends detailed Slack alerts to notify responsible teams. 🔔 Key Benefits ✅ Keeps SDK documentation aligned with product releases ✅ Prevents outdated information from reaching users ✅ Provides centralized release tracking in Google Sheets ✅ Sends real-time Slack alerts for overdue updates ✅ Strengthens DevRel and developer experience operations Features GitHub release trigger for real-time monitoring Google Sheets logging for tracking and auditing Notion database integration for documentation comparison Automated drift calculation (days since last update) Slack notifications for overdue documentation Requirements GitHub OAuth2 credentials Notion API credentials Google Sheets OAuth2 credentials Slack Bot token with chat:write permissions Target Audience Developer Relations (DevRel) and SDK engineering teams Product documentation and technical writing teams Project managers tracking SDK and doc release parity Step-by-Step Setup Instructions Connect your GitHub account and select your SDK repository. Replace YOUR_GOOGLE_SHEET_ID and YOUR_SHEET_GID with your tracking spreadsheet. Add your Notion FAQ database ID. Configure your Slack channel ID for alerts. Run once manually to validate setup, then enable automation.

📘 Description: This workflow automates developer Q&A handling by connecting GitHub, GPT-4o (Azure OpenAI), Notion, Google Sheets, and Slack. Whenever a developer comments on a pull request with a “how do I…” or “how to…” question, the workflow automatically detects the query, uses GPT-4o to generate a concise technical response, stores it in Notion for documentation, and instantly shares it on Slack for visibility. It reduces repetitive manual answering, boosts engineering knowledge sharing, and keeps teams informed with AI-powered insights. ⚙️ What This Workflow Does (Step-by-Step) 🟢 GitHub PR Comment Trigger — Starts the automation when a pull request comment is posted in a specified repository. Action: Listens for pull_request_review_comment events. Description: Captures comment text, author, PR number, and repository name as the trigger payload. 🔍 Validate GitHub Webhook Payload (IF Node) — Ensures the webhook data includes a valid comment URL. ✅ True Path: Continues to question detection. ❌ False Path: Sends invalid or missing data to Google Sheets for error logging. ❓ Detect Developer Question in PR Comment — Checks whether the comment includes question patterns such as “how do I…” or “how to…”. If a valid question is found, the workflow proceeds to the AI assistant; otherwise, it ends silently. 🧠 Configure GPT-4o Model (Azure OpenAI) — Connects to the GPT-4o model for intelligent language generation. Acts as the central AI engine to craft short, precise technical answers. 🤖 Generate AI Response for Developer Question — Sends the developer’s comment and PR context to GPT-4o. GPT analyzes the question and produces a short (2–3 line) helpful answer, maintaining professional and technical tone. 🧩 Extract GitHub Comment Metadata — Uses a JavaScript code node to structure key details (repo, user, comment, file path, PR number) into a clean JSON format. Prepares standardized data for storage and further use. 🧾 Save Comment Insight to Notion Database — Appends the GitHub comment, AI response, and metadata into a Notion database (“test db”). Acts as a centralized knowledge base for tracking and reusing AI-generated technical answers. 💬 Post AI Answer & PR Link to Slack — Sends the generated response and GitHub PR comment link to a Slack channel or user. Helps reviewers or teammates instantly view AI-generated suggestions and maintain active discussion threads. 🚨 Log Errors in Google Sheets (Error Handling) — Logs webhook validation or AI-processing errors into a shared Google Sheet (“error log sheet”). Ensures full visibility into workflow issues for future debugging. 🧩 Prerequisites GitHub OAuth credentials with webhook access Azure OpenAI (GPT-4o) account Notion API integration for the documentation database Slack API connection for notifications Google Sheets API access for error tracking 💡 Key Benefits ✅ Automated detection of developer questions in GitHub comments ✅ AI-generated instant answers with context awareness ✅ Centralized documentation in Notion for knowledge reuse ✅ Real-time Slack notifications for visibility and collaboration ✅ Continuous error logging for transparent troubleshooting 👥 Perfect For Developer teams using GitHub for code reviews Engineering leads wanting AI-assisted PR support Companies aiming to build self-learning documentation Teams using Notion and Slack for workflow visibility

How it Works This workflow accepts meeting transcripts via webhook (Zoom, Google Meet, Teams, Otter.ai, or manual notes), immediately processing them through an intelligent pipeline that eliminates post-meeting admin work. The system parses multiple input formats (JSON, form data, transcription outputs), extracting meeting metadata including title, date, attendees, transcript content, duration, and recording URLs. OpenAI analyzes the transcript to extract eight critical dimensions: executive summary, key decisions with ownership, action items with assigned owners and due dates, discussion topics, open questions, next steps, risks/blockers, and follow-up meeting requirements—all returned as structured JSON. The intelligence engine enriches each action item with unique IDs, priority scores (weighing urgency + owner assignment + due date), status initialization, and meeting context links, then calculates a completeness score (0-100) that penalizes missing owners and undefined deadlines. Multi-channel distribution ensures visibility: Slack receives formatted summaries with emoji categorization for decisions (✅), action items (🎯) with priority badges and owner assignments, and completeness scores (📊). Notion gets dual-database updates—meeting notes with formatted decisions and individual task cards in your action item database with full filtering and kanban capabilities. Task owners receive personalized HTML emails with priority color-coding and meeting context, while Google Calendar creates due-date reminders as calendar events. Every meeting logs to Google Sheets for analytics tracking: attendee count, duration, action items created, priority distribution, decision count, completeness score, and follow-up indicators. The workflow returns a JSON response confirming successful processing with meeting ID, action item count, and executive summary. The entire pipeline executes in 8-12 seconds from submission to full distribution. Who is this for? Product and engineering teams drowning in scattered action items across tools Remote-first companies where verbal commitments vanish after calls Executive teams needing auditable decision records without dedicated note-takers Startups juggling 10+ meetings daily without time for manual follow-up Operations teams tracking cross-functional initiatives requiring accountability Setup Steps Setup time:** 25-35 minutes Requirements:** OpenAI API key, Slack workspace, Notion account, Google Workspace (Calendar/Gmail/Sheets), optional transcription service Webhook Trigger: Automatically generates URL, configure as POST endpoint accepting JSON with title, date, attendees, transcript, duration, recording_url, organizer Transcription Integration: Connect Otter.ai/Fireflies.ai/Zoom webhooks, or create manual submission form OpenAI Analysis: Add API credentials, configure GPT-4 or GPT-3.5-turbo, temperature 0.3, max tokens 1500 Intelligence Synthesis: JavaScript calculates priority scores (0-40 range) and completeness metrics (0-100), customize thresholds Slack Integration: Create app with chat:write scope, get bot token, replace channel ID placeholder with your #meeting-summaries channel Notion Databases: Create "Meeting Notes" database (title, date, attendees, summary, action items, completeness, recording URL) and "Action Items" database (title, assigned to, due date, priority, status, meeting relation), share both with integration, add token Email Notifications: Configure Gmail OAuth2 or SMTP, customize HTML template with company branding Calendar Reminders: Enable Calendar API, creates events on due dates at 9 AM (adjustable), adds task owner as attendee Analytics Tracking: Create Google Sheet with columns for Meeting_ID, Title, Date, Attendees, Duration, Action_Items, High_Priority, Decisions, Completeness, Unassigned_Tasks, Follow_Up_Needed Test: POST sample transcript, verify Slack message, Notion entries, emails, calendar events, and Sheets logging Customization Guidance Meeting Types:** Daily standups (reduce tokens to 500, Slack-only), sprint planning (add Jira integration), client calls (add CRM logging), executive reviews (stricter completeness thresholds) Priority Scoring:** Add urgency multiplier for <48hr due dates, owner seniority weights, customer impact flags AI Prompt:** Customize to emphasize deadlines, blockers, or technical decisions; add date parsing for phrases like "by end of week" Notification Routing:** Critical priority (score >30) → Slack DM + email, High (20-30) → channel + email, Medium/Low → email only Tool Integrations:** Add Jira/Linear for ticket creation, Asana/Monday for project management, Salesforce/HubSpot for CRM logging, GitHub for issue creation Analytics:** Build dashboards for meeting effectiveness scores, action item velocity, recurring topic clustering, team productivity metrics Cost Optimization:** ~1,200 tokens/meeting × $0.002/1K (GPT-3.5) = $0.0024/meeting, use batch API for 50% discount, cache common patterns Once configured, this workflow becomes your team's institutional memory—capturing every commitment and decision while eliminating hours of weekly admin work, ensuring accountability is automatic and follow-through is guaranteed. 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.

AI Email Manager: Auto Summary, Labeling, and CRM Logging via n8n + Gemini Overview This workflow turns your Gmail inbox into a fully autonomous AI Email Agent that reads, summarizes, categorizes, and organizes emails in real-time. Built with n8n, Google Gemini, Notion, and Google Sheets, it’s perfect for founders, freelancers, and agencies who receive a ton of emails daily and want to automate the triage process without losing control. How It Works Gmail Trigger — Detects new incoming emails. Process Email Data — Extracts sender info, subject, and content in a clean structured format. AI Email Analyzer — Uses Gemini AI to summarize the email and decide the most relevant label (e.g., Project Updates, Client Requests, Invoices, etc.). Create Gmail Label (if not exists) — Dynamically creates a new label if the AI recommends one that doesn’t exist. AI Agent + Add Label to Email — Applies the correct Gmail label automatically using the message ID. Logs in Notion & Google Sheets — Every processed email (summary, sender, date, label) is logged for tracking and analytics. Who It’s For Entrepreneurs & Founders — Manage investor, client, and product update emails automatically. Agencies & Teams — Classify and track client emails effortlessly across projects. Freelancers & Consultants — Get AI summaries and organize leads without manually labeling emails. Tech Builders — Anyone building AI automation tools and SaaS products around inbox management.