PROJECT / overview
The challenge & approach
Availability is more than an empty calendar: working hours, breaks, timezones, conflicts and buffers must be respected.
Approach
I designed separate availability and booking workflows. The system validates dates, reads calendar events and computes eligible slots before booking.
PROJECT / architecture
Technical architecture
The solution combines n8n, REST APIs, Google Calendar. The focus is on clear responsibilities, reliable user flows and testable functionality.
User / Browser Experience
↓
n8n + REST APIs
↓
Integrations / Validation / Testing
PROJECT / features
Key capabilities
- Availability API and booking API
- 09:00–17:00 working hours; 10:00–11:00 blocked; Sundays closed
- 60/90-minute appointments and 15-minute buffers
- Timezone handling with Asia/Karachi
- Google Calendar event integration
PROJECT / decisions
Engineering decisions
- Explicit validation boundaries
- Conflict-aware slot calculation
- Planned concurrency, idempotency and observability improvements
PROJECT / testing
Quality & validation
- Date and duration validation
- Break and operating-hours checks
- Calendar conflict and buffer scenarios
PROJECT / outcome
Outcome & next steps
Availability, validation and booking workflows implemented. Further production hardening is planned.