Skip to content

Conversation

@Nocelli
Copy link
Contributor

@Nocelli Nocelli commented Sep 15, 2025

Summary by Sourcery

Include messageId and fromMe in the configuration object sent to the Flowise bot

New Features:

  • Add messageId to overrideConfig.vars for Flowise bot requests
  • Add fromMe flag to overrideConfig.vars for Flowise bot requests

@sourcery-ai
Copy link
Contributor

sourcery-ai bot commented Sep 15, 2025

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

The PR extends the FlowiseService payload by injecting message metadata into the overrideConfig.vars, enabling the bot to access unique message identifiers and origin context.

Entity relationship diagram for new message metadata fields in FlowiseService

erDiagram
FLOWISE_SERVICE {
  string sessionId
}
VARS {
  string messageId
  boolean fromMe
  string remoteJid
  string pushName
  string instanceName
}
FLOWISE_SERVICE ||--o{ VARS : contains
Loading

Class diagram for updated FlowiseService payload structure

classDiagram
class FlowiseService {
  +overrideConfig: object
}
FlowiseService --|> BaseChatbotService
class overrideConfig {
  +sessionId: string
  +vars: object
}
class vars {
  +messageId: string
  +fromMe: boolean
  +remoteJid: string
  +pushName: string
  +instanceName: string
}
overrideConfig --> vars
FlowiseService --> overrideConfig
Loading

File-Level Changes

Change Details Files
Include additional metadata fields in the Flowise bot request payload
  • Added extraction of messageId from msg.key.id
  • Added extraction of fromMe flag from msg.key.fromMe
src/api/integrations/chatbot/flowise/services/flowise.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

Copy link
Contributor

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey there - I've reviewed your changes and they look great!


Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

@DavidsonGomes DavidsonGomes changed the base branch from main to develop September 16, 2025 14:47
@DavidsonGomes
Copy link
Collaborator

Please, fix the lint with npm run lint

@Nocelli Nocelli closed this Sep 17, 2025
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