Vincent Aboy

Selected work / Service Booking and Scheduling System

Service Booking and Scheduling System

Takes bookings and informal schedule messages through review, team assignment and job tracking, with customer records, an audit history and owner reports.

  • FastAPI
  • PostgreSQL
  • SQLAlchemy
  • n8n
  • Google Sheets
screenshot coming soonStaff dashboard with request counts, an operator queue and upcoming jobs
n8n workflow that receives an event and writes it to four Google Sheets
n8n workflow
The public landing page
Public landing page
The service request form
Request form
Schedule intake: pasting the team's raw schedule into a draft
Schedule intake
The daily team schedule with Team A and Team B
Team schedule
Search and filter every scheduled job
Appointments list
Customer records
Customers
Teams and technician assignment
Teams and technicians
The automation outbox with the event log
Automation outbox
The audit trail of decisions and assignments
Activity history
Read-only deployment settings
Settings

The problem

A service request is not an appointment yet. Staff have to check the service, date, area and team capacity before committing, then assign a team without clashing with another job. Jobs also get moved and cancelled, so the owner needs a clear record of what changed.

What I built

A web system with two ways in: a customer booking form, and a Schedule intake screen where the team's informal messages become reviewable draft rows. Both end up as jobs that staff assign to a team and a time, then track through reschedules, cancellation and completion, with a history of every change.

Staff can also manage the team roster: add technicians and teams, set team leads, and deactivate people safely. Owner reports go to Google Sheets through n8n, with retries when a send fails.

How it works

  1. Request
  2. Staff review
  3. Team and time
  4. Job tracking
  5. History
  1. Event saved
  2. Sent to n8n
  3. Sheets updated
  4. Confirmed or retried
  • FastAPI application with staff screens: review queue, dispatcher board, team schedule, appointments, customers, teams, activity history and settings.
  • PostgreSQL holds the real records. Google Sheets is only a readable copy for the owner.
  • An n8n workflow receives each event on a protected webhook, updates four Google Sheets tabs (daily schedule, client summary, service history and customer directory) and confirms back to the app.
  • Reporting events go through an outbox with retries and stable event keys, with a monitor to see and recover failed sends.
  • Database changes are tracked with migrations.

Where it stands

Version 1 is complete and was piloted by the owner with real bookings. It is not in daily use at the moment. Customer messaging and payments are not part of this version.

My role

I defined the workflow, made the design choices, reviewed, tested and deployed it. I built it with AI-assisted development, so the code was written with an AI tool under my direction.

Skills shown

Workflow design, FastAPI, PostgreSQL, scheduling logic, text parsing for informal messages, audit history, team and customer management, automation with n8n and Google Sheets, reliability thinking (retries and recovery), automated testing, working with AI tools.