All nodes/Integrations/VK / VK Teams

VK Config

Selects a saved VK connection (community/user access_token) 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 connection. It is needed when several Send VK Message nodes post from the same community, or when you want the canvas to show whose voice the workflow speaks in. A graph with a single message does not need it — the send node carries a “VK connection” field of its own.

Do not confuse it with VK Teams Config: VK is vk.com and its communities, while VK Teams is a corporate messenger with bots of its own. Their tokens differ, and one kind of connection wired into the other’s port will not do.

How it works

The credentials — a community or user access token plus an API version — live under Settings → Integrations. This node references that record and, during a run, passes the resolved settings along the wire into the vk_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. Only the connection name is left in the run log.

The API version comes from the integration; when that field is left empty, the send node falls back to its own default version.

Common mistakes

• A token without the rights you assumed. What a token may do is VK’s decision. There is no “Check connection” button here — only mail and DAV have one — so missing rights surface on the first send.
• A user token where a community was meant. Whose name the message goes out under follows from the token type, not from the node.
• An empty “Connection” field. The node fails at run time.
• A connection of another kind in the port. Whatever you wire into vk_config is what arrives: with a VK Teams connection the send node stops, reporting that there is no VK access token.
• One community, one node. Two communities need two config nodes; a single one can feed any number of sends.

Inputs

—

Outputs

Configuration