error in bot reply

Hello I want to report that when activating the bot reply from a flow, button, or at the end of a WhatsApp flow, no labels or custom fields are added. This only works if activated with keywords.

Would you please provide a screenshot or a short video where and when you are getting error. If possible open a support ticket by specify your issues. Thanks

Hello Support Team, I’m opening this ticket to follow up on an issue I’ve already detailed over WhatsApp. In short: Problem: When triggering our reply bot via API endpoint, at the end of another flow, from a button inside a flow, or through catalog notifications, the bot fires but fails to add/remove tags, set custom fields, or perform any of its configured actions. API Endpoint Detail: If the bot is invoked via the API endpoint without any keywords configured, it does not send at all. Workaround: Only keyword-triggered bots execute those actions correctly. Impact: Labels and fields are never updated unless the bot is invoked by a keyword, which breaks our automated workflows. Please review the WhatsApp thread timestamped 12/05 (00:30–00:48) for full context. Let me know what additional information you need or when a fix can be expected. Thank you,

I've now verified that the reply bot activated via the API only sends the first frame within the flow. Whatever we put in "Next Message" doesn't continue.

Hello, Thank you for bringing this to our attention. I’ve tested the issue on my end and was able to replicate it as well. I’ve forwarded the details to our development team, and they are now looking into it. We hope to have it resolved as soon as possible. Thank you for your patience and understanding.

Thank you. Please note this: Bots activated with API DO NOT work: Adding/removing tags Sending a webhook does not work if there are no keywords defined. I haven't tested if agent assignment works. But I think basically nothing in the initial flow works if it's with API. Nothing works either if the bot is activated from a button on ANOTHER bot. (When the user presses a button > start flow)

Okay, we will fix the issue as soon as possible. Thank you.

Hello This still doesn't work and it's a basic feature.