[mysubcult]

Follow-up to #92, done the way you suggested: the bot trigger executed by the button answers the click itself, no extra webhooks. Possible now that payload_array always holds the latest update (LiveHelperChat/livehelperchat@e96276258).

Changes

Two new methods in the TelegramIntegration Rest API:

• Answer callback query — answerCallbackQuery, stops the loading spinner on the clicked button:

  {"callback_query_id": {{args.chat.incoming_chat.payload_array.callback_query.id}}}
  

• Hide inline buttons of the clicked message — editMessageReplyMarkup with an empty keyboard, so the visitor can't click the same buttons again (like in the website widget).

Usage: add a Rest API action with one or both methods to the trigger the button executes. check_not_empty skips the request if the last update wasn't a button click, so the same trigger works for website chats too. Documented in README.

Testing

Rendered both methods through erLhcoreClassGenericBotActionRestapi::makeRequest against a local echo server:

• button click payload → {"callback_query_id": "4122368201564890123"} and {"chat_id": 512345678, "message_id": 1842, "reply_markup": {"inline_keyboard": []}}
• text message payload → no request (Empty variable)

Note: main_cond from ae1f525

main_cond = message.chat.type=private is checked against the whole update, so every update without message is now rejected. Checked with isValidCondition:

update	result
private text	✅
group text	❌ (intended)
button click (callback_query)	❌
edited_message	❌
message_reaction	❌

So with the current template button clicks, edits and reactions don't reach LHC at all. Conditions in main_cond are AND-ed, so I couldn't add callback_query.message.chat.type=private as an alternative — I left it untouched for you to decide how you'd like to handle it.

🤖 Generated with Claude Code