Generate move-out deposit statements with gpt-5.6-terra, Gmail, and Google Sheets
Ready for 3.0What this workflow does
This AI workflow has 26 nodes and runs when an HTTP POST request hits its webhook URL (plus 1 other trigger). Along the way it connects Google Sheets, OpenAI Chat Model, Gmail and Telegram.
How it runs
Trigger: When an HTTP POST request hits its webhook URL (plus 1 other trigger).
- Normalize Move Out (Edit Fields (Set)): sets 11 fields: moveout_id, tenant_name, tenant_email…
- Read MoveOutLog for Sweep (Google Sheets): uses Google Sheets
- Validate Move Out Input (If): checks a condition and branches into true / false
- Compute Unprocessed Move Outs (Code): runs custom JavaScript code
- Append Pending Move Out (Google Sheets): append
- Build Invalid Move Out Alert (Edit Fields (Set)): sets 4 fields: tenant_name, tenant_email, unit…
- Has Unprocessed Move Outs (If): checks a condition and branches into true / false
- Build Disposition Prompt (Edit Fields (Set)): sets 9 fields: moveout_id, tenant_name, tenant_email…
- Alert Landlord Invalid Move Out (Telegram): uses Telegram
- Alert Landlord Unprocessed (Telegram): uses Telegram
…plus 13 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)
- Webhook
n8n-nodes-base.webhook - Edit Fields (Set)
n8n-nodes-base.set - If
n8n-nodes-base.if - Google Sheets
n8n-nodes-base.googleSheets - OpenAI Chat Model
@n8n/n8n-nodes-langchain.lmChatOpenAi - AI Agent
@n8n/n8n-nodes-langchain.agent - Code
n8n-nodes-base.code - Gmail
n8n-nodes-base.gmail - Telegram
n8n-nodes-base.telegram - Schedule Trigger
n8n-nodes-base.scheduleTrigger
From the author
Move-outs without the paperwork headache. This workflow takes inspection data via webhook, has AI separate chargeable damages from normal wear-and-tear, computes the deposit refund or amount owed, emails an itemized statement to the tenant, and keeps the…