How tanveer-singh7/ai-customer-support works
This repository implements a Gmail polling and message-ingestion service, not an evidenced AI response workflow. The main path polls Gmail, claims each message in the event table, reads it, upserts a ticket and saves the inbound message, then labels it processed and records success; failures are recorded and retried up to a limit. A separate FastAPI health endpoint is defined but is not shown driving the poller. Gmail operations and database calls are visible in the excerpts; other README detail is unavailable beyond the product name.
Main entry points: gmail.py Gmail Adapter · poller.py Mail Poller · pipeline.py Message Pipeline · db.py Database Access
Components 9
Polling and Processing
- Mail Poller
app/poller.py - Message Pipeline
app/pipeline.py
External Integrations
- Gmail Adapter
app/gmail.py - Gmail Service
- Database Access
app/db.py - Postgres
Configuration
- Settings
app/config.py
Health API
- Health Endpoint
app/main.py
Other components
- Health Caller
Connections 10
- Mail Poller → Gmail Adapter: lists mail
app/poller.py - Mail Poller → Message Pipeline: handles messages
app/poller.py - Message Pipeline → Gmail Adapter: reads and labels
app/pipeline.py - Message Pipeline → Database Access: records events and messages
app/pipeline.py - Gmail Adapter → Gmail Service: calls Gmail API
app/gmail.py - Database Access → Postgres: queries and updates
app/db.py - Mail Poller → Settings: reads interval
app/poller.py - Gmail Adapter → Settings: reads credentials
app/gmail.py - Database Access → Settings: reads database URL
app/db.py - Health Caller → Health Endpoint: requests health
app/main.py