How syedyaseenjamal/voxa-backend works
Voxa Backend is a multi-tenant communications and campaign API for administrators and company users. The main user journey is to authenticate, manage tenant and user access, maintain leads and integrations, then operate campaigns and telephony/AI call workflows. The map includes billing and DID management as separate product areas. README content was absent, and most implementation excerpts were partial, so uncertain internal and persistence links are omitted.
Main entry points: app.js Express application · telephony.controller.js Telephony workflows · auth.routes.js Authentication · leads.controller.js Lead management
Components 27
API and access
- Express application
src/app.js - Authentication
src/modules/auth/auth.routes.js - Auth handlers
src/modules/auth/auth.controller.js - Access middleware
src/middlewares/authenticate.js
Tenant administration
- Company management
src/modules/companies/company.routes.js - Company users
src/modules/company-users/companyUser.routes.js - Roles and permissions
src/modules/roles/role.routes.js - Admin users
src/modules/admin-users/adminUser.routes.js
Leads and campaigns
- Lead management
src/modules/leads/leads.controller.js - Platform integrations
src/modules/integrations/integration.routes.js - Lead data
src/modules/integrations/lead.model.js - Meta campaigns
src/modules/integrations/campaigns.controller.js - IVR campaigns
src/modules/ivr-campaigns/ivrCampaign.controller.js - OBD CMS service
src/modules/ivr-campaigns/obdCms.service.js
Voice and AI
- DID management
src/modules/dids/did.controller.js - Dialer control
src/modules/dialer/dialer.controller.js - Telephony workflows
src/modules/telephony/telephony.controller.js - Call processing
src/modules/telephony/telephony.service.js - AI agent workflows
src/modules/ai-agents/aiAgent.controller.js
Billing and integrations
- Orders
src/modules/orders/order.routes.js - Billing plans
src/modules/billing/billing.routes.js
Other components
- API client
- MongoDB
src/config/db.js - Meta Graph API
- OBD CMS
- Asterisk interfaces
- AI pipeline
Connections 27
- API client → Express application: sends requests
- Express application → Authentication: routes requests
- Authentication → Auth handlers: dispatches
- Express application → Access middleware: applies access checks
- Express application → Company management: routes requests
- Express application → Company users: routes requests
- Express application → Roles and permissions: routes requests
- Express application → Admin users: routes requests
- Express application → Lead management: routes requests
- Express application → Platform integrations: routes requests
- Express application → Meta campaigns: routes requests
- Express application → IVR campaigns: routes requests
- Express application → DID management: routes requests
- Express application → Dialer control: routes requests
- Express application → Telephony workflows: routes requests
- Express application → AI agent workflows: routes requests
- Express application → Orders: routes requests
- Express application → Billing plans: routes requests
- Lead management → Lead data: reads and writes
- Meta campaigns → Meta Graph API: requests campaign data
- IVR campaigns → OBD CMS service: calls campaign operations
- OBD CMS service → OBD CMS: manages campaigns
- Telephony workflows → Call processing: calls processing
- Telephony workflows → Asterisk interfaces: fetches call logs
- Telephony workflows → AI pipeline: submits call workflows
- AI agent workflows → AI pipeline: proxies pipeline calls
- Dialer control → Asterisk interfaces: controls calls