Real-Time Visibility for All MSP Teams As part of our ongoing initiative to reduce blind spots and improve real-time operational awareness across all 6 MSP's we own, we’ve deployed a fully automated Server Event Log Analyzer that processes server event reports from Datto and delivers actionable summaries directly to each MSP’s Slack channel. For context, we rely on Datto RMM for monitoring and alerting across all managed endpoints. Datto provides the raw data—scheduled server event log reports that run automatically on a daily interval. Until now, these reports were only available if someone manually reviewed them, which meant issues often slipped through the cracks unless a technician actively went looking for them. This new automation eliminates that manual bottleneck. 📂 How It Works – End-to-End Workflow 1. Datto Generates Daily Server Event Log Reports Every day, Datto runs a scheduled report containing all server event log alerts from the previous period.These reports include issues such as: - Disk corruption or MFT errors - Failed services - Authentication or AD/GPO failures - Backup service issues - Recurring or noisy alerts across servers 2. Datto Drops the Report Into a Watched Google Drive Folder Datto is configured to deposit the CSV export into a specific folder. 3. Google Drive Watch Trigger Kicks Off the Automation Our workflow checks the folder every hour. As soon as a new file appears: - n8n downloads the CSV - Extracts the contents into structured JSON - Processes and normalizes the data 4. AI Organizes Alerts by Business Unit (MSP) Because we operate six separate MSPs across the country, the workflow intelligently identifies which alerts belong to which business unit. This is done by parsing the site names and extracting the MSP prefix: Each MSP's alerts are isolated into their own dataset, to help reduce noise. 5. Each MSP Dataset Is Sent to Its Own LLM Analyzer Once separated, each dataset is passed into a dedicated AI chain that:

Now that I’ve started on this journey, my mind can’t stop thinking about how I can automate everything 😂 This is a workflow I built for my wife’s candle company — her small side hustle and creative escape from her full-time job as a Communications Director for a global architecture and design firm. We already had a really detailed Airtable setup to track every aspect of the business: - Candle recipes and fragrance ratios - Batch production and material costs - Consignment and wholesale tracking - Inventory levels for jars, wicks, and fragrance oils So naturally, I thought: why not give her a Slack-based AI assistant to handle it all? 🧠 How It Works The Cantique Candle AI Co-Pilot connects Slack, OpenAI, and Airtable so we can literally ask the business questions in plain English — things like: “What was the last consignment order we dropped off? “How much of each fragrance would we need to make a batch of 24 candles? “What’s our material cost for a 12-candle batch of Hudson Woods?” …and it responds instantly with real data from Airtable. ⚙️ Workflow Overview: 🗣️ Chat Interface The Slack Trigger starts the conversation.Messages are passed to the AI Agent, which uses the OpenAI Chat Model and a Simple Memory node to keep context across messages. The agent interprets what’s being asked, runs the necessary Airtable searches, and sends a clean response right back into Slack. This gives us a natural, chat-based interface for the entire business — no dashboards, no clicking through tables. 📊 Airtable Data Layer Each of these nodes represents a connection to a specific Airtable table or function: - Upsert to Airtable: Automatically adds or updates records (like new batches or updated inventory). - Get Record: Fetches specific entries like batch data or consignment details. - Candle Cost Search: Calculates total material costs using live pricing and recipe data. - Search Consignment: Looks up consignment drop-offs, store partners, and payment status. - Search Wholesale: Retrieves wholesale account orders. - Search Fragrances: Finds fragrance inventory levels and cost per gram. - Search Recipes: Pulls candle formulas and scales ingredient needs for any batch size. - Search Inventory: Tracks all on-hand materials like wax, wicks, jars, and fragrance oils.

Hey everyone 👋, I run an agency together with my partner, who’s a software developer based in Romania. We’re currently looking for someone from the USA, Canada, or Europe to collaborate with us and help manage client meetings and interviews. Here’s how it works (100% legal and transparent): You’ll handle client interviews, meetings, and communication. My partner will handle all the technical work — website design, development, and digital marketing. We work under a legal subcontractor setup, so everything is professional and well-documented. You’ll earn a good commission — between 30% to 40% on every successful project we complete together. We’re looking for someone serious, honest, and ready to grow with a hardworking team. If you have experience in client handling, project coordination, or sales — this could be a great opportunity for you. 📩 DM me if you’re interested, and I’ll share more details about the work, our past projects, and how we’ll collaborate.

Hey everyone 👋 Following up on Part 1 of my Incident Report Automation (which generates polished Markdown reports from form submissions), I just finished building Part 2 – the Client Email Creator. This workflow automatically drafts a professional client-facing email every time a new incident report file hits Google Drive. ⚙️ How It Works 1. Google Drive Trigger Polls the Incident Reports folder for any new files created by the previous workflow. 2. Download + Extract Text When a new .md or .txt report appears, it’s downloaded and the text is extracted for processing. 3. AI Agent – Email Draft Generation The extracted report text is passed to an AI Agent (GPT-4.1 mini) that analyzes the content and produces a clean JSON response with a "Subject" and "Message" for a client-ready email. 4. Create Draft in Gmail The workflow automatically builds a Gmail draft using those fields—ready for review and send. 5. Slack Notification A quick Slack message confirms that the new report was detected and a draft email was created. 💡 Why It’s Useful - Eliminates manual email writing after each incident - Maintains consistent, professional tone across communications - Ensures clients are updated promptly after every issue - Seamlessly links with Part 1 (Incident Report Creator) for end-to-end automation 🧠 Stack - n8n – Workflow orchestration - Google Drive Trigger – Detects new reports - Extract from File – Converts report binaries to text - OpenAI (GPT-4.1 mini) – Drafts the client email - Gmail Tool – Creates draft automatically - Slack API – Sends notification 🚀 Next Steps - Map drafts to client-specific contact lists - Add an optional auto-send approval step - Generate PDF attachments from Markdown for record keeping It’s been awesome watching both parts work together – from raw form data ➜ polished report ➜ ready-to-send client email. Would love to hear how others are chaining AI + automation for client communications! #n8n #Automation #OpenAI #AIOps #WorkflowDesign #IncidentResponse #Gmail #Slack #GoogleDrive

Hey everyone 👋 I wanted to share a workflow I just finished building — an Incident Report Creator that turns form submissions into full, professional incident reports automatically using n8n + OpenAI. ⚙️ How It Works 1. Incident Intake Form: A web form collects the essential incident details — reporter name, client, incident type, severity, and resolution notes. 2. AI Report Generation: The data is passed to an AI Agent that formats it into a clean, client-ready Markdown report, including summary, impact, root cause, and preventive recommendations. 3. Metadata Extraction & ID Generation: A JavaScript node parses the AI output to extract the incident title, client, and date, then builds a unique incidentId and prepares structured JSON for the next steps. 4. File Conversion & Storage: The Markdown report is converted to a .md file and automatically uploaded to Google Drive for archival. 5. Notifications: A Slack message alerts the team that a new incident report has been created and stored. 💡 Why It’s Useful - Completely automates report writing and documentation - Produces consistent, professional-looking output - Keeps everything neatly organized with unique IDs - Saves engineers tons of time after incidents - Fully modular — easy to expand with PDF export, Airtable logging, or compliance alerts 🧠 Stack - n8n – Workflow orchestration - OpenAI (GPT-4.1) – Report generation - Slack – Notifications - Google Drive – Storage and archiving - JavaScript – Metadata extraction & automation logic 🔧 Next Steps I’m planning to add: - Auto-generated PDF reports with company branding - Integration with Airtable for compliance tracking - Conditional Slack alerts based on severity level Would love feedback or ideas from the community — especially if you’ve done similar AI + automation builds in n8n or other platforms! — Michael