All nodes/Integrations/VK / VK Teams

Send VK Teams Message

Sends a text message to a VK Teams chat. Requires VK Teams Config via the 'vk_teams_config' port. chat_id and text are set in the config (templates supported).

Try it

When to use it

This node sends one text message into a VK Teams chat: a page to whoever is on duty, a report into a team chat, a signal about how a run finished. It is a graph step, not an agent tool — the node has no tool_out port, so a model cannot call it. To let the model decide, wrap the node in a WF Tool.

For vk.com communities there is a different node — Send VK Message; they are separate products with separate bots.

How it works

“Chat ID” and “Message” are template fields. A VK Teams chat id looks unfamiliar: for a direct conversation it is the user’s email (user@example.com), and for a group chat an identifier such as 681234567@chat.agent. There is no numeric id the way Telegram has one.

The node’s output is the message_id of the sent message — an opaque string rather than a number, and the handle any follow-up action on that message needs. An API refusal (unknown chat, invalid token, an unreachable server) stops the node with the description from the reply. Turn on “Error output” to handle it in the graph; without it the run ends in failure.

Common mistakes

• A VK peer id in the Chat ID field. Numeric vk.com identifiers do not work here — it is a different product.
• Expecting empty fields to be a quiet no-op. “Chat ID” and “Message” are both required: the validator says so before the run, and a template that renders empty stops the node.
• Formatting. The text is sent as plain text; markup from a model’s answer reaches the recipient with its markup characters showing.
• Attachments. The node sends text only; it has no port for files.
• A wrong base URL on the connection. A self-hosted address filled in “just in case” turns every send into a connection error.

Inputs

Outputs

Configuration