A Discord automation system designed to organize digital product sales, support tickets, product selection, payment workflows, and seller operations.
Commercial project: the production source code is private and is not distributed in this repository.
This project was created to automate a real Discord-based sales workflow and reduce repetitive manual work for sellers and support staff.
The bot centralizes product identification, ticket interactions, payment-method selection, seller notifications, administrative operations, and persistent configuration.
- Automated support and sales tickets
- Product/house identification inside tickets
- Portuguese and Spanish user flows
- Multiple payment workflow options
- Seller and staff notifications
- Persistent ticket and configuration data
- Discord slash commands for administration
- Product/category organization
- Bulk price-management tools
- Roblox-related purchase workflow integration
- Modular architecture separated by responsibility
- Node.js
- JavaScript
- Discord.js
- REST APIs
- JSON-based persistence
- Linux server deployment
The production application is organized into modules responsible for:
Discord Events
|
v
Ticket Workflow
|
+---- Product / House Management
|
+---- Payment Workflows
|
+---- Roblox Integration
|
+---- Administrative Commands
|
v
Persistence / Configuration
More information is available in docs/ARCHITECTURE.md.
The bot guides customers through a structured ticket flow, keeps the selected product visible to the seller, and reduces the amount of manual information gathering required during a sale.
The ticket experience supports Portuguese and Spanish, allowing the same sales workflow to serve different audiences.
Different payment methods can use different confirmation and delivery flows while sharing the same ticket infrastructure.
Sensitive payment information and production credentials are stored outside the source repository.
The private production version includes slash commands and internal tools for maintaining products, categories, prices, messages, and operational data.
Operational data is separated from application code so deployments and code updates do not overwrite production state.
Screenshots and demonstrations can be added to the screenshots/ directory.
Before publishing screenshots, make sure they do not contain:
- customer names or personal information
- payment information
- Discord IDs
- private channels
- API tokens or credentials
- internal administrative data
The source code is intentionally private because this project is being developed as a commercial product.
This public repository exists only as a technical showcase of the project, its features, and its architecture.
It does not contain the production implementation, credentials, private configuration, customer data, or internal business logic.
Active development / private commercial project.
This project is an independent software project and is not affiliated with, endorsed by, or sponsored by Discord or Roblox.