Complete booking system with Google Calendar, business hours & REST API
GCalendar Smart Booking System
Demo

π Description
Transform your booking chaos into streamlined automation with this production-ready GCalendar Smart Booking System. This comprehensive n8n workflow eliminates weeks of custom development by providing two powerful REST APIs that handle everything from input validation to calendar integration.
What makes this special? Unlike basic booking forms, this system includes enterprise-grade features like intelligent conflict detection, public holiday awareness, business hours enforcement, and automatic Google Calendar integration with Meet links. It's battle-tested with real-world business logic including lunch breaks, timezone handling, and comprehensive error responses.
Privacy & Cost Benefits:
- π Privately yours & free - No need to purchase expensive booking software or worry about data breaches. Your booking data stays secure in your own Google Calendar, completely under your control.
- π― All-in-One solution - No manual invitation sending required. Google Calendar automatically handles attendee notifications and generates real Google Meet links for every booking, creating a seamless experience for both you and your clients. No need pay for API to get public holiday, use the google calendar free default .
Perfect for rapid deployment: Whether you're building for clients, launching an MVP, or replacing expensive booking software, this template gets you from zero to production in under 15 minutes. The clean API design makes frontend integration effortless, while the robust validation ensures reliable operation at scale.
Two endpoints, endless possibilities:
/make-booking- Complete booking creation with multi-layer validation/check-booking-date- Real-time slot availability listing (comes with conflict detection, business hour checks)
Built by developers, for developers - with comprehensive documentation, testing examples, and customization guides included.
Purpose
This workflow provides a webhook API endpoint that your frontend can easily integrate typically triggered by a submit button on a booking form. When the frontend calls this REST API, the workflow handles the booking logic by performing several key checks:
- Valid Input β Ensures all required fields are present and correctly formatted.
- Date & Time Validation β Confirms the requested slot falls within business hours, excludes lunch/dinner breaks, and respects public holidays.
- Conflict Detection β Checks for any existing bookings at the requested time to prevent overlaps.
- Calendar Integration β Once all checks pass, the workflow automatically creates a booking entry in your Google Calendar, keeping everything synced and visible.
π― Target Audience
This template is perfect for:
π₯ Healthcare & Medical Professionals: Clinics, dental offices, physiotherapy centers, and medical practices needing automated appointment scheduling with proper business hours validation and no-show reduction.
πΌ Professional Service Providers: Consultants, lawyers, accountants, financial advisors, and coaches who require sophisticated booking systems with calendar integration and conflict prevention.
π Educational Institutions: Universities, tutoring centers, training academies, and educational consultants needing student appointment scheduling with academic calendar integration.
π’ Small to Medium Businesses: Service-based businesses like salons, spas, repair services, and consulting firms looking to automate their booking process without expensive software subscriptions.
π¨βπ» Software Development Teams: Developers and engineering teams who need to rapidly deploy booking functionality for client projects without building from scratch.
π Digital Agencies: Web development agencies, marketing firms, and digital consultancies building booking solutions for multiple clients across different industries.
π¨ Hospitality & Events: Meeting room booking, event venue scheduling, equipment rental companies, and co-working spaces requiring intelligent availability management.
π§ Freelancers & Solo Entrepreneurs: Independent professionals like designers, photographers, personal trainers, and contractors who need professional booking systems on a budget.
π Product Managers: Teams building SaaS products that require booking/scheduling features as part of their core functionality or user experience.
π Startup Founders: Early-stage companies needing to validate booking-related business models quickly without significant development investment.
π¨ Creative Professionals: Photographers, videographers, music instructors, and artists who need client appointment scheduling with portfolio integration possibilities.
βοΈ Technical Operations Teams: DevOps engineers and system administrators who need to implement booking systems for internal resource allocation (servers, equipment, meeting rooms).
This template eliminates weeks of development time while providing enterprise-grade validation, making it ideal for anyone who values rapid deployment, reliability, and professional functionality in their booking systems.
βοΈ How It Works
π Booking Flow (Step-by-Step)
Phase 1: Input Validation
// Real validation logic from the workflow
β
Name, email, phone, date, time validation
β
Email format verification (RFC compliant)
β
Phone number format checking
β
Date/time format standardization (YYYY-MM-DD, HH:MM)
Phase 2: Business Logic Validation
// Business hours: Monday-Friday, 9AM-9PM (customizable)
β
Weekend blocking
β
Business hours enforcement
β
Lunch break exclusion (12PM-2PM)
β
Dinner break exclusion (6PM-8PM)
β
Timezone handling (Malaysia/UTC+8 default)
Phase 3: Intelligent Conflict Detection
// Multi-calendar checking
β
Public holiday calendar integration
β
Main booking calendar conflict detection
β
Real-time availability verification
β
Overlap prevention algorithms
Phase 4: Calendar Integration
// Google Calendar automation
β
Event creation with attendee invitation
β
Google Meet link generation
β
Custom event descriptions and summaries
β
Calendar color coding
π Availability API Flow
- Date Input β Validates YYYY-MM-DD format
- Weekend/Holiday Check β Blocks non-working days
- Slot Generation β Creates available time slots
- Conflict Mapping β Marks booked vs available slots
- Response Formatting β Returns structured availability data
π οΈ Quick Start Guide
Prerequisites
- n8n instance (cloud or self-hosted)
- Google Cloud Project with Calendar API enabled
- Google Calendar credentials
Simple Setup Guide
Step 1: Import the Workflow β¬οΈ
- Download the
smart-booking-system.jsonfile - In your n8n instance: Workflows β Import from File
- Select the downloaded JSON file
- Click Import
Step 2: Set Up Google Calendar Credentials π
-
Create Google Cloud Project:
- Go to Google Cloud Console
- Create new project or select existing one
- Enable Google Calendar API
-
Configure n8n Credentials:
- In n8n: Credentials β Add Credential β Google Calendar OAuth2 API
- Enter your Google Cloud Client ID and Client Secret
- Save as "Google Calendar account"
-
Update Workflow Nodes:
- Find nodes:
Create Calendar Event,Check Calendar Availability, etc. - Select your Google Calendar credential in each node
- Find nodes:
Step 3: Configure Your Calendars π
-
Main Booking Calendar:
- Create a dedicated Google Calendar for bookings
- Copy the Calendar ID (found in Calendar Settings)
- Replace
YOUR_BOOKING_CALENDAR_ID@group.calendar.google.comin these nodes:Create Calendar EventCheck Calendar Availability - MainCheck Calendar Availability
-
Holiday Calendar (Optional):
- Add your country's holiday calendar to Google Calendar
- Find the calendar ID (e.g.,
en.usa#holiday@group.v.calendar.google.com) - Update
Check Calendar Availability - public holidayandCheck Public Holiday Calendarnodes
Step 4: Customize Business Hours β°
- Find the ConfigTimeSlots node
- Edit the time slots array:
[
{ "time": "09:30", "display": "9:30 AM - 10:30 AM", "available": true },
{ "time": "10:30", "display": "10:30 AM - 11:30 AM", "available": true },
{ "time": "11:30", "display": "11:30 AM - 12:30 PM", "available": true },
{ "time": "14:30", "display": "2:30 PM - 3:30 PM", "available": true },
{ "time": "15:30", "display": "3:30 PM - 4:30 PM", "available": true },
{ "time": "16:30", "display": "4:30 PM - 5:30 PM", "available": true },
{ "time": "17:30", "display": "5:30 PM - 6:30 PM", "available": true },
{ "time": "20:30", "display": "8:30 PM - 9:30 PM", "available": true }
]
Step 5: Activate & Test π
-
Activate the workflow: Toggle the workflow Active switch
-
Get your webhook URLs:
- Booking:
https://your-n8n-domain/webhook/suarify-make-booking - Availability:
https://your-n8n-domain/webhook/suarify-check-booking-date
- Booking:
-
Test with sample requests:
# Test booking creation
curl -X POST 'https://your-n8n-domain/webhook/suarify-make-booking' \
-H 'Content-Type: application/json' \
-d '{
"name": "John Doe",
"email": "john@example.com",
"phone": "+1234567890",
"date": "2024-03-15",
"time": "14:30"
}'
# Test availability checking
curl -X POST 'https://your-n8n-domain/webhook/suarify-check-booking-date' \
-H 'Content-Type: application/json' \
-d '{"date": "2024-03-15"}'
Step 6: Integrate with Your Frontend π»
- Use the webhook URLs in your booking form
- Handle the JSON responses for success/error states
- Display available time slots from the availability API
π You're ready to start taking bookings!
π API Documentation
π€ Booking Creation API
Endpoint: POST /webhook/make-booking
Request Body:
{
"name": "John Doe",
"email": "john@example.com",
"phone": "+1234567890",
"date": "2024-03-15",
"time": "14:30",
"source": "Website Form"
}
Success Response (200):
{
"success": true,
"message": "Booking confirmed successfully!",
"bookingDetails": {
"name": "John Doe",
"email": "john@example.com",
"phone": "+1234567890",
"date": "2024-03-15",
"time": "14:30",
"eventId": "abc123def456",
"eventLink": "https://calendar.google.com/event?eid=...",
"calendarEvent": { /* Full calendar event object */ }
},
"confirmationMessage": "Hi John Doe, your booking has been confirmed for 2024-03-15 at 14:30. You will receive a calendar invitation shortly."
}
Error Response (400):
{
"success": false,
"error": "Invalid email format",
"message": "Booking request failed validation",
"details": { /* Error context */ }
}
π Availability Check API
Endpoint: POST /webhook/check-booking-date
Request Body:
{
"date": "2024-03-15"
}
Success Response (200):
{
"success": true,
"isWorkingDay": true,
"isWeekend": false,
"holidayName": "",
"availableSlots": [
{
"time": "09:30",
"display": "9:30 AM - 10:30 AM",
"available": true
},
{
"time": "10:30",
"display": "10:30 AM - 11:30 AM",
"available": false,
"status": "booked"
}
],
"totalConflicts": 3
}
ποΈ Customization Guide
Business Hours Configuration
Edit the ConfigTimeSlots node to modify available booking times:
const timeSlots = [
{ time: '09:00', display: '9:00 AM - 10:00 AM', available: true },
{ time: '10:00', display: '10:00 AM - 11:00 AM', available: true },
// Lunch break automatically excluded
{ time: '14:00', display: '2:00 PM - 3:00 PM', available: true },
// Customize as needed...
];
Timezone Adjustment
Modify the Business Hours Check node:
// Change from Malaysia (UTC+8) to your timezone
const timezone = 'America/New_York'; // UTC-5
const timezoneOffset = '-05:00';
Holiday Calendar
Update calendar ID in holiday checking nodes:
// Replace with your country's holiday calendar
"value": "en.usa#holiday@group.v.calendar.google.com"
Business Rules
Customize validation in the Business Hours Check node:
// Business hours: Mon-Fri, 9am-6pm (example)
const isWithinBusinessHours = timeInMinutes >= 540 && timeInMinutes <= 1080;
// Remove lunch breaks if not needed
const isNotLunchBreak = true; // Always allow
Start automating in under 15 minutes! π
Made with β€οΈ for the engineering community. Star this repo if it saves you time!
n8n Booking System with Google Calendar Business Hours and REST API
This n8n workflow provides a robust booking system that integrates with Google Calendar to manage appointments, respecting defined business hours and handling booking requests via a REST API. It allows for conditional logic to determine if a booking is within business hours and responds to the API caller accordingly.
What it does
- Receives Booking Requests: Listens for incoming booking requests via a Webhook, acting as a REST API endpoint.
- Sets Booking Data: Transforms and prepares the incoming data for further processing.
- Checks Business Hours:
- Retrieves business hours from a specified Google Calendar.
- Uses a Code node to apply custom logic to determine if the requested booking time falls within the defined business hours.
- Conditional Processing: Routes the workflow based on whether the booking is within business hours:
- If within business hours: Proceeds to create the event.
- If outside business hours: Responds to the webhook immediately, indicating that the booking cannot be made.
- Creates Google Calendar Event: If the booking is valid, it creates an event in the specified Google Calendar.
- Responds to API: Sends a final response back to the original API caller, confirming the booking or indicating a failure.
- Delays Confirmation (Optional): Includes a "Wait" node, potentially for a delayed confirmation or further processing after the initial API response.
Prerequisites/Requirements
- n8n Instance: A running n8n instance.
- Google Calendar Account: A Google account with access to the calendar where bookings will be managed.
- Google Calendar Credentials: OAuth2 credentials configured in n8n for Google Calendar.
- API Client: An application or service that will send booking requests to the n8n Webhook.
Setup/Usage
- 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.
- Configure Credentials:
- Locate the "Google Calendar" node.
- Click on the "Credential" field and select your existing Google Calendar OAuth2 credential or create a new one. Follow the n8n documentation for setting up Google OAuth2 credentials if needed.
- Configure Webhook:
- Locate the "Webhook" trigger node.
- Copy the "Webhook URL" displayed in the node settings. This URL will be used by your API client to send booking requests.
- Ensure the "HTTP Method" and "Response Mode" are configured as per your API client's requirements (e.g., POST for booking requests).
- Customize Business Hours Logic:
- Open the "Code" node.
- Review and modify the JavaScript code to accurately reflect your business hours and any specific booking rules. This is where you define the logic for checking if a requested
startTimeandendTimefall within your operational hours.
- Activate the Workflow:
- Once all configurations are complete, click the "Activate" toggle in the top right corner of the n8n editor to enable the workflow.
Your n8n booking system is now ready to receive and process booking requests!
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: <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+
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
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"