Skip to content

fix: Corrige envio da apiKey da instância nos payloads do Evolution Bot e N8N #1485

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
May 22, 2025

Conversation

oriondesign2015
Copy link
Contributor

@oriondesign2015 oriondesign2015 commented May 22, 2025

Corrige o envio da apiKey nos payloads do Evolution Bot e N8N para usar a apiKey específica da instância ao invés da apiKey global do sistema.

Summary by Sourcery

Fix apiKey payloads in Evolution Bot and N8N services to use the instance-specific token instead of the global system API key

Bug Fixes:

  • Use instance.token as apiKey in Evolution Bot payloads instead of the global API key
  • Use instance.token as apiKey in N8N payloads instead of the global API key

Corrige o envio da apiKey no payload do Evolution Bot para usar a apiKey específica da instância ao invés da apiKey global do sistema.
Corrige o envio da apiKey no payload do N8N para usar a apiKey específica da instância ao invés da apiKey global do sistema.
Copy link
Contributor

sourcery-ai bot commented May 22, 2025

Reviewer's Guide

The PR updates EvolutionBot and N8N integration services to use each instance’s specific API key (instance.token) in outbound payloads instead of the global system API key from configuration.

Sequence Diagram: API Key Usage in EvolutionBotService

sequenceDiagram
    participant Initiator as Initiator
    participant EvoService as EvolutionBotService
    participant Inst as Instance
    participant EvoBotExt as Evolution Bot (External)

    Initiator->>EvoService: Process Message Request
    activate EvoService
    EvoService->>Inst: Get token (instance.token)
    activate Inst
    Inst-->>EvoService: token
    deactivate Inst
    EvoService->>EvoBotExt: Send API Request (payload with apiKey from instance.token)
    deactivate EvoService
Loading

Sequence Diagram: API Key Usage in N8nService

sequenceDiagram
    participant Initiator as Initiator
    participant N8nSvc as N8nService
    participant Inst as Instance
    participant N8nExt as N8N (External)

    Initiator->>N8nSvc: Trigger Send Message Request
    activate N8nSvc
    N8nSvc->>Inst: Get token (instance.token)
    activate Inst
    Inst-->>N8nSvc: token
    deactivate Inst
    N8nSvc->>N8nExt: Send API Request (payload with apiKey from instance.token)
    deactivate N8nSvc
Loading

Class Diagram: Service Dependency on Instance for API Key

classDiagram
    class Instance {
        +token: string
        +instanceName: string
    }

    class EvolutionBotService {
        +handleMessage(msg, session, instance: Instance, remoteJid) void
    }

    class N8nService {
        +sendMessage(instance: Instance, session, msg, remoteJid, content, type, addition) void
    }

    EvolutionBotService ..> Instance : uses for API key
    N8nService ..> Instance : uses for API key
Loading

File-Level Changes

Change Details Files
Switch API key source to instance-specific token
  • Replaced global config-based API key retrieval with instance.token in EvolutionBotService payload
  • Replaced global config-based API key retrieval with instance.token in N8nService payload
src/api/integrations/chatbot/evolutionBot/services/evolutionBot.service.ts
src/api/integrations/chatbot/n8n/services/n8n.service.ts

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@DavidsonGomes DavidsonGomes merged commit 6a83e89 into EvolutionAPI:develop May 22, 2025
1 check failed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants