[BUG] Webhook Events (LABELS_ASSOCIATION and LABELS_EDIT) Only Triggered from Mobile Devices, Not via API
Welcome!
- [x] Yes, I have searched for similar issues on GitHub and found none.
What did you do?
I implemented routes in Python to handle the LABELS_ASSOCIATION and LABELS_EDIT webhook events. The webhook listener is correctly set up and works as expected only when label actions are performed from the mobile device running the Evolution instance.
However, when the same label changes or associations are triggered via the official API endpoint ({{baseUrl}}/label/handleLabel/{{instance}}), no webhook events are fired. This means that backend-triggered updates do not notify listeners via webhooks, which breaks expected synchronization behavior.
This issue was consistently reproduced across different instances and environments.
What did you expect?
I expected that all label updates and associations, regardless of their source (mobile app or API), would consistently trigger the corresponding webhook events (LABELS_ASSOCIATION and LABELS_EDIT). This would ensure real-time synchronization and allow external systems to react accordingly, independent of how the label changes were initiated.
What did you observe instead of what you expected?
When label modifications or associations are performed via the API (/label/handleLabel/{{instance}}), no webhook events are triggered. As a result, the external listener does not receive any LABELS_ASSOCIATION or LABELS_EDIT payloads.
This behavior deviates from the expected functionality, as the same actions executed through the mobile application do trigger the corresponding webhook events properly.
Screenshots/Videos
No response
Which version of the API are you using?
Evolution API version: v2.3.0 (latest build from develop branch)
What is your environment?
Windows
Other environment specifications
No response
If applicable, paste the log output
No response
Additional Notes
No response
sei que houve uma atualizazação de fetchlabels na versão develop mas nao consegui encontrar mais informações se resolve o disparado de eventos que como voce bem colocou tornaria possivel a sincronização de etiquetas que é o que eu busto.. Usuario poder atribuir etiqueta ao chat e a automação receber essa etiqueta para manipular o atendimento por etiquetas...
vou tentar instalar a develop pra saber sobre essa nova atualizaçao