Removed chatbot integrations: Chatwoot, Typebot, OpenAI, Dify, Flowise, and EvoAI.
Only N8N integration remains active.
Changes include:
- Deleted all integration directories and files (controllers, services, DTOs, validators, routers)
- Updated chatbot.controller.ts to only emit to N8N
- Updated chatbot.router.ts and chatbot.schema.ts to export only N8N
- Removed OpenAI dependency from N8nService (removed audio transcription)
- Updated server.module.ts to remove all chatbot service instantiations
- Cleaned monitor.service.ts and channel.service.ts from chatbot references
- Removed chatbot properties from DTOs and validation schemas
- Removed LocalChatwoot type and TYPEBOT events from wa.types
- Cleaned PostgreSQL Prisma schema: removed 12 models and 2 enums
- Removed chatbot relations from Instance model
- Removed Chatwoot fields from Message model
N8N remains as the only supported chatbot integration.
Remove the EvolutionBot chatbot integration as it is no longer needed.
The project now supports only external chatbot integrations: Chatwoot, Typebot, OpenAI, Dify, Flowise, N8N, and EvoAI.
Changes:
- Deleted EvolutionBot directory with all files (controller, service, router, dto, schema)
- Removed EvolutionBot models from Prisma schemas (postgresql and mysql)
- Updated ChatbotController to remove evolutionBotController.emit() call
- Updated ChatbotRouter to remove EvolutionBot route
- Cleaned up imports and exports in server.module.ts
- Updated documentation (CLAUDE.md, AGENTS.md)
Note: Prisma migrations will be created separately to drop EvolutionBot and EvolutionBotSetting tables from the database.
- Introduced Kafka support in the Evolution API, allowing for real-time event streaming and processing.
- Updated environment configuration to include Kafka-related variables.
- Added KafkaController and KafkaRouter for managing Kafka events.
- Enhanced event management to support Kafka alongside existing integrations.
- Updated database schemas and migrations for Kafka integration in both MySQL and PostgreSQL.
- Documented Kafka integration in the README file.
- Add pgbouncer service to handle connection pooling
- Update database connection URIs to support direct and pooled connections
- Optimize postgres configuration with better memory settings
- Update prisma schema to support directUrl connection
- Introduced a new optional `lid` field in the IsOnWhatsapp model to enhance data tracking.
- Updated migration script to add the `lid` column to the database.
- Modified OnWhatsAppDto to include the `lid` property for better integration with WhatsApp user data.
- Enhanced the WhatsApp Baileys service to handle `lid` numbers separately and improve user verification logic.
- Updated cache handling functions to support the new `lid` field for consistent data management.
- Introduced `splitMessages` and `timePerChar` fields in the Typebot and TypebotSetting models with default values.
- Created a migration script to update the database schema accordingly.
- Updated audio message handling to prepend `[audio]` to transcriptions for better clarity in message context.
- Introduced Evoai and EvoaiSetting models in both MySQL and PostgreSQL schemas.
- Implemented EvoaiController and EvoaiService for managing EvoAI bots.
- Created EvoaiRouter for handling API requests related to EvoAI.
- Added DTOs and validation schemas for EvoAI integration.
- Updated server module and chatbot controller to include EvoAI functionality.
- Configured environment settings for EvoAI integration.
- Introduced N8n and N8nSetting models in both MySQL and PostgreSQL schemas.
- Implemented N8nController and N8nService for managing N8n bots.
- Created N8nRouter for handling API requests related to N8n.
- Added DTOs and validation schemas for N8n integration.
- Updated server module and chatbot controller to include N8n functionality.
- Configured environment settings for N8n integration.
- Added NATS package to dependencies
- Created Prisma schema models for NATS configuration
- Implemented NATS controller, router, and event management
- Updated instance controller and event manager to support NATS
- Added NATS configuration options in environment configuration
- Included NATS events in instance validation schema
- Removed the unique constraint on `remoteJid` and `instanceId` in the `Chat` model to prevent potential migration failures due to existing duplicates.
- Deleted the old migration file for adding `wavoipToken` to the `Setting` table and created a new migration that includes a check for the column's existence before adding it, ensuring smoother migration processes.
- Updated migration logic to clear previous migrations related to `wavoip_token` to maintain a clean migration history.
- Added `wavoipToken` field to `Setting` model in both MySQL and PostgreSQL schemas.
- Updated `package.json` and `package-lock.json` to include `mime-types` and `socket.io-client` dependencies.
- Introduced `BaileysController` and `BaileysRouter` for handling WhatsApp interactions.
- Refactored media type handling to use `mime-types` instead of `mime` across various services.
- Updated DTOs and validation schemas to accommodate the new `wavoipToken` field.
- Implemented voice call functionalities using the Wavoip service in the Baileys integration.
- Enhanced event handling in the WebSocket controller to support new features.
