Notion and Slack integration

Overview This template is ideal for photographers, graphic designers, and creative professionals who manage large volumes of visual assets. It is also perfect for Digital Asset Managers looking for a customizable, automated solution to organize files without manual tagging. What it does When a new image is uploaded to a designated "Inbox" folder in Google Drive, the workflow performs the following actions: AI Analysis**: Uses GPT-4o to analyze the image content, generating a description, extracting dominant colors, and determining the category (e.g., Portrait vs. Landscape). Safety Check**: Runs an AI-based NSFW filter. If inappropriate content is detected, the process stops, and a warning is sent to Slack. Smart Sorting**: Automatically moves the file into the correct subfolder based on its category. Contextual Tagging**: Generates specific tags (e.g., "smile, natural light" for portraits) and updates the file metadata. Archiving**: Creates a comprehensive entry in a Notion Database with the image link, tags, and description. Notification**: Sends a success alert to Slack with a summary of the archived asset. How to set up This workflow is designed to be plug-and-play using a central configuration node. Credentials: Connect your Google Drive, OpenAI, Notion, and Slack accounts in n8n. Set Variables: Open the node named "Workflow Configuration". Replace the placeholder IDs with your actual Folder IDs (for Inbox, Portraits, and Landscapes), Notion Database ID, and Slack Channel ID. Prepare Notion: Create a Database in Notion with the following properties: Category (Select) Description (Rich Text) Image URL (URL) Tags (Rich Text) Date (Date) Requirements n8n Version**: 1.0 or later. OpenAI API: Access to the **gpt-4o model is recommended for accurate vision analysis. Google Drive**: A specific folder structure (Inbox, Portraits, Landscapes). Notion**: A dedicated database for the portfolio. Slack**: A channel for notifications. How to customize Add Categories**: You can expand the "Category Router" (Switch node) to include more specific genres like "Architecture," "Macro," or "Street," and add corresponding paths. Adjust Prompts**: Modify the system prompts in the AI nodes to change the language of the output or the style of the generated tags. Change Output**: Connect to Airtable or Excel instead of Notion if you prefer a different database system.

📘 Description: This workflow automates sales performance tracking and motivational updates by integrating HighLevel CRM, Notion, GPT-4o, and Slack. It pulls all deals from HighLevel, cleans and summarizes sales data per representative, creates performance dashboards in Notion, and uses GPT-powered AI to generate personalized motivational Slack messages. It eliminates manual leaderboard tracking and boosts sales engagement with real-time insights and daily motivation — ensuring every sales rep stays informed, recognized, and inspired. What This Workflow Does (Step-by-Step) 🟢 Manual Trigger – Starts the automation manually for data refresh or testing. 📦 Fetch All Deals from HighLevel CRM – Retrieves all opportunities from HighLevel CRM, including deal names, reps, values, and stages for full visibility. 🔍 Validate Deal Fetch Success (IF Node) – Verifies that fetched data contains valid deal IDs. ✅ True Path: Continues to data cleaning. ❌ False Path: Logs failed records to Google Sheets for debugging. 🧹 Clean & Structure Deal Data – Normalizes raw deal data into a consistent schema (deal ID, rep ID, client name, value, status). Ensures clean inputs for analytics. 📊 Summarize Sales by Representative – Aggregates deals per sales rep and computes: Total deals handled Total deal value Total deals won Average deal value 🧾 Generate Notion Performance Dashboard – Creates personalized Notion dashboards for each rep with daily updated performance summaries and motivation metrics. ⚙️ Transform Data for AI Input – Converts summarized data into AI-readable format for GPT-4o processing. 🧠 GPT-4o Model Configuration – Sets up Azure OpenAI GPT-4o model to generate motivational and contextual Slack messages. 🤖 AI-Generated Motivational Slack Messages – Uses LangChain + GPT-4o to create energetic, emoji-filled messages that celebrate rep achievements and encourage improvement. 💬 Notify Sales Team in Slack – Sends the AI-generated performance summaries and motivational blurbs directly to each rep or the team Slack channel for transparency and engagement. 🚨 Log Fetch or Validation Errors (Error Handling) – Records any fetch or validation failures in the Google Sheets “error log sheet” for easy review and error management. Prerequisites HighLevel CRM API credentials Google Sheets for “Error Log” tracking Notion API integration for dashboards Azure OpenAI (GPT-4o) credentials Slack API connection for notifications Key Benefits ✅ Fully automated daily performance tracking ✅ Personalized AI-powered motivation in Slack ✅ Transparent visibility for managers and reps ✅ Improved accountability and sales performance ✅ Seamless integration across CRM, Notion, and Slack 👥 Perfect For Sales teams seeking real-time motivation and transparency Managers who want automated performance dashboards Teams using HighLevel CRM and Slack for daily operations Companies aiming to gamify sales productivity

Who is this for Team leads, project managers, and operations staff who want to automate meeting documentation. Useful for any team that records meetings and needs structured notes with clear action items. What this workflow does This workflow accepts a meeting recording upload via a web form. The recording is uploaded to Gemini Files API for audio analysis. Gemini AI generates a structured summary including key decisions, action items with assignees, and follow-up topics. A Notion page is created with the complete notes, and the team is notified on Slack with a summary and the action item list. Setup Add a Google Gemini API credential for file upload and audio analysis. Add a Notion API credential and create a database with columns: Title, Date, Summary, Action Items, Status. Add a Slack OAuth2 credential and set your meetings channel. Requirements Google Gemini API key (supports audio file analysis) Notion workspace with API integration enabled Slack workspace with OAuth2 app How to customize Edit the analysis prompt in "Analyze recording with Gemini" to focus on specific meeting types (standup, retrospective, planning). Change the Gemini model to a larger variant for longer recordings. Add a Google Calendar integration to automatically match recordings to calendar events. Important disclaimer AI-generated summaries may not capture every detail or nuance from the recording. Always review the notes before sharing externally or making decisions based on them.

Who is this for Customer support teams and operations managers who receive support requests via email and need automated triage. Works well for small to mid-size teams using Notion as their ticket tracker. What this workflow does This workflow watches a Gmail inbox for incoming support emails. Each email is analyzed by Gemini AI to determine its category (billing, technical, feature request, or general), priority level, and a suggested response draft. A new page is created in a Notion database with all classified fields. Critical tickets trigger an immediate Slack alert to the on-call team, while all tickets get a summary notification. Setup Add a Gmail OAuth2 credential and configure label or address filters. Add a Google Gemini API credential for email classification. Add a Notion API credential and create a database with columns: Title, Category, Priority, Status, Summary. Add a Slack OAuth2 credential and set your alerts channel. Requirements Gmail account with OAuth2 access Google Gemini API key Notion workspace with API integration enabled Slack workspace with OAuth2 app How to customize Edit the AI prompt in "Classify ticket with AI" to add more categories or adjust priority rules. Change the critical priority condition in "Is critical priority" to include high-priority tickets. Replace Notion with Airtable or Google Sheets for a different ticket backend.

Run automated daily standups using Slack, Notion, and Redis 📌 Overview This workflow fully automates your team's daily standup process using Slack for communication, Notion for structured data storage, and Redis for real-time session management. It automatically sends standup questions to active team members, collects and stores their responses, manages conversation sessions, and generates structured summary reports for managers. Morning and evening standups run on schedule without manual intervention. Redis ensures fast and reliable session tracking, prevents duplicate standups, and maintains conversation state. All responses are securely stored in Notion for long-term reporting and tracking. This workflow eliminates manual follow-ups, improves reporting consistency, and gives managers full visibility into team progress, blockers, and attendance. ⚙️ How it works This workflow runs automatically based on configured schedules. Morning standup Fetches active team members from the Notion database Creates standup sessions in Redis Sends standup questions to each team member via Slack direct message Stores responses in Notion Tracks session state using Redis Automated reports The workflow automatically generates: Morning summary report showing attendance, responses, and blockers Evening summary report showing accomplishments, completion status, and help requests Both reports are automatically sent to the Slack admin channel. Redis ensures session tracking and prevents duplicate standups. 🛠 Setup steps Import this workflow into n8n Connect your Slack credentials Connect your Notion credentials Connect your Redis credentials Configure your Notion database IDs Configure your Slack admin channel ID Activate the workflow The workflow will run automatically based on the configured schedule. 🚀 Features Automated standup management Automatically sends standup questions Tracks team responses Stores responses securely in Notion Prevents duplicate standup sessions Automated reporting Attendance tracking Task completion tracking Blocker detection Missing response detection Automatic Slack summary reports 📋 Requirements You need the following accounts: n8n Slack Notion Redis 🎯 Benefits Fully automated standup system No manual follow-ups required Automatic attendance tracking Identifies blockers early Improves team visibility Saves management time 👨‍💻 Author BytezTech Pvt Ltd

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.

LinkedIn Inbox Triage (Gmail Label to Notion + Slack) This n8n template demonstrates how to use AI to triage LinkedIn emails in your Gmail inbox, so you only see the messages worth your time. It filters out automated noise, scores sales likelihood, drafts quick replies for real conversations, stores everything in Notion, and sends you a Slack DM for items you should answer quickly. Good to know This workflow sends email content to an LLM. Do not use it with sensitive mailboxes unless you are comfortable with that. Cost depends on your model choice and token usage. The body is currently limited to 4000 characters to control spend. If you want a shorter run window, adjust the receivedAfter filter. How it works Runs on a daily schedule. Pulls emails from Gmail using a label you define (example: LinkedIn). Applies two filters: Keeps only invitations and messages Removes common automated notifications Fetches the full email body for better classification. Sends the message to an AI agent that returns strict structured JSON: action (reply_quick, review, ignore, block) relevancy_score (0 to 100) sales_likelihood (0 to 1) summary optional reply_draft Applies a quality gate to keep high signal messages. Writes the output to a Notion database as a ticket. Sends a Slack DM only for items marked reply_quick. How to use Create a Gmail label that captures LinkedIn emails, then add the label id to the Gmail node. Create a Notion database with fields matching the Notion node mapping. Connect your OpenAI, Gmail, Notion, and Slack credentials in n8n. Run once manually to verify mapping, then enable the workflow. Requirements Gmail account OpenAI API credentials (or compatible model node) Notion database Slack account Customising this workflow Make it more aggressive by increasing the sales threshold or raising the relevancy cutoff. Add more filter phrases for your own LinkedIn email language. Swap Slack DM for a channel post, or send a daily digest instead of per message. Add a redaction step before the AI node if you want to remove signatures or quoted replies.

AI job application tracker and interview prep assistant Categories: AI, Productivity, Career Transform your job search from chaos to clarity. This workflow automatically tracks every application, researches companies, and prepares you for interviews with AI-generated materials — all saved to a visual Notion pipeline. Benefits Never lose track of applications** — Every job gets logged automatically with status tracking Walk into interviews prepared** — AI generates likely questions, talking points, and company insights Save 2-3 hours per application** — Research and prep that took hours now happens in seconds Automated follow-up reminders** — Get notified when it's time to send that follow-up email How It Works Submit application via form (paste job URL) or forward your confirmation email AI extracts job details — company, role, requirements, salary, location Interview prep generates — likely questions, suggested talking points, questions to ask Everything saves to Notion — visual pipeline with follow-up dates Daily reminders — Slack notification for applications needing follow-up Required Setup Notion Database Structure Create a Notion database with these properties: | Property Name | Type | Purpose | |---------------|------|---------| | Company | Title | Company name | | Role | Text | Job title | | Status | Select | Applied, Interviewing, Offer, Rejected, Ghosted | | Applied Date | Date | When you applied | | Salary Range | Text | Compensation info | | Job URL | URL | Link to posting | | Location | Text | City/Remote | | Interview Prep | Text | AI-generated prep materials | | Follow Up Date | Date | When to follow up | | Requirements | Text | Key job requirements | | Notes | Text | Your personal notes | Credentials Needed OpenAI API** — For job extraction and interview prep generation Notion** — Connected to your job tracker database Gmail** (optional) — For email forwarding and confirmations Slack** (optional) — For follow-up reminders Use Cases Active job seekers** — Track 20+ applications without spreadsheet chaos Career changers** — Get AI help understanding new industry requirements Recent graduates** — Build interview confidence with generated prep materials Passive searchers** — Keep a running list with minimal effort Set Up Steps Import the workflow into your n8n instance Create Notion database with the structure above (or duplicate template) Connect OpenAI credentials — API key with GPT-5 access recommended Connect Notion credentials — Select your job tracker database Configure Gmail trigger (optional) — Set filter for forwarded job emails Set up Slack webhook (optional) — Choose channel for reminders Test with a sample job posting — Paste a LinkedIn or company careers page URL Customization Tips Edit the interview prep prompt to mention your background/experience Adjust the follow-up reminder interval (default: 7 days) Add additional research sources (LinkedIn, Crunchbase) for richer company data Connect to calendar to block interview prep time automatically Technical Notes Uses Jina AI Reader for web scraping (free tier available) GPT-5-mini recommended for cost efficiency Notion text fields limited to 2000 characters (full prep saved) Daily check runs at 9 AM (configurable) Difficulty Level: Intermediate Estimated Setup Time: 30-45 minutes Monthly Operating Cost: ~$2-5 (based on 50 applications/month with GPT-5-mini)

🧾 An intelligent automation system that turns Google Meet recordings into structured meeting notes — integrating Fireflies.ai, OpenAI GPT-4.1-mini, Notion, Slack, Google Drive, and Gmail via n8n. 🎥 Demo: Watch the Loom walkthrough ⚙️ What It Does The Google Meet Notes Generator & Distributor automates the entire post-meeting workflow. Workflow Summary: Fetches Google Meet transcript via Fireflies.ai webhook. Aggregates and summarizes transcript using OpenAI GPT-4.1-mini into: Title Summary Decisions Action Items Risks Questions Stores the transcript as a text file on Google Drive and generates a shareable link. Creates a Notion page with all the meeting details. Posts the summary in #meeting Slack channel. DMs each attendee on Slack with personalized meeting notes. Sends email recap to all attendees via Gmail. Result: No more manual note-taking or scattered updates — everything centralized, formatted, and instantly shareable. 💡 Use Cases | Scenario | Description | | --------------------------- | --------------------------------------------------------------------------------------- | | Team Meeting Summaries | Automatically summarize and distribute meeting notes for internal teams. | | Project Management | Keep structured decisions, action items, and risks documented for each project meeting. | | Remote Teams | Notify distributed teams in Slack and via email without extra effort. | | Client Updates | Share polished meeting summaries with clients instantly. | | Knowledge Base / Notion | Archive structured notes in Notion for reference and compliance. | 🔧 Setup Accounts and Tools Needed | Tool | Purpose | | -------------------------- | ---------------------------------------------- | | 🤖 Fireflies.ai API | Fetch Google Meet transcripts via webhook | | 🧠 OpenAI API | Summarize and structure transcript into notes | | 📓 Notion API | Create structured meeting pages | | 💬 Slack OAuth/Bot | Post summaries in channel and DM attendees | | 🗂 Google Drive OAuth2 | Store transcripts and generate shareable links | | ✉️ Gmail OAuth2 | Email meeting recaps to attendees | Fireflies.ai Setup Get API key from Fireflies.ai. Configure n8n → Credentials → Fireflies API. Ensure webhook triggers are set to send meetingId to n8n. OpenAI Setup Generate API key at OpenAI. Add to n8n → Credentials → OpenAI API. Use model GPT-4.1-mini in Agent and Generate Slack Message nodes. Notion Setup Create a Notion integration and share your workspace. Add API token in n8n → Credentials → Notion API. Map workspace/page IDs to Notion Page node. Slack Setup Create Slack Bot in workspace with chat:write and users:read permissions. Add OAuth token in n8n → Credentials → Slack API. Connect to Send a message #meeting and DMs to Attendees nodes. Google Drive Setup Create a folder for transcripts. Enable Google Drive API in Google Cloud Console. Add OAuth2 credentials to n8n → Google Drive. Gmail Setup Enable Gmail API in Google Cloud. Add OAuth2 credentials in n8n → Gmail. Connect to Email to Attendees node. n8n Workflow Setup Import provided n8n workflow JSON. Configure all credentials: Fireflies, OpenAI, Notion, Slack, Google Drive, Gmail. Activate workflow. Test by sending a meeting ID via webhook. Workflow automatically: Fetch → Summarize → Store → Notion → Slack → DM → Email 🧠 Result A fully automated AI pipeline that transforms Google Meet recordings into polished, shareable meeting notes — eliminating manual note-taking and keeping your team informed in real time. 📞 Support & Contact If you face any issues during setup or execution, contact: 📧 Email: [email protected] 🔗 LinkedIn: Atharva Jaiswal

Automatically backs up your workflows to Github and generates documentation in a Notion database. Weekly run, uses the "internal-infra" tag to look for new or recently modified workflows Uses a Notion database page to hold the workflow summary, last updated date, and a link to the workflow Uses OpenAI's 4o-mini to generate a summarization of what the workflow does Stores a backup of the workflow in GitHub (recommend a private repo) Sends notification to Slack channel for new or updated workflows Who is this for Anyone seeking backup of their most important workflows Anyone seeking version control for their most important workflows Credentials required N8N: You will need an N8N credential created so the workflow can query the N8N instance to find all active workflows with the "internal-infra" tag Notion: You will need an Notion credential created OpenAI: You will need an OpenAI credential, unless you intend on rewiring this with your AI of choice (ollama, openrouter, etc.) GitHub: You will need an GitHub credential Slack: You will require an Slack credential, recommend a Bot / access token configuration Setup Notion Create a database with the following columns. Column type is specified in [type]. Workflow Name [text] isActive (dev) [checkbox] Error workflow setup [checkbox] AI Summary [text] Record last update [date/time] URL (dev) [text/url] Workflow created at [date/time] Workflow updated at [date/time] Slack Create a channel for updates to be posted into Github Create a private repo for your workflows to be exported into N8N Download & install the template Configure the blocks to use your N8N, Notion, OpenAI & Slack credentials for your own Edit the "Set Fields" block and change the URL to that of your N8N instance (cloud or self-hosted) Edit the "Add to Notion" action and specify the Database page you wish to update Edit the Slack actions to specify the Channel you want slack notifications posted to Edit the GitHub actions to specify the Repository Owner & Repository Name Sample output in Notion Workflow diagram

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

Who is this for? Teams that want to capture important Slack messages in Notion with smart categorization. Perfect for knowledge workers, community managers, or any team that needs to preserve valuable conversations from Slack and organize them automatically in a Notion database. What problem does this solve? Important Slack messages get buried in chat history and are hard to find later. This workflow monitors your Slack channel and automatically saves starred messages to Notion with AI-generated titles and smart tags. No more manually copying messages or losing track of important discussions. How it works Trigger - Schedule Trigger fires every 10 minutes to check for new messages. Get Slack Messages - fetches recent messages from your specified Slack channel within the last 10 minutes. Star Filter - only processes messages that have been reacted to with a ⭐ emoji (configurable to any emoji). Get Message Link - retrieves the permanent link to the starred Slack message. Choose Notion DB - connects to your target Notion database and loads available tag options. Set Tags - prepares the available tags from your Notion database for AI processing. AI Processing - uses OpenAI GPT-4o-mini to: Generate a concise title (under 50 characters) Automatically categorize the message with existing tags (90%+ confidence threshold) Create Notion Page - saves the message to Notion with: AI-generated title Auto-selected tags Original message content Permanent link back to Slack Setup steps Import and connect credentials Import this template into n8n Connect your Slack API credentials (Slack Bot Setup Guide) Connect your Notion API token (Notion Integration Guide) Connect your OpenAI API credentials Configure Slack integration Create a Slack bot and add it to your target channel Update the channelId in "Get Slack Messages" node with your channel ID Ensure your bot has these permissions: channels:history - to read channel messages reactions:read - to detect star reactions chat:write.public - to get message permalinks Slack Bot Setup Resources: Creating a Slack App Bot Token Scopes Adding Apps to Channels Set up Notion database Create or use existing Notion database with required properties: Tags (Multi-select) - add tag options with descriptions for better AI accuracy Link (URL) - for storing Slack permalink Title (Title) - will be auto-populated by AI Update the databaseId in "Choose Notion DB" and "Create Notion Page" nodes Customize the workflow Change trigger emoji**: Edit the IF condition to use a different emoji (e.g., bookmark, pushpin) Adjust timing**: Modify the Schedule Trigger interval (remember to update the "oldest" filter in Get Slack Messages to match) Improve AI prompts**: Edit the prompt in "Write Title & Tag" node for better categorization Test the setup Star a message in your Slack channel Wait for the next 10-minute trigger or manually execute the workflow Check your Notion database for the new entry Example output Slack message: > "Hey team, just found this amazing tool for automating our design workflow. We should definitely consider it for next sprint: https://example.com/design-tool" Generated Notion page: Title:** "Design Tool Recommendation for Next Sprint" Tags:** "Tools", "Design", "Sprint Planning" Content:** Full message text with Slack permalink Link:** Direct link back to original Slack message Extending the flow Multi-channel support - duplicate the "Get Slack Messages" node for different channels and merge the outputs. Enhanced AI processing - modify the prompt to extract additional metadata like: Priority levels Action items Mentioned team members Due dates Rich content preservation - add logic to handle Slack attachments, images, or threaded replies. Notification system - add nodes to notify team members when important messages are archived. Sentiment analysis - incorporate additional AI processing to categorize message sentiment or urgency. This template provides a lean setup for intelligent Slack-to-Notion archiving. Star important messages, let AI handle the organization, and never lose track of valuable conversations again.

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

CallForge - AI Gong Sales Call Processing Workflow Automate your Gong.io sales call analysis with AI-driven insights, real-time tracking, and structured CRM integration. Who is This For? This workflow is designed for: ✅ Sales teams looking to automate sales call processing. ✅ Revenue operations (RevOps) professionals managing high volumes of call data. ✅ AI-driven sales intelligence teams using Gong.io for data-driven insights. What Problem Does This Workflow Solve? Manually managing and analyzing large volumes of Gong call data is time-consuming and error-prone. With CallForge, you can: ✔ Automate call processing to scale AI-driven insights. ✔ Integrate with Notion to track and organize sales call data efficiently. ✔ Get real-time Slack updates to stay informed on call processing progress. ✔ Handle API failures gracefully, allowing easy reruns if a rate limit is hit. ✔ Ensure AI-ready analysis, feeding structured call data into an AI-powered system. What This Workflow Does Triggers on New Gong Calls Captures new Gong calls and retrieves metadata, call summaries, and participant details. Compares Calls Against Notion Database Checks whether the call has already been processed and stored in Notion. Prevents duplicate entries** from being added. Creates a Parent Notion Record for AI Processing Stores call details such as date, title, URL, company name, sales rep, and opportunity details in Notion. Links calls to Salesforce Opportunity (SF Opp) data. Assigns sales representatives and customer information to each call. Loops Through Calls for Processing Ensures resilience* by allowing failed runs to restart where they left off*. Processes calls one at a time to prevent Notion rate limits. Sends Call Data to an AI Processor Extracts structured call details and sends them to an AI-powered analysis workflow. Allows multiple AI agents to process and extract structured data from calls. Provides Real-Time Slack Alerts Posts a progress update in Slack when the queue starts processing. Sends real-time call progress notifications. Sends a completion alert once all calls are processed. How to Set Up This Workflow Connect Your APIs 🔹 Gong API Credentials – Ensure you have valid Gong API credentials in n8n. 🔹 Notion Database – Provide access to a Notion database for storing call insights. 🔹 Slack Integration – Configure a Slack channel for progress alerts. 🔹 AI Processing Workflow – Connect an AI-powered call processing workflow for final analysis. 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 How to Customize This Workflow 💡 Modify Call Storage – Swap Notion for a different CRM or database (e.g., HubSpot, Airtable, Salesforce). 💡 Change AI Processing – Integrate a custom AI model for analyzing sales conversations. 💡 Customize Slack Notifications – Adjust Slack messages or send alerts via email instead. 💡 Expand with More Integrations – Connect with Salesforce, Pipedrive, or HubSpot for further enrichment. Why Use CallForge? 🚀 Automate Gong call tracking for seamless sales intelligence. 📊 Improve sales operations with structured, AI-powered insights. ⚡ Get real-time updates and keep your team informed instantly. Start optimizing your Gong call processing today!

📘 Description This workflow is an AI-driven FX concept generation pipeline that transforms a single VFX brief into multiple high-quality simulation-ready video concepts. It automates ideation, rendering, storage, and team review—bridging the gap between creative direction and simulation execution. ⚙️ Step-by-Step Flow The process begins with a webhook trigger that serves as the FX brief intake layer, receiving a POST request containing the core FX brief, shot code, and optional parameters such as FX type, scale, intensity, and camera details. This input then moves through a validation and normalization stage, where required fields are verified and key attributes—such as FX type (fire, smoke, explosion), camera movement, frame range, FPS, scale, intensity, and speed—are standardized for consistency. Following this, the system performs prompt engineering and fans out the single brief into four creative variations: a primary reference (balanced), a high-intensity version (extreme simulation), a subtle version (controlled low-intensity FX), and an alternate camera variation offering a different perspective. Each variation is enriched with detailed cinematic instructions, including camera behavior, speed dynamics, and frame timing. At the core of the workflow, a dynamic generation mode determines whether to use image-to-video (if a reference image is provided) or text-to-video (if not), ensuring flexibility across both concepting and plate-matching use cases. Each variation is then submitted as an independent job to the Seedance API for AI rendering, returning unique job IDs for asynchronous tracking. A polling system manages execution by checking the job status every 20 seconds and continues until rendering is complete, handling each variation independently. Once completed, the system structures detailed metadata for each asset, including the video URL, FX type, scale, intensity, camera movement, frame specifications, and relevant tags for tracking and review. The asset storage pipeline then downloads the generated videos, uploads them to Google Drive using a structured naming convention, and logs all associated metadata into a Notion database for organized tracking. An aggregation layer consolidates all variations into a single structured output, combining video links, Notion records, and technical metadata. Finally, a Slack review dispatch sends a well-formatted message to the FX team, presenting all variations in one place with direct video previews, along with a technical breakdown covering scale, intensity, camera settings, and FPS, as well as Notion links for streamlined tracking and review. 🚨 Error Handling • Global error trigger • Sends Slack alert with failure details • Ensures no lost jobs or silent failures 🧩 Prerequisites • Seedance API (AI video generation) • Google Drive OAuth2 • Notion API • Slack OAuth2 • Webhook integration 💡 Key Benefits ✔ Rapid FX concept iteration (4 variations instantly) ✔ Structured prompt engineering for consistent outputs ✔ Automatic handling of camera, timing, and simulation context ✔ Integrated storage (Drive + Notion) ✔ Centralized team review via Slack ✔ Supports both concept art and simulation previsualization 👥 Perfect For VFX studios Simulation teams (Houdini, FX artists) Previsualization pipelines Creative direction teams AI-assisted film production systems

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

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

🚀 How it works Fully automates your Day 0–30 employee onboarding sequence the moment HR submits a webhook. No manual steps, no missed tasks. 🔐 Provisions Google Workspace account via Admin API 💬 Posts a personalised welcome message to Slack 📝 Creates a Notion onboarding page pre-filled with the employee's details 📧 Sends a welcome email via Gmail with first-day instructions ⏱️ Waits 7 days, then checks task completion — alerts the manager if anything is overdue ✅ Waits 30 days, runs a final completion check and closes the onboarding loop 🛠️ Set up steps Estimated setup time: ~20 minutes Webhook — copy the webhook URL and send it from your HR system (BambooHR, HiBob, Workday, or a simple form) Google Workspace — connect a Service Account with Domain-Wide Delegation; grant admin.directory.user scope Slack — connect Slack OAuth2; set the welcome channel in the node (e.g. #general) Notion — connect Notion OAuth2; set your Onboarding database ID in the Create Page node Gmail — connect Gmail OAuth2; customise the welcome email template in the Send Email node Follow the sticky notes inside the workflow — each key node has a one-liner guide 📋 Prerequisites Google Workspace (Business Starter or higher) Slack workspace with a bot or OAuth2 app Notion workspace with an onboarding database Gmail account for sending welcome emails Custom Workflow Request with Personal Dashboard [email protected] https://www.smartflowcraft.com/contact More free templates https://www.smartflowcraft.com/n8n-templates

Description Execute email actions directly from Notion. Set an email’s status to Responded, Delegated, Routed, or Archived, and this workflow handles the Gmail action, Slack notification, or Jira routing automatically. Context This is the action layer for the Inbox Zero Engine. When you set an email’s status in Notion, the workflow executes the appropriate action: • Responded: sends the draft reply via Gmail thread • Delegated: forwards the email + sends a Slack DM to the delegate • Routed: creates items in Jira, RICE+ backlog, or customer health • Archived: applies Gmail labels After each action, the entry is marked as “Processed” in Notion. Who is this for? • PMs using Notion as their command center • Anyone who wants to process email without leaving Notion • Teams that delegate and route emails frequently Requirements • Notion account with Email Intelligence database • Gmail OAuth2 • Slack Bot token How it works Trigger Watches Email Intelligence in Notion for status changes. Action Router 4-way switch: Responded sends reply, Delegated forwards + DMs, Routed creates tickets, Archived labels in Gmail. Closed Loop Updates each entry to “Processed” with timestamp and reference. What you get • One-click email actions from Notion • Automatic Gmail replies, forwards, and archiving • Slack notifications for delegated emails • Full audit trail in Notion About me : I’m Yassin a Product Manager Scaling tech products with data-driven project management. 📬 Feel free to connect with me on Linkedin

Description AI-powered priority re-evaluation every 2 hours. Analyzes new signals, meeting decisions, emails, and blockers, then runs 3 AI passes (Impact, Urgency, Final Ranking) to suggest re-ranking. Only updates when the ranking actually changes. Context Runs every 2 hours during work days (8:00–18:00). Pulls 5 data sources in parallel: open priorities, recent high-impact signals, today’s meeting decisions, urgent emails, and overdue/blocked actions. A Priority Context Matrix links each priority to relevant new information. Three sequential AI passes score Impact, Urgency, and produce a Final Ranking with rationale. CompareDatasets detects changes vs current ranking. Only if the ranking changed, Notion is batch-updated and Slack shows before/after. Who is this for? • PMs managing dynamic priority stacks • Product leaders who need real-time priority alignment • Teams where priorities shift frequently due to customer signals Requirements • Notion account with PM Daily databases • OpenAI API key • Slack Bot token How it works Trigger Runs every 2 hours, Monday–Friday, 8:00–18:00. Context Collection 5 parallel pulls: open priorities, signals, meetings, emails, blocked actions. Priority Matrix Links each priority to relevant signals, emails, and decisions. Deduplicates and normalizes. 3-Pass AI Scoring Pass 1: Impact. Pass 2: Urgency. Pass 3: Final Ranking with rationale. Change Detection Compares new vs current ranking. If changed: batch-updates Notion and posts before/after to Slack. What you get Continuous priority re-evaluation every 2 hours 3-pass AI scoring (Impact, Urgency, Final) Change detection — only updates when needed Before/after ranking comparison on Slack 40+ node workflow with CompareDatasets intelligence About me : I’m Yassin a Product Manager Scaling tech products with data-driven project management. 📬 Feel free to connect with me on Linkedin

Research competitors and generate market insights with Claude AI and Notion Who is this for SaaS product managers, startup founders, and marketing teams who need to stay informed about competitor movements without manual monitoring. Perfect for teams who want to automate competitive intelligence gathering and respond quickly to market changes. How it works The workflow runs weekly, automatically scraping competitor websites and pricing pages using HTTP requests. A code node extracts key content and creates content hashes to detect changes from previous scans. When changes are detected, Claude AI analyzes the updates and provides strategic insights about pricing shifts, feature launches, or messaging changes. All competitor data and AI analysis are automatically saved to a Notion database for historical tracking. Important changes trigger immediate Slack notifications with actionable insights. At the end of each week, a comprehensive report summarizing all competitor activity is generated and emailed to your team. How to set up Configure competitor URLs in the Set node by adding websites, pricing pages, and feature pages you want to monitor. Set up API credentials for Claude AI, Notion, Slack, and Gmail. Create a Notion database with properties for competitor name, URL, content hash, AI analysis, and scan date. Define environment variables for your Notion database ID, Slack channel, and team email list. Requirements Anthropic Claude API key for competitive analysis Notion workspace with API access for data storage Slack workspace for urgent alerts Gmail account for weekly reporting Basic HTML/CSS knowledge helpful for customizing content extraction How to customize Adjust the schedule trigger frequency, modify urgent notification keywords in the priority evaluation code, or customize the Claude AI analysis prompt to focus on specific competitive aspects like pricing, features, or market positioning.

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.

This n8n template from Intuz provides a complete and automated solution for preparing and delivering context-rich briefings directly to attendees before every meeting. It acts as an AI-powered executive assistant, gathering relevant information from all your key work tools to ensure everyone arrives prepared and aligned. Who's this workflow for? Engineering Managers & Team Leads Product Managers & Project Managers Scrum Masters & Agile Coaches Any team that holds regular status, planning, or technical meetings. How it works Trigger on New Calendar Event: The workflow starts automatically whenever a new meeting is created in a designated Google Calendar. Fetch Previous Context: It immediately connects to Notion to retrieve the notes from the most recent past meeting, ensuring continuity. Wait for the Right Moment: The workflow calculates a time 15 minutes before the meeting's scheduled start and pauses its execution until then. Gather Real-Time Project Data: Just before the meeting, the workflow wakes up and: Extracts keywords from the meeting title. Searches GitHub for recent Pull Requests (PRs) relevant to those keywords. Searches Jira for any tickets or issues that match the meeting's topic. Build the Intelligent Briefing: It assembles all the gathered information—previous notes from Notion, current PRs from GitHub, and relevant tickets from Jira—into a single, beautifully formatted Slack message. Deliver to Each Attendee: The workflow identifies all attendees from the Google Calendar invite, finds their corresponding Slack profiles via email, and sends the personalized briefing as a Direct Message (DM) to each one, ensuring everyone is prepared just in time. Key Requirements to Use This Template n8n Instance: An active n8n account (Cloud or self-hosted). Google Calendar Account: To trigger the workflow on new events. Notion Account: With a dedicated database for storing meeting notes. GitHub Account: To search for relevant pull requests. Jira Cloud Account: To search for relevant project tickets. Slack Workspace & App: A Slack workspace where you have permission to install an app. You will need a Bot Token with the necessary permissions. Setup Instructions Google Calendar Trigger: In the "Capture New Google Calendar Event" node, connect your Google Calendar account and select the calendar you want to monitor. Notion Connection: In the "Get Last Meeting Notes" node, connect your Notion account. Select the Notion Database ID that contains your meeting notes. GitHub & Jira Connections: In the "Get PRs from Repo" node, connect your GitHub account and select the repository to search. In the "Get Jira Issues Related to Meeting" node, connect your Jira Cloud account. You can customize the JQL query if needed. Slack Configuration (Crucial Step): Create a Slack App: Go to api.slack.com/apps, create a new app, and install it to your workspace. Set Permissions: In your app's "OAuth & Permissions" settings, add the following Bot Token Scopes: chat:write (to send messages) and users:read.email (this is critical for looking up attendees). Reinstall the app to your workspace. Get Bot Token: Copy the "Bot User OAuth Token" (it starts with xoxb-). Connect in n8n: In the "Get User Slack Info from Email" node, click "Header Parameters" and replace {{ slack oauth token }} with your actual Bot Token. In the "Send Meeting Context in Slack DM" node, connect your Slack credentials using the same Bot Token. Activate the Workflow: Save the workflow and toggle the "Active" switch to ON. Your automated pre-meeting bot is now live! Connect with us Website: https://www.intuz.com/n8n-workflow-automation-templates Email: [email protected] LinkedIn: https://www.linkedin.com/company/intuz Get Started: https://n8n.partnerlinks.io/intuz For Custom Workflow Automation Click here: Get Started

This n8n template helps you turn inbound messages into a clean, deduped queue of actionable tickets. It includes Slack and Gmail as ready to use examples, but the key idea is the universal intake normalizer: you can plug in other sources later (forms, webhooks, chat tools, other inboxes) as long as you map them into the same normalized schema. Good to know This workflow sends message content to an LLM for classification. Keep sensitive data out of the prompt, and only process messages you are allowed to process. Costs depend on message volume and length, so truncation and tight filters matter. How it works Collect inbound items (Slack and Gmail are included as examples). Normalize each item into one shared JSON format so every source behaves the same. Deduplicate items using a data table so repeats are skipped. Use an AI agent with structured output to score urgency and importance, produce a summary, and draft a reply. Create a Notion ticket for tracking, and optionally notify Slack for high priority items. Setup steps Connect credentials for Slack, Gmail, Notion, and your LLM provider. Choose your Slack channel and set a Gmail filter that keeps volume manageable. Select your Notion database and ensure properties match the field mappings. Create or select a data table and map the unique ID column for deduplication. Adjust the notification threshold and schedule interval to match your workflow. Requirements Slack workspace access (optional if you swap the source) Gmail access (optional if you swap the source) Notion database for ticket creation LLM API credentials Customising this workflow Add new sources by mapping them into the normalizer schema. Truncate long messages before the AI step to reduce cost. Change categories, scoring, and thresholds to match your operating model.

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

⚖️ HR Sovereign: AI-Powered Onboarding Hub A high-fidelity employee onboarding engine: Intake → Role-Based Enrichment → AI Personalization → IT Provisioning. ⚙️ Core Sovereign Logic Enrichment:** Auto-classifies Tech, Sales, and Leadership roles to drive specific logic tracks. Intelligence:* Uses AI Agent (GPT-4)* to generate personalized welcome messaging based on job DNA. Atomization:* Merge PDF* node assembles role-specific policies and benefits into a single high-res package. Provisioning:* Dynamically generates Jira hardware/access tickets and Notion* tracking dashboards. Delivery:* Sends branded HTML emails via Gmail and announces hires on Slack*. 📋 Setup & Prerequisites Intake: Connect your HRIS (BambooHR/Workday) to the Webhook URL. Assets: Organize Drive folders into "Technical", "Leadership", and "Standard" templates. Tracking: Connect your Notion Onboarding Database and Jira IT Project. Metrics: Time_to_Provision, Engagement_Score, Document_Integrity_Hash.

Who is this for? Agencies, consultants, and service providers who conduct discovery calls and need to quickly turn conversations into professional proposals. What it does: This workflow transforms meeting transcripts into complete, professional quotes using a sophisticated multi-agent AI architecture. It handles the entire quote lifecycle: from transcript analysis to client signature and onboarding. How it works: Trigger: Google Drive detects a new VTT/transcript file in a designated folder Extraction: The transcript is cleaned and parsed, then matched with calendar data to identify the client AI Analysis: A main orchestrator agent analyzes the call and delegates tasks to specialized sub-agents: SOW Agent: Generates problems, solutions, and action items Pricing Agent: Creates competitive pricing based on service catalog and market research Document Creation: PandaDoc API creates the quote with all tokens populated Review & Approval: Quote is sent to Slack for human review with approve/reject buttons Delivery: Approved quotes are sent via Gmail with custom HTML templates Post-Signature: Webhook triggers CRM update and welcome email upon signature Key Features: Multi-agent architecture with specialized AI agents Automatic pricing calculation with 80%+ margin targeting Market research integration via Perplexity API Human-in-the-loop approval via Slack Professional HTML email templates CRM integration (Notion) for client status tracking Requirements Google Drive account (for transcript storage) Google Calendar (for meeting context) PandaDoc account (for quote generation) OpenRouter API (for LLM access - Claude/GPT models) Perplexity API (for market research) Slack workspace (for approval workflow) Gmail account (for client communication) Notion database (for CRM) Setup Instructions Configure Google Drive trigger folder Set up PandaDoc template with required tokens Add API credentials for OpenRouter and Perplexity Connect Slack workspace for approval notifications Configure Gmail for outbound emails Set up Notion CRM database with required properties

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

Create FAQ articles from Slack threads to Notion and Zendesk This workflow helps you capture "tribal knowledge" shared in Slack conversations and automatically converts it into structured documentation. By simply adding a specific reaction (default: 📚) to a message, the workflow aggregates the thread, uses AI to summarize it into a Q&A format, and publishes it to your knowledge base (Notion and Zendesk). Who is this for? Customer Support Teams** who want to turn internal troubleshooting discussions into public help articles. Knowledge Managers** looking to reduce the friction of documentation. Development Teams** wanting to archive technical decisions made in Slack threads. What it does Trigger: Watches for a specific emoji reaction (📚 :book:) on a Slack message. Data Collection: Fetches the parent message and all replies in the thread to get the full context. AI Processing: Uses OpenAI to analyze the conversation, summarize the solution, and format it into a clear Question & Answer structure. Publishing: Creates a new page in a Notion database with tags and summaries. (Optional) Drafts a new article in Zendesk. Notification: Replies to the original Slack thread with links to the newly created documentation. Requirements n8n** (Self-hosted or Cloud) Slack** workspace (with an App installed that has permissions to read channels and reactions). OpenAI** API Key. Notion** account with an Integration Token. Zendesk** account (optional, can be removed if not needed). How to set up Configure Credentials: Set up authentication for Slack, OpenAI, Notion, and Zendesk in n8n. Setup Notion: Create a database in Notion with the following properties: Name (Title) Summary (Text/Rich Text) Tags (Multi-select) Source (URL) Channel (Select or Text) Update Configuration Node: Open the Workflow Configuration1 node (Set node) and replace the placeholder values: slackWorkspaceId: Your Slack Workspace ID (e.g., T01234567). notionDatabaseId: The ID of your Notion database. zendeskSectionId: (Optional) The ID of the section where articles should be created. Slack App Scopes: Ensure your Slack App has the following scopes: reactions:read, channels:history, groups:history, chat:write. How to customize Change the Trigger:* If you prefer a different emoji (e.g., 📝 or 💡), update the "Right Value" in the IF - :book: Reaction Check* node. Modify the Prompt:* Edit the OpenAI* node to change how the AI formats the answer (e.g., ask it to be more technical or more casual). Remove Zendesk:* If you don't use Zendesk, simply delete the Zendesk node and remove the reference to it in the final Slack - Notify Completion* node.

Overview This workflow turns a single YouTube video into multiple content formats and publishes them across different platforms with an optional human approval step. It helps content creators, marketers, and agencies repurpose long-form video content into blog posts and social media updates automatically. How it works Fetches the transcript from a YouTube video Uses AI to generate blog and social media content Optionally waits for manual approval Publishes content to selected platforms Logs the result for tracking Setup steps Add your API credentials (AI, transcript, and social platforms) Paste a YouTube video URL Choose auto-publish or approval mode Run the workflow Use cases Content repurposing for YouTube creators Automated blog and social media publishing Marketing automation for agencies AI-assisted content production pipelines 🧑‍💻 Creator Information Developed by: Adem Tasin 🌐 Website: ademtasin.com 💼 LinkedIn: Adem Tasin

Description Automatically triage Product UAT feedback with AI, deduplicate it against your existing Notion backlog, create/update the right Notion item, and close the loop with the tester (Slack or email). This workflow standardizes incoming UAT feedback, runs AI classification (type, severity, summary, suggested title, confidence), searches Notion to prevent duplicates, and upserts the roadmap entry for product review. It then confirms receipt to the tester and returns a structured webhook response. Context Feature requests often arrive unstructured and get lost across channels. Product teams waste time re-triaging the same ideas, creating duplicates, and manually confirming receipt. This workflow ensures: Faster feature request triage Fewer duplicates in your roadmap/backlog Consistent structure for every feedback item Automatic tester acknowledgement Full traceability via webhook response Who is this for? Product Managers running UAT or beta programs Product Ops teams managing a roadmap backlog Teams collecting feature requests via forms, Slack, or internal tools Anyone who wants AI speed with clean backlog hygiene Requirements Webhook trigger (form / Slack / internal tool) OpenAI account (AI triage) Notion account (roadmap/backlog database) Slack and/or Gmail (tester notification) How it works Trigger: feedback received via webhook Normalize & Clean: standardizes fields and cleans message AI Triage: returns structured JSON (type, severity, title, confidence…) Notion Dedupe & Upsert: search by suggested title → update if found, else create Closed Loop: notify tester (Slack or email) + webhook response payload What you get One workflow to capture and structure feature requests Clean Notion backlog without duplicates Automatic tester confirmation Structured output for downstream automation About me : I’m Yassin a Product Manager Scaling tech products with a data-driven mindset. 📬 Feel free to connect with me on Linkedin

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

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

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

How it works This workflow automates the entire lifecycle of a service-based client, combining four distinct business flows into a single view: Intake Leads: Receives a webhook from your form builder, validates the data, optionally enriches the email using Clearbit, and creates records in Airtable and Notion. Manage Bookings: Processes scheduling webhooks to update lead status, create Google Calendar events, and send pre-call survey emails. Send Reminders: Runs a daily schedule to scan Airtable for upcoming calls and automatically sends 24h reminder emails to reduce no-shows. Onboard Clients: Reacts to successful payments by marking leads as "Paid," generating a Notion Onboarding Checklist, and sending a Welcome Kit via Email and WhatsApp. Set up steps Configure Credentials: Connect your accounts for Airtable, Notion, Slack, Google Calendar, and GMAIL. (Optional) Add credentials for Clearbit (enrichment) and Twilio (WhatsApp). Customize Emails: Open the four Email Send nodes. Customize the Body Text with your own booking links and survey URLs. Configure Tables & IDs: Update the Airtable nodes with your specific Base and Table names (e.g., tblLeads). Update the Notion nodes with your Database IDs for Projects and Onboarding. Connect Webhooks: Copy the Production URLs from the three Webhook nodes (Lead Intake, Booking, Payment) and paste them into your respective form, calendar, or payment provider settings.

Who is this for This template is essential for Remote Operations Managers, HR Teams, and Project Leads managing distributed teams across different countries. It prevents scheduling conflicts by automatically flagging when a regional team is out of office and identifying when multiple teams are off simultaneously. What it does Stop manually Googling "Is it a holiday in Berlin today?" This workflow automates your team availability calendar. It triggers on a weekly schedule. It takes your team's locations (e.g., KR, MX) and a "Lookahead" range (e.g., 50 days). It fetches official public holidays for both the current and next year using the Nager.Date API (to ensure year-end holidays aren't missed). It filters the results to find only holidays occurring within your defined lookahead window. It compares dates across countries to identify "Shared Holidays" (dates where multiple teams are off). It logs these holidays into a Notion database and notifies the team via Slack, specifically highlighting if a holiday is shared. How to set up Notion: Create a Database with properties: Name (Title), Date (Date), and Shared Countries (Text). Slack: Connect your Slack account in the credentials. Configuration: Define Team Countries: Enter the 2-letter country codes (e.g., "KR", "US") in the Set node. Define Days to Lookahead: Set how many days into the future you want to check (default is 50). Add to Notion: Select your Database ID. How to customize Filter Logic:** The "Filter Upcoming" node handles the date logic. You can modify this to check for specific holiday types (e.g., exclude "Optional" holidays). Shared Logic:** The "Find Shared Holidays" node calculates overlaps. You can adjust the JavaScript here if you want to change the format of the shared message sent to Slack. Destinations:** Swap the Notion node for Google Calendar to block off time directly.

Who is this for This template is perfect for sales professionals, account managers, and business development teams who want to make memorable impressions on their clients. It automates the tedious task of researching gift shops and preparation spots before important meetings. What it does This workflow automatically prepares personalized recommendations for client visits by monitoring your Google Calendar, enriching data from Notion, and using AI to select the perfect options. How it works Trigger: Activates when a calendar event containing keywords like "visit," "meeting," "client," or "dinner" is created or updated Extract: Parses company name from the event title Enrich: Fetches customer preferences from your Notion database Search: Google Places API finds nearby gift shops and quiet cafes Analyze: GPT-4 recommends the best options based on customer preferences Notify: Sends a personalized message to Slack with recommendations Example Slack Output Here's what the final notification looks like: 🎁 Recommended Gift Shop Patisserie Sadaharu AOKI (★4.6) 3-5-2 Marunouchi, Chiyoda-ku 💡 Reason: The customer loves French desserts, so this patisserie's macarons would be perfect! ☕ Pre-Meeting Cafe Starbucks Reserve Roastery (★4.5) 5 min walk from meeting location Set up steps Setup time: approximately 15 minutes Google Calendar: Connect your Google Calendar account and select your calendar Notion Database: Create a customer database with "Company Name" (title) and "Preferences" (text) fields Google Places API: Get an API key from Google Cloud Console and add it to the Configuration node OpenAI: Connect your OpenAI account for AI-powered recommendations Slack: Connect your Slack workspace and update the channel ID in the final node Requirements Google Calendar account Notion account with a customer database Google Places API key (requires Google Cloud account) OpenAI API key Slack workspace with bot permissions How to customize Search radius: Adjust the searchRadius parameter in the Configuration node (default: 1000 meters) Event keywords: Modify the Filter node conditions to match your calendar naming conventions Notification channel: Change the Slack channel ID to your preferred channel

Who is this for This workflow is perfect for busy professionals, consultants, and anyone who frequently travels between meetings. If you want to make the most of your free time between appointments and discover great nearby spots without manual searching, this template is for you. What it does This workflow automatically monitors your Google Calendar and identifies gaps between appointments. When it detects sufficient free time (configurable, default 30+ minutes), it calculates travel time to your next destination, checks the weather, and uses AI to recommend the top 3 spots to visit during your break. Recommendations are weather-aware: indoor spots like cafés in malls or stations for rainy days, and outdoor terraces or open-air venues for nice weather. How it works Schedule Trigger - Runs every 30 minutes to check your calendar Fetch Data - Gets your next calendar event and user preferences from Notion Calculate Gap Time - Determines available free time by subtracting travel time (via Google Maps) from time until your next appointment Weather Check - Gets current weather at your destination using OpenWeatherMap Smart Routing - Routes to indoor or outdoor spot search based on weather conditions AI Recommendations - GPT-4.1-mini analyzes spots and generates personalized top 3 recommendations Slack Notification - Sends a friendly message with recommendations to your Slack channel Set up steps Configure API Keys - Add your Google Maps, Google Places, and OpenWeatherMap API keys in the "Set Configuration" node Connect Google Calendar - Set up OAuth connection and select your calendar Set up Notion - Create a database for user preferences and add the database ID Connect Slack - Set up OAuth and specify your notification channel Connect OpenAI - Add your OpenAI API credentials Customize - Adjust currentLocation and minGapTimeMinutes to your needs Requirements Google Cloud account with Maps and Places APIs enabled OpenWeatherMap API key (free tier available) Notion account with a preferences database Slack workspace with bot permissions OpenAI API key How to customize Change trigger frequency: Modify the Schedule Trigger interval Adjust minimum gap time: Change minGapTimeMinutes in the configuration node Modify search radius: Edit the radius parameter in the Places API calls (default: 1000m) Customize spot types: Modify the type and keyword parameters in the HTTP Request nodes Change AI model: Switch to a different OpenAI model in the AI node Localize language: Update the AI prompt to generate responses in your preferred language

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