Coordinate move-out cleaning and repair tasks with Google Sheets, Slack, email and Claude

Name: Coordinate move-out cleaning and repair tasks with Google Sheets, Slack, email and Claude
Availability: InStock
Rating: 4.5 (1 reviews)
Author: Hyrum Hurst

$20/month : Unlimited workflows

2500 executions/month

Try free

THE #1 IN WEB SCRAPING

Scrape any website without limits

Try free

HOSTINGER 🎉 Early Black Friday Deal
DISCOUNT 20%

Self-hosted n8n

Unlimited workflows - from $4.99/mo

Try free

#1 hub for scraping, AI & automation

6000+ actors - $5 credits/mo

Try free

Who this is for

Property management companies managing frequent tenant move-outs across multiple units.

What this workflow does

Automatically schedules and coordinates move-out cleaning and repair tasks, sends vendor instructions, notifies internal teams, tracks completions, and logs everything for reporting.

How it works

Cron triggers workflow before lease end.
AI generates personalized move-out instructions and checklists.
Vendors and property management teams are notified.
Completion updates logged in Google Sheets.
Optional AI suggests follow-up actions for delays.

How to set up

Connect tenant data, configure Cron, Slack, Email, and Task Manager credentials. Customize AI prompts and verify notification flows.

Requirements

Google Sheets
Email & Slack credentials
AI Node access
Task Manager (Trello/Asana/etc.)

Built by QuarterSmart. Created by Hyrum Hurst.

Hyrum Hurst

0 workflows

Nodes

set gmail telegram agent google-gemini

Complexity

advanced

Published 04 Jan 2026

Likes 0

View on n8n.io Download Workflow

✨

Share Your Workflow

Have a great workflow to share? Join the n8n Creator Hub and help the community!

Submit Your Template How to Submit

Related Workflows

Track employee performance KPIs from ClickUp with GPT-4.1 and Google Sheets

## How it works This workflow runs on a schedule to collect task data from ClickUp and evaluate employee performance using AI. Tasks are analyzed to generate structured summaries, productivity metrics, and KPI scores. JavaScript logic refines and standardizes the results. The final performance data is stored in Google Sheets as a live KPI dashboard. ## Step-by-step - **Step 1: Collect ClickUp task data** - **Schedule Trigger** – Starts the workflow automatically at defined intervals. - **Get many folders** – Fetches all folders from the selected ClickUp space. - **Loop Over Items** – Iterates through folders to process tasks sequentially. - **Get many tasks** – Retrieves tasks associated with each folder or list. - **Step 2: Analyze tasks and compute KPIs** - **Message a model** – Sends task details to an AI model to generate summaries and raw performance metrics. - **Code in JavaScript** – Parses AI output, recalculates KPI scores, and assigns standardized ratings. - **Step 3: Update employee KPI dashboard** - **Append or update row in sheet** – Writes or updates task and employee performance data in Google Sheets. ## Why use this? - Automates employee performance tracking without manual reporting. - Produces consistent KPI scores across all ClickUp tasks. - Helps managers quickly identify overdue or high-priority work. - Keeps Google Sheets dashboards continuously up to date. - Improves visibility into productivity and task execution trends.

View

Notify Redmine project members in Slack about teammates’ approved Odoo leave

## 📌Who is this for? This workflow is designed for engineering teams, project managers, and IT operations who need consistent visibility into team availability across multiple projects. It’s perfect for organizations that use Odoo for leave management and Redmine for project collaboration, and want to ensure that everyone involved gets timely, automated Slack notifications whenever a team member will be absent the next day. ## 📌The problem When team members go dark, everything grinds to a halt. You're stuck with: - Last-minute meeting reschedules (and frustrated stakeholders) - Tasks assigned to people who aren't there - No time to redistribute workload - Bottlenecks affecting multiple projects ## 📌How it works 1. **Runs** daily at 17:15 - Set it and forget it. Executes every afternoon, giving teams time to prepare. 2. **Fetches** Tomorrow's Approved Leaves from Odoo - Pulls all leave records with tomorrow's start date and "approved" status. 3. **Maps** Employee & Project Data - Grabs the employee's details and identifies every Redmine project they're assigned to. 4. **Finds** All Teammates on the Same Projects - Deduplicates across overlapping projects to avoid notification spam. 5. **Sends** Targeted Slack Notifications - Only notifies people who actually work with the absent member, plus optional manager alerts. ## 📌Quick setup Before you start, you’ll need: - Odoo API key - Redmine API key - Slack Bot Token (or Incoming Webhook URL) - Subflows need to be created within a new flow; the main flow will call these subflows. ## 📌Results What changes immediately: - Zero surprises - teams know absences 24 hours ahead - Workload rebalancing happens before the person goes off - Managers make proactive decisions, not reactive ones - No more wasted Slack messages to irrelevant people - This creates a more predictable and transparent workflow across your engineering and project teams. ## 📌Take it further Ready to supercharge it? Add: - Auto-assign backup owners for critical tasks - Sync absences to Google Calendar/Outlook - Log notifications to a database for auditing - Conditional alerts (key roles, high-priority projects only) - Daily summary digest of all upcoming absences ## 📌Need help customizing? Contact me for consulting and support: [Linkedin](https://www.linkedin.com/company/bac-ha-software/posts/?feedView=all) / [Website](https://bachasoftware.com/bhsoft-contacts)

View

Triage product UAT feedback with OpenAI, Notion, Slack and Gmail

## 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 ![image.png](fileId:3835) - 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](https://www.linkedin.com/in/yassin-zehar)

View

👨‍💻

Need Custom Automation?

N8N Automation Expert

Specialized in N8N automation, I design custom workflows that connect your tools and automate your processes.