Booking System (Fixed)

What is Booking System (Fixed)?

Booking System (Fixed) is a fixed version of a booking system for Andriana Delcheva, designed to run on Cloudflare Workers and integrate with Google Calendar and MCP Servers. It resolves critical issues in the original implementation, including booking completion, confirmation emails, and Google Calendar integration.

How to use Booking System (Fixed)?

Clone the repository, install dependencies with npm install, configure environment variables (e.g., Google Calendar credentials, MCP server URL), and deploy to Cloudflare Workers using npm run deploy:prod. API endpoints are available at /api/availability and /api/book.

Key features of Booking System (Fixed)

• Multi-step booking process with real-time availability checking
• Automated email confirmations via MCP Servers
• Google Calendar event creation with service details
• MCP Server integration for event notifications and error handling
• Comprehensive error handling with user-friendly messages
• Responsive design for mobile and desktop

Use cases of Booking System (Fixed)

• Scheduling appointments with automatic Google Calendar syncing
• Sending booking confirmation emails to customers
• Checking real-time availability before confirming bookings
• Handling booking errors with detailed monitoring via MCP

FAQ from Booking System (Fixed)

What prerequisites are needed to deploy?

A Cloudflare Workers account, a Google Cloud project with Calendar API enabled, a Google service account with access to the calendar, and an MCP Server for backend processing.

How are environment variables configured?

Variables like GOOGLE_CLIENT_EMAIL, GOOGLE_PRIVATE_KEY, GOOGLE_CALENDAR_ID, EMAIL_FROM, MCP_SERVER_URL, and MCP_API_KEY must be set in wrangler.toml or using wrangler secret put.

How does Google Calendar integration work?

It uses JWT authentication with the service account, checks for existing events before booking, creates detailed calendar events with booking info, and includes attendees and reminders.

What are the main API endpoints?

Two endpoints: POST /api/availability (returns available time slots for a date and duration) and POST /api/book (creates a booking and returns a booking ID and event ID).

How does the system handle errors?

It provides validation errors with specific messages, network error handling with retry options, server error logging with MCP integration, and user-friendly error messages.