Back to Catalog

Automated Google Drive to FTP transfer with JSON logging & reports

Dariusz KorytoDariusz Koryto
165 views
2/3/2026
Official Page

Google Drive to FTP Transfer Workflow - Setup Guide

Overview

This n8n workflow automatically transfers files from Google Drive to an FTP server on a scheduled basis. It includes comprehensive logging, email notifications, and error handling.

Features

  • Automated Scheduling: Runs every 6 hours (customizable)
  • Manual Trigger: Webhook endpoint for on-demand transfers
  • File Filtering: Supports specific file types and size limits
  • Comprehensive Logging: Detailed transfer reports saved to Google Drive
  • Email Notifications: HTML reports sent after each run
  • Error Handling: Graceful handling of failed transfers
  • Batch Processing: Files processed individually to prevent rate limits

Prerequisites

Before setting up this workflow, ensure you have:

  1. n8n instance running (self-hosted or cloud)
  2. Google Drive account with files to transfer
  3. FTP server with upload permissions
  4. Email service for sending reports (SMTP)

Step-by-Step Setup Instructions

1. Google Drive API Setup

1.1 Create Google Cloud Project

  1. Go to Google Cloud Console
  2. Create a new project or select existing one
  3. Enable the Google Drive API:
    • Navigate to "APIs & Services" → "Library"
    • Search for "Google Drive API"
    • Click "Enable"

1.2 Create OAuth2 Credentials

  1. Go to "APIs & Services" → "Credentials"
  2. Click "Create Credentials" → "OAuth client ID"
  3. Configure consent screen if prompted
  4. Choose "Web application" as application type
  5. Add your n8n instance URL to authorized redirect URIs:
    https://your-n8n-instance.com/rest/oauth2-credential/callback
    
  6. Note down the Client ID and Client Secret

1.3 Configure n8n Credential

  1. In n8n, go to "Credentials" → "Add Credential"
  2. Select "Google Drive OAuth2 API"
  3. Enter your Client ID and Client Secret
  4. Complete OAuth flow by clicking "Connect my account"
  5. Set credential ID as: your-google-drive-credentials-id

2. FTP Server Setup

2.1 FTP Server Requirements

  • Ensure FTP server is accessible from your n8n instance
  • Verify you have upload permissions
  • Note the server details:
    • Host/IP address
    • Port (usually 21 for FTP)
    • Username and password
    • Destination directory path

2.2 Configure n8n FTP Credential

  1. In n8n, go to "Credentials" → "Add Credential"
  2. Select "FTP"
  3. Enter your FTP server details:
    • Host: your-ftp-server.com
    • Port: 21 (or your custom port)
    • Username: your-ftp-username
    • Password: your-ftp-password
  4. Set credential ID as: your-ftp-credentials-id

3. Email Setup (SMTP)

3.1 Choose Email Provider

Configure SMTP settings for one of these providers:

  • Gmail: smtp.gmail.com, port 587, use App Password
  • Outlook: smtp-mail.outlook.com, port 587
  • Custom SMTP: Your organization's SMTP server

3.2 Configure n8n Email Credential

  1. In n8n, go to "Credentials" → "Add Credential"
  2. Select "SMTP"
  3. Enter your SMTP details:
    • Host: smtp.gmail.com (or your provider)
    • Port: 587
    • Security: STARTTLS
    • Username: your-email@example.com
    • Password: your-app-password
  4. Set credential ID as: your-email-credentials-id

4. Workflow Configuration

4.1 Import Workflow

  1. Copy the workflow JSON from the artifact above
  2. In n8n, click "Import from JSON"
  3. Paste the workflow JSON and import

4.2 Update Credential References

  1. Google Drive nodes: Verify credential ID matches your-google-drive-credentials-id
  2. FTP node: Verify credential ID matches your-ftp-credentials-id
  3. Email node: Verify credential ID matches your-email-credentials-id

4.3 Customize Parameters

FTP Server Settings (Upload to FTP node)
{
  "host": "your-ftp-server.com",           // Replace with your FTP host
  "username": "your-ftp-username",         // Replace with your FTP username
  "password": "your-ftp-password",         // Replace with your FTP password
  "path": "/remote/directory/{{ $json.validFiles[$json.batchIndex].name }}", // Update destination path
  "port": 21                               // Change if using different port
}
Email Settings (Send Report Email node)
{
  "sendTo": "admin@yourcompany.com",       // Replace with your email address
  "subject": "Google Drive to FTP File Transfer - Report"
}
File Filter Settings (Filter & Validate Files node)

In the JavaScript code, update these settings:

const transferNotes = {
  settings: {
    maxFileSizeMB: 50,                     // Change maximum file size
    allowedExtensions: [                   // Add/remove allowed file types
      '.pdf', '.doc', '.docx', '.txt', 
      '.jpg', '.png', '.zip', '.xlsx'
    ],
    autoDeleteAfterTransfer: false,        // Set to true to delete from Drive after transfer
    verifyTransfer: true                   // Keep true for verification
  }
};
Google Drive Notes Storage (Upload Notes to Drive node)
{
  "parents": {
    "parentId": "your-notes-folder-id"     // Replace with actual folder ID from Google Drive
  }
}

5. Schedule Configuration

5.1 Modify Schedule Trigger

In the "Schedule Trigger" node, adjust the interval:

{
  "rule": {
    "interval": [
      {
        "field": "hours",
        "hoursInterval": 6               // Change to desired interval (hours)
      }
    ]
  }
}

Alternative schedule options:

  • Daily: "field": "days", "daysInterval": 1
  • Weekly: "field": "weeks", "weeksInterval": 1
  • Custom cron: Use cron expression for complex schedules

5.2 Webhook Configuration

The webhook trigger is available at:

POST https://your-n8n-instance.com/webhook/webhook-transfer-status

Use this for manual triggers or external integrations.

6. Testing and Validation

6.1 Test Connections

  1. Test Google Drive: Run "Get Drive Files" node manually
  2. Test FTP: Upload a test file using "Upload to FTP" node
  3. Test Email: Send a test email using "Send Report Email" node

6.2 Run Test Transfer

  1. Activate the workflow
  2. Click "Execute Workflow" to run manually
  3. Monitor execution in the workflow editor
  4. Check for any error messages or failed nodes

6.3 Verify Results

  • FTP Server: Confirm files appear in destination directory
  • Email: Check you receive the transfer report
  • Google Drive: Verify transfer notes are saved to specified folder

7. Monitoring and Maintenance

7.1 Workflow Monitoring

  • Execution History: Review past runs in n8n interface
  • Error Logs: Check failed executions for issues
  • Performance: Monitor execution times and resource usage

7.2 Regular Maintenance

  • Credential Renewal: Google OAuth tokens may need periodic renewal
  • Storage Cleanup: Consider archiving old transfer notes
  • Performance Tuning: Adjust batch sizes or schedules based on usage

8. Troubleshooting

8.1 Common Issues

Google Drive Authentication Errors:

  • Verify OAuth2 credentials are correctly configured
  • Check if Google Drive API is enabled
  • Ensure redirect URI matches n8n instance URL

FTP Connection Failures:

  • Verify FTP server credentials and connectivity
  • Check firewall settings allow FTP connections
  • Confirm destination directory exists and has write permissions

Email Delivery Issues:

  • Verify SMTP credentials and server settings
  • Check if email provider requires app-specific passwords
  • Ensure sender email is authorized

File Transfer Failures:

  • Check file size limits in filter settings
  • Verify allowed file extensions include your file types
  • Monitor FTP server disk space

8.2 Debug Mode

Enable debug mode by:

  1. Adding console.log statements in code nodes
  2. Using "Execute Workflow" with step-by-step execution
  3. Checking node outputs for data validation

9. Advanced Customizations

9.1 Additional File Filters

Add custom filtering logic in the "Filter & Validate Files" node:

// Example: Filter by modification date
const isRecentFile = new Date(file.modifiedTime) > new Date(Date.now() - 7 * 24 * 60 * 60 * 1000); // Last 7 days

// Example: Filter by folder location
const isInSpecificFolder = file.parents && file.parents.includes('specific-folder-id');

9.2 Enhanced Reporting

Customize the email report template in "Send Report Email" node:

<h2>📊 File Transfer Report</h2>
<div>
  <h3>Summary</h3>
  <ul>
    <li><strong>Date:</strong> {{ new Date().toLocaleString('en-US') }}</li>
    <li><strong>Success Rate:</strong> {{ Math.round((successfulTransfers / totalFiles) * 100) }}%</li>
    
  </ul>
</div>

9.3 Integration with Other Services

Add nodes to integrate with:

  • Slack: Send notifications to team channels
  • Discord: Post updates to Discord servers
  • Webhook: Trigger other workflows or systems
  • Database: Log transfers to MySQL, PostgreSQL, etc.

10. Security Considerations

10.1 Credential Security

  • Use environment variables for sensitive data
  • Regularly rotate FTP and email passwords
  • Implement least-privilege access for service accounts

10.2 Network Security

  • Use SFTP instead of FTP when possible
  • Implement VPN connections for sensitive transfers
  • Monitor network traffic for unusual patterns

10.3 Data Privacy

  • Ensure compliance with data protection regulations
  • Implement data retention policies for transfer logs
  • Consider encryption for sensitive file transfers

Support and Resources

Documentation Links

Getting Help

If you encounter issues:

  1. Check the troubleshooting section above
  2. Review n8n execution logs for error details
  3. Search the n8n community forum for similar issues
  4. Create a support ticket with detailed error information

Note: Replace all placeholder values (URLs, credentials, IDs) with your actual configuration before running the workflow.

Automated Google Drive to FTP Transfer with JSON Logging and Reports

This n8n workflow automates the process of transferring files from a specified Google Drive folder to an FTP server. It includes conditional logic to handle files based on their type, logs the transfer process, and sends email notifications for successful transfers or errors.

What it does

This workflow performs the following actions:

  1. Triggers on Schedule: The workflow starts at a predefined schedule (e.g., daily, hourly).
  2. Lists Google Drive Files: It connects to Google Drive and retrieves a list of files from a specified folder.
  3. Loops Through Files: It processes each file found in the Google Drive folder individually.
  4. Filters for Binary Files: It checks if the current file is a binary file (e.g., documents, images, archives).
  5. Downloads Binary Files: If the file is binary, it downloads the file content from Google Drive.
  6. Uploads to FTP: The downloaded binary file is then uploaded to a specified directory on an FTP server.
  7. Logs Transfer (Placeholder): A "Write Binary File" node is present, which could be used for local logging of the transfer process, though its current connection is not explicit in the provided JSON.
  8. Handles Non-Binary Files (Placeholder): There's a path for non-binary files, which currently doesn't perform any specific action.
  9. Sends Email Notifications:
    • Success Notification: Sends an email upon successful completion of the transfer process (or a batch of transfers).
    • Error Notification: Sends an email if any issues arise during the workflow execution.
  10. Custom Code Execution (Placeholder): A "Code" node is included, suggesting potential for custom logic, data transformation, or enhanced logging, though its specific implementation isn't detailed in the connections.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running instance of n8n.
  • Google Drive Account: With access to the folder containing the files to be transferred.
    • Google Drive OAuth2 Credential: Configured in n8n to allow access to your Google Drive.
  • FTP Server: An active FTP server with credentials and a target directory for uploads.
    • FTP Credential: Configured in n8n with the necessary host, port, username, and password.
  • SMTP Server: For sending email notifications.
    • Send Email Credential: Configured in n8n with your SMTP server details.

Setup/Usage

  1. Import the Workflow:
    • Download the provided JSON file.
    • In your n8n instance, go to "Workflows" and click "New".
    • Click the "Import from JSON" button and paste the workflow JSON or upload the file.
  2. Configure Credentials:
    • Click on the "Google Drive" node and select or create a new Google Drive OAuth2 credential. Ensure it has access to the relevant folder.
    • Click on the "FTP" node and select or create a new FTP credential.
    • Click on the "Send Email" nodes and select or create a new Send Email (SMTP) credential.
  3. Customize Nodes:
    • Schedule Trigger: Adjust the schedule in the "Schedule Trigger" node to your desired frequency (e.g., daily, hourly).
    • Google Drive: In the "Google Drive" node, specify the Folder ID from which files should be listed.
    • If Node: The "If" node currently checks for binary files. You might want to adjust its conditions based on your specific file type requirements.
    • FTP: In the "FTP" node, configure the Remote Path where the files should be uploaded.
    • Send Email: Update the To, From, Subject, and Body fields in both "Send Email" nodes for success and error notifications.
    • Code Node: If you intend to use the "Code" node for custom logic or logging, update its JavaScript code accordingly.
  4. Activate the Workflow: Once all credentials and configurations are set, activate the workflow by toggling the "Active" switch in the top right corner of the workflow editor.

This workflow will now automatically transfer files from your specified Google Drive folder to your FTP server according to the defined schedule, providing email notifications along the way.

Related Templates

Automate interior design lead qualification with AI & human approval to Notion

Overview This automated workflow intelligently qualifies interior design leads, generates personalized client emails, and manages follow-up through a human-approval process. Built with n8n, Claude AI, Telegram approval, and Notion database integration. ⚠️ Hosting Options This template works with both n8n Cloud and self-hosted instances. Most nodes are native to n8n, making it cloud-compatible out of the box. What This Template Does Automated Lead Management Pipeline: Captures client intake form submissions from website or n8n forms AI-powered classification into HOT/WARM/COLD categories based on budget, project scope, and commitment indicators Generates personalized outreach emails tailored to each lead type Human approval workflow via Telegram for quality control Email revision capability for rejected drafts Automated client email delivery via Gmail Centralized lead tracking in Notion database Key Features ✅ Intelligent Lead Scoring: Analyzes 12+ data points including budget (AED), space count, project type, timeline, and style preferences ✅ Personalized Communication: AI-generated emails reference specific client details, demonstrating genuine understanding ✅ Quality Control: Human-in-the-loop approval via Telegram prevents errors before client contact ✅ Smart Routing: Different workflows for qualified leads (meeting invitations) vs. unqualified leads (respectful alternatives) ✅ Revision Loop: Rejected emails automatically route to revision agent for improvements ✅ Database Integration: All leads stored in Notion for pipeline tracking and analytics Use Cases Interior design firms managing high-volume lead intake Architecture practices with complex qualification criteria Home renovation companies prioritizing project value Any service business requiring budget-based lead scoring Sales teams needing approval workflows before client contact Prerequisites Required Accounts & API Keys: Anthropic Claude API - For AI classification and email generation Telegram Bot Token - For approval notifications Gmail Account - For sending client emails (or any SMTP provider) Notion Account - For lead database storage n8n Account - Cloud or self-hosted instance Technical Requirements: Basic understanding of n8n workflows Ability to create Telegram bots via BotFather Gmail app password or OAuth setup Notion database with appropriate properties Setup Instructions Step 1: Clone and Import Template Copy this template to your n8n instance (cloud or self-hosted) All nodes will appear as inactive - this is normal Step 2: Configure Form Trigger Open the Client Intake Form Trigger node Choose your trigger type: For n8n forms: Configure form fields matching the template structure For webhook: Copy webhook URL and integrate with your website form Required form fields: First Name, Second Name, Email, Contact Number Project Address, Project Type, Spaces Included Budget Range, Completion Date, Style Preferences Involvement Level, Previous Experience, Inspiration Links Step 3: Set Up Claude AI Credentials Obtain API key from https://console.anthropic.com In n8n: Create new credential → Anthropic → Paste API key Apply credential to these nodes: AI Lead Scoring Engine Personalized Client Outreach Email Generator Email Revision Agent Step 4: Configure Telegram Approval Bot Create bot via Telegram's @BotFather Copy bot token Get your Telegram Chat ID (use @userinfobot) In n8n: Create Telegram credential with bot token Configure Human-in-the-Loop Email Approval node: Add your Chat ID Customize approval message format if desired Step 5: Set Up Gmail Sending Enable 2-factor authentication on Gmail account Generate app password: Google Account → Security → App Passwords In n8n: Create Gmail credential using app password Configure Client Email Delivery node with sender details Step 6: Connect Notion Database Create Notion integration at https://www.notion.so/my-integrations Copy integration token Create database with these properties: Client Name (Title), Email (Email), Contact Number (Phone) Project Address (Text), Project Type (Multi-select) Spaces Included (Text), Budget (Select), Timeline (Date) Classification (Select: HOT/WARM/COLD), Confidence (Select) Estimated Value (Number), Status (Select) Share database with your integration In n8n: Add Notion credential → Paste token Configure Notion Lead Database Manager with database ID Step 7: Customize Classification Rules (Optional) Open AI Lead Scoring Engine node Review classification criteria in the prompt: HOT: 500k+ AED, full renovations, 2+ spaces WARM: 100k+ AED, 2+ spaces COLD: &lt;100k AED OR single space Adjust thresholds to match your business requirements Modify currency if not using AED Step 8: Personalize Email Templates Open Personalized Client Outreach Email Generator node Customize: Company name and branding Signature placeholders ([Your Name], [Title], etc.) Tone and style preferences Alternative designer recommendations for COLD leads Step 9: Test the Workflow Activate the workflow Submit a test form with sample data Monitor each node execution in n8n Check Telegram for approval message Verify email delivery and Notion database entry Step 10: Set Up Error Handling (Recommended) Add error workflow trigger Configure notifications for failed executions Set up retry logic for API failures Workflow Node Breakdown Client Intake Form Trigger Captures lead data from website forms or n8n native forms with all project details. AI Lead Scoring Engine Analyzes intake data using structured logic: budget validation, space counting, and multi-factor evaluation. Returns HOT/WARM/COLD classification with confidence scores. Lead Classification Router Routes leads into three priority workflows based on AI classification, optimizing resource allocation. Sales Team Email Notifier Sends instant alerts to sales representatives with complete lead details and AI reasoning for internal tracking. Personalized Client Outreach Email Generator AI-powered composer creating tailored responses demonstrating genuine understanding of client vision, adapted by lead type. Latest Email Version Controller Captures most recent email output ensuring only final approved version proceeds to delivery. Human-in-the-Loop Email Approval Telegram-based review checkpoint sending generated emails to team member for quality control before client delivery. Approval Decision Router Evaluates reviewer's response, routing approved emails to client delivery or rejected emails to revision agent. Email Revision Agent AI-powered editor refining rejected emails based on feedback while maintaining personalization and brand voice. Client Email Delivery Sends final approved personalized emails demonstrating understanding of project vision with clear next steps. Notion Lead Database Manager Records all potential clients with complete intake data, classification results, and tracking information for pipeline management. Customization Tips Adjust Classification Thresholds: Modify budget ranges and space requirements in the AI Lead Scoring Engine prompt to match your market and service level. Multi-Language Support: Update all AI agent prompts with instructions for your target language. Claude supports 100+ languages. Additional Routing: Add branches for special cases like urgent projects, VIP clients, or specific geographic regions. CRM Integration: Replace Notion with HubSpot, Salesforce, or Airtable using respective n8n nodes. SMS Notifications: Add Twilio node for immediate HOT lead alerts to mobile devices. Troubleshooting Issue: Telegram approval not received Verify bot token is correct Confirm chat ID matches your Telegram account Check bot is not blocked Issue: Claude API errors Verify API key validity and credits Check prompt length isn't exceeding token limits Review rate limits on your Anthropic plan Issue: Gmail not sending Confirm app password (not regular password) is used Check "Less secure app access" if using older method Verify daily sending limits not exceeded Issue: Notion database not updating Confirm integration has access to database Verify property names match exactly (case-sensitive) Check property types align with data being sent Template Metrics Execution Time: ~30-45 seconds per lead (including AI processing) API Calls: 2-3 Claude requests per lead (classification + email generation, +1 if revision) Cost Estimate: ~$0.05-0.15 per lead processed (based on Claude API pricing) Support & Community n8n Community Forum: https://community.n8n.io Template Issues: Report bugs or suggest improvements via n8n template feedback Claude Documentation: https://docs.anthropic.com Notion API Docs: https://developers.notion.com License This template is provided as-is under MIT license. Modify and adapt freely for your business needs. --- Version: 1.0 Last Updated: October 2025 Compatibility: n8n v1.0+ (Cloud & Self-Hosted), Claude API v2024-10+

Jameson KanakulyaBy Jameson Kanakulya
201

Automated UGC video generator with Gemini images and SORA 2

This workflow automates the creation of user-generated-content-style product videos by combining Gemini's image generation with OpenAI's SORA 2 video generation. It accepts webhook requests with product descriptions, generates images and videos, stores them in Google Drive, and logs all outputs to Google Sheets for easy tracking. Main Use Cases Automate product video creation for e-commerce catalogs and social media. Generate UGC-style content at scale without manual design work. Create engaging video content from simple text prompts for marketing campaigns. Build a centralized library of product videos with automated tracking and storage. How it works The workflow operates as a webhook-triggered process, organized into these stages: Webhook Trigger & Input Accepts POST requests to the /create-ugc-video endpoint. Required payload includes: product prompt, video prompt, Gemini API key, and OpenAI API key. Image Generation (Gemini) Sends the product prompt to Google's Gemini 2.5 Flash Image model. Generates a product image based on the description provided. Data Extraction Code node extracts the base64 image data from Gemini's response. Preserves all prompts and API keys for subsequent steps. Video Generation (SORA 2) Sends the video prompt to OpenAI's SORA 2 API. Initiates video generation with specifications: 720x1280 resolution, 8 seconds duration. Returns a video generation job ID for polling. Video Status Polling Continuously checks video generation status via OpenAI API. If status is "completed": proceeds to download. If status is still processing: waits 1 minute and retries (polling loop). Video Download & Storage Downloads the completed video file from OpenAI. Uploads the MP4 file to Google Drive (root folder). Generates a shareable Google Drive link. Logging to Google Sheets Records all generation details in a tracking spreadsheet: Product description Video URL (Google Drive link) Generation status Timestamp Summary Flow: Webhook Request → Generate Product Image (Gemini) → Extract Image Data → Generate Video (SORA 2) → Poll Status → If Complete: Download Video → Upload to Google Drive → Log to Google Sheets → Return Response If Not Complete: Wait 1 Minute → Poll Status Again Benefits: Fully automated video creation pipeline from text to finished product. Scalable solution for generating multiple product videos on demand. Combines cutting-edge AI models (Gemini + SORA 2) for high-quality output. Centralized storage in Google Drive with automatic logging in Google Sheets. Flexible webhook interface allows integration with any application or service. Retry mechanism ensures videos are captured even with longer processing times. --- Created by Daniel Shashko

Daniel ShashkoBy Daniel Shashko
1166

Track personal finances in Google Sheets with AI agent via Slack

Who's it for This workflow is perfect for individuals who want to maintain detailed financial records without the overhead of complex budgeting apps. If you prefer natural language over data entry forms and want an AI assistant to handle the bookkeeping, this template is for you. It's especially useful for: People who want to track cash and online transactions separately Anyone who lends money to friends/family and needs debt tracking Users comfortable with Slack as their primary interface Those who prefer conversational interactions over manual spreadsheet updates What it does This AI-powered finance tracker transforms your Slack workspace into a personal finance command center. Simply mention your bot with transactions in plain English (e.g., "₹500 cash food, borrowed ₹1000 from John"), and the AI agent will: Parse transactions using natural language understanding via Google Gemini Calculate balance changes for cash and online accounts Show a preview of changes before saving anything Update Google Sheets only after you approve Track debts (who owes you, who you owe, repayments) Send daily reminders at 11 PM with current balances and active debts The workflow maintains conversational context using PostgreSQL memory, so you can say things like "yesterday's transactions" or "that payment to Sarah" and it understands the context. How it works Scheduled Daily Check-in (11 PM) Fetches current balances from Google Sheets Retrieves all active debts Formats and sends a Slack message with balance summary Prompts you to share the day's transactions AI Agent Transaction Processing When you mention the bot in Slack: Phase 1: Parse & Analyze Extracts amount, payment type (cash/online), category (food, travel, etc.) Identifies transaction type (expense, income, borrowed, lent, repaid) Stores conversation context in PostgreSQL memory Phase 2: Calculate & Preview Reads current balances from Google Sheets Calculates new balances based on transactions Shows formatted preview with projected changes Waits for your approval ("yes"/"no") Phase 3: Update Database (only after approval) Logs transactions with unique IDs and timestamps Updates debt records with person names and status Recalculates and stores new balances Handles debt lifecycle (Active → Settled) Phase 4: Confirmation Sends success message with updated balances Shows active debts summary Includes logging timestamp Requirements Essential Services: n8n instance (self-hosted or cloud) Slack workspace with admin access Google account Google Gemini API key PostgreSQL database Recommended: Claude AI model (mentioned in workflow notes as better alternative to Gemini) How to set up Google Sheets Setup Create a new Google Sheet with three tabs named exactly: Balances Tab: | Date | CashBalance | OnlineBalance | Total_Balance | |------|--------------|----------------|---------------| Transactions Tab: | TransactionID | Date | Time | Amount | PaymentType | Category | TransactionType | PersonName | Description | Added_At | |----------------|------|------|--------|--------------|----------|------------------|-------------|-------------|----------| Debts Tab: | PersonName | Amount | Type | Datecreated | Status | Notes | |-------------|--------|------|--------------|--------|-------| Add header rows and one initial balance row in the Balances tab with today's date and starting amounts. Slack App Setup Go to api.slack.com/apps and create a new app Under OAuth & Permissions, add these Bot Token Scopes: app_mentions:read chat:write channels:read Install the app to your workspace Copy the Bot User OAuth Token Create a dedicated channel (e.g., personal-finance-tracker) Invite your bot to the channel Google Gemini API Visit ai.google.dev Create an API key Save it for n8n credentials setup PostgreSQL Database Set up a PostgreSQL database (you can use Supabase free tier): Create a new project Note down connection details (host, port, database name, user, password) The workflow will auto-create the required table n8n Workflow Configuration Import the workflow and configure: A. Credentials Google Sheets OAuth2: Connect your Google account Slack API: Add your Bot User OAuth Token Google Gemini API: Add your API key PostgreSQL: Add database connection details B. Update Node Parameters All Google Sheets nodes: Select your finance spreadsheet Slack nodes: Select your finance channel Schedule Trigger: Adjust time if you prefer a different check-in hour (default: 11 PM) Postgres Chat Memory: Change sessionKey to something unique (e.g., financetrackeryour_name) Keep tableName as n8nchathistory_finance or rename consistently C. Slack Trigger Setup Activate the "Bot Mention trigger" node Copy the webhook URL from n8n In Slack App settings, go to Event Subscriptions Enable events and paste the webhook URL Subscribe to bot event: app_mention Save changes Test the Workflow Activate both workflow branches (scheduled and agent) In your Slack channel, mention the bot: @YourBot ₹100 cash snacks Bot should respond with a preview Reply "yes" to approve Verify Google Sheets are updated How to customize Change Transaction Categories Edit the AI Agent's system message to add/remove categories. Current categories: travel, food, entertainment, utilities, shopping, health, education, other Modify Daily Check-in Time Change the Schedule Trigger's triggerAtHour value (0-23 in 24-hour format). Add Currency Support Replace ₹ with your currency symbol in: Format Daily Message code node AI Agent system prompt examples Switch AI Models The workflow uses Google Gemini, but notes recommend Claude. To switch: Replace "Google Gemini Chat Model" node Add Claude credentials Connect to AI Agent node Customize Debt Types Modify AI Agent's system prompt to change debt handling logic: Currently: IOwe and TheyOwe_Me You can add more types or change naming Add More Payment Methods Current: cash, online To add more (e.g., credit card): Update AI Agent prompt Modify Balances sheet structure Update balance calculation logic Change Approval Keywords Edit AI Agent's Phase 2 approval logic to recognize different approval phrases. Add Spending Analytics Extend the daily check-in to calculate: Weekly/monthly spending summaries Category-wise breakdowns Use additional Code nodes to process transaction history Important Notes ⚠️ Never trigger with normal messages - Only use app mentions (@botname) to avoid infinite loops where the bot replies to its own messages. 💡 Context Awareness - The bot remembers conversation history, so you can reference "yesterday", "last week", or previous transactions naturally. 🔒 Data Privacy - All your financial data stays in your Google Sheets and PostgreSQL database. The AI only processes transaction text temporarily. 📊 Backup Regularly - Export your Google Sheets periodically as backup. --- Pro Tips: Start with small test transactions to ensure everything works Use consistent person names for debt tracking The bot understands various formats: "₹500 cash food" = "paid 500 rupees in cash for food" You can batch transactions in one message: "₹100 travel, ₹200 food, ₹50 snacks"

Habeeb MohammedBy Habeeb Mohammed
448