A VK community menu

The same menu as in Telegram, except VK differs in three places at once — and each of them quietly breaks a scenario written from memory of Telegram.

What is inside

1. Message to the community — the entry.
2. What was tapped — a branch on data.vk.payload.command. In VK a button tap is a separate event and the command arrives in payload, not as text: a scenario reading the text would silently fall through to the menu on every tap.
3. VK community — the connection node. All three outbound nodes take their access from it: one place instead of three.
4. Button menu and two ready answers.

The recipient is always stated. Unlike Telegram, an empty field on a VK node does not mean “the current chat” — which is why all three nodes reference the sender from the trigger.

What to set up for yourself

• The connection in the VK community node: replace REPLACE_ME with your own.
• Buttons, their colours and the answers. VK buttons have a colour and Telegram’s do not: make the primary action blue and leave the rest grey.
• The menu text. It deliberately says “or just write your question”: older versions of the VK app do not render keyboards, and a person without buttons must still have a way to ask.

What to connect

A VK community with messages enabled, and a community access token with permission to write. Add a connection in settings, select it in the VK community node, and enable the VK target on the Publish tab.

One thing the token does not settle: a bot’s access level inside a group chat is granted inside that chat. By default a community sees only mentions, and full access to the conversation has to be allowed by hand.