Skip to content

feat(ines/phase4): Intégrations agenda — orchestration + core-n8n (P1)

idevx1 a demandé de fusionner feature/ines-backend-phase4 vers develop

Phase 4 — Intégrations agenda

Spec §9.3-9.4

OrchestrationServiceClient

Proxy complet vers /api/izemx-orchestration/agent-integrations et /user-integrations :

  • getIntegrationsByAgent, getIntegrationsByUser, getIntegrationByUid
  • createAgentIntegration, createUserIntegration
  • updateIntegration, deleteAgentIntegration, deleteUserIntegration
  • activate, deactivate, connect, disconnect, replicate
  • WebClient (aligné stack WebFlux du projet)

CoreN8nServiceClient

Proxy vers /api/izemx-core-n8n/credential/local/* (stockage BDD, sans workflow n8n) :

  • createLocalCredential → POST /credential/local/create
  • getLocalCredentials → GET /credential/local/get?userUid=&credentialType=
  • getLocalCredentialById → GET /credential/local/get/{credentialUid}
  • getCredentialUidByInstanceUid → résolution UID

IntegrationServiceImpl — flux création

  1. Si credentialData fourni → créer credential local via core-n8n
  2. Créer user-integration + agent-integration via orchestration-service
  3. Pas de logique métier dupliquée — proxy pur

Endpoints

GET    /api/phone-agent/integrations/agent/{agentUid}
POST   /api/phone-agent/integrations/agent/{agentUid}  (Header: X-USER-UID)
DELETE /api/phone-agent/integrations/{integrationUid}
POST   /api/phone-agent/integrations/{integrationUid}/activate|deactivate|connect|disconnect

Rapports de requête de fusion