Two-way property repair management system with Google Sheets & Drive
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 17 nodes and runs on Google Sheets events (row added) (plus 1 other trigger). Along the way it connects Google Sheets, Google Drive and Gmail.
How it runs
Trigger: On Google Sheets events (row added) (plus 1 other trigger).
- Isolate new entry (Code): runs custom JavaScript code
- If: checks a condition and branches into true / false
- Get row(s) in sheet (Google Sheets): uses Google Sheets
- Format Data (Edit Fields (Set)): sets 3 fields: name, photosVideos, feedbackSuggestions
- Separate Photo Files (Code): runs custom JavaScript code
- New details (Edit Fields (Set)): sets 4 fields: UUID, Action-new, nameDate-new…
- Existing Details (Edit Fields (Set)): sets 4 fields: UUID, Action, nameDate…
- Report Alert + Info (Gmail): uses Gmail
- Add UUID # (Google Sheets): update
- Photo Uploading (Loop Over Items (Split in Batches)): loops over the items in batches
…plus 5 more steps. See the full node list below.
Services it uses
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (10)
- Google Sheets
n8n-nodes-base.googleSheets - Google Drive
n8n-nodes-base.googleDrive - Edit Fields (Set)
n8n-nodes-base.set - Gmail
n8n-nodes-base.gmail - Loop Over Items (Split in Batches)
n8n-nodes-base.splitInBatches - Code
n8n-nodes-base.code - Merge
n8n-nodes-base.merge - If
n8n-nodes-base.if - Google Sheets Trigger
n8n-nodes-base.googleSheetsTrigger - Manual Trigger
n8n-nodes-base.manualTrigger
From the author
This workflow automates the repair request process between tenants and building managers, keeping all updates organized in a single spreadsheet. It is composed of two coordinated workflows, as two separate triggers are required — one for new repair…