mirror of
https://github.com/EvolutionAPI/evolution-api.git
synced 2025-12-26 15:17:44 -06:00
refactor: remove Evolution Channel provider integration
Remove the Evolution Channel provider from WhatsApp integrations as it is no longer needed. Only Baileys and Meta Business API providers are now supported. Changes: - Deleted Evolution Channel service, controller, and router files - Updated ChannelController factory to remove Evolution provider case - Removed Integration.EVOLUTION from type definitions - Updated channel router to remove Evolution routes - Cleaned up imports and exports in server.module.ts - Updated documentation (CLAUDE.md, AGENTS.md, integration-channel-rules.mdc) Note: EvolutionBot chatbot integration remains unchanged (different component)
This commit is contained in:
@@ -7,7 +7,6 @@ This file provides comprehensive guidance to Claude AI when working with the Evo
|
||||
**Evolution API** is a powerful, production-ready REST API for WhatsApp communication that supports multiple WhatsApp providers:
|
||||
- **Baileys** (WhatsApp Web) - Open-source WhatsApp Web client
|
||||
- **Meta Business API** - Official WhatsApp Business API
|
||||
- **Evolution API** - Custom WhatsApp integration
|
||||
|
||||
Built with **Node.js 20+**, **TypeScript 5+**, and **Express.js**, it provides extensive integrations with chatbots, CRM systems, and messaging platforms in a **multi-tenant architecture**.
|
||||
|
||||
@@ -67,7 +66,7 @@ npm test # Run tests with watch mode
|
||||
### Core Structure
|
||||
- **Multi-tenant SaaS**: Complete instance isolation with per-tenant authentication
|
||||
- **Multi-provider database**: PostgreSQL and MySQL via Prisma ORM with provider-specific schemas and migrations
|
||||
- **WhatsApp integrations**: Baileys, Meta Business API, and Evolution API with unified interface
|
||||
- **WhatsApp integrations**: Baileys and Meta Business API with unified interface
|
||||
- **Event-driven architecture**: EventEmitter2 for internal events + WebSocket, RabbitMQ, SQS, NATS, Pusher for external events
|
||||
- **Microservices pattern**: Modular integrations for chatbots, storage, and external services
|
||||
|
||||
@@ -81,7 +80,7 @@ src/
|
||||
│ ├── dto/ # Data Transfer Objects (simple classes)
|
||||
│ ├── guards/ # Authentication/authorization middleware
|
||||
│ ├── integrations/ # External service integrations
|
||||
│ │ ├── channel/ # WhatsApp providers (Baileys, Business API, Evolution)
|
||||
│ │ ├── channel/ # WhatsApp providers (Baileys, Business API)
|
||||
│ │ ├── chatbot/ # AI/Bot integrations (OpenAI, Dify, Typebot, Chatwoot)
|
||||
│ │ ├── event/ # Event systems (WebSocket, RabbitMQ, SQS, NATS, Pusher)
|
||||
│ │ └── storage/ # File storage (S3, MinIO)
|
||||
@@ -99,7 +98,6 @@ src/
|
||||
**Channel Integrations** (`src/api/integrations/channel/`):
|
||||
- **Baileys**: WhatsApp Web client with QR code authentication
|
||||
- **Business API**: Official Meta WhatsApp Business API
|
||||
- **Evolution API**: Custom WhatsApp integration
|
||||
- Connection lifecycle management per instance with automatic reconnection
|
||||
|
||||
**Chatbot Integrations** (`src/api/integrations/chatbot/`):
|
||||
|
||||
Reference in New Issue
Block a user