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
- Google Drive Trigger Polls the Incident Reports folder for any new files created by the previous workflow.
- Download + Extract Text When a new .md or .txt report appears, it’s downloaded and the text is extracted for processing.
- 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.
- Create Draft in Gmail The workflow automatically builds a Gmail draft using those fields—ready for review and send.
- 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