All nodes/Integrations/VK / VK Teams

VK Teams Config

Selects a saved VK Teams bot from the workspace. Credentials are configured in workspace settings, not in the graph.

Try it

When to use it

The node that holds a VK Teams bot connection. It is needed when several Send VK Teams Message nodes post as the same bot, or when you want the bot visible on the canvas. A graph with a single message does not need it — the send node carries a “VK Teams connection” field of its own.

VK Teams is a corporate messenger, not vk.com: it has its own bots and its own tokens. VK communities need VK Config instead, and the two kinds of connection are not interchangeable.

How it works

The bot token is stored as a secret under Settings → Integrations, along with an optional API base URL — needed only for a self-hosted installation of the messenger; otherwise the field stays empty and the default address is used.

This node references that record and, during a run, passes the resolved settings along the wire into the vk_teams_config port. It needs no execution input: the platform resolves the connection on first use and reuses the result for the rest of the run. The run log shows only the connection name — the token never reaches it.

Common mistakes

• An empty “Connection” field. The node fails at run time.
• A VK token instead of a VK Teams bot token. The integration form will not mix them up — they are separate kinds — but an edge from the wrong config node can still be drawn, and the send node then stops, reporting that there is no bot token.
• Filling in the base URL just in case. Set it only for a self-hosted installation: a mistyped address turns every send into a connection error.
• Expecting a connection check. VK Teams has no “Check connection” button — only mail and DAV do. A wrong token shows up on the first send.
• One bot, one node. Two bots need two config nodes; a single one can feed any number of sends.

Inputs

—

Outputs

Configuration