Start free

All nodes/Integrations/VK

VK Tools

Tool for an AI Agent: one bounded entry point to a VK chat — reading (history, search, conversation, members) and moderation (delete, remove, pin, unpin). Each action is enabled separately, and the tool list the model sees is narrowed further by the type of the current chat. The chat comes from the config or the running turn — the model does NOT choose it. Supports dry_run. There is no ban, mute or admin promotion: VK has no such methods for a conversation. Moderation requires the community to be an administrator of the conversation. Connects to the agent's 'Agent extensions' input.

VK Tools
VK connectionAgent extension

Type in the graph: vk_tools

Try it

Minimal working scenario

Entry
AI Agent▶▦
VK Tools
LLM▦
Buffer Memory▶S
Exit▶
  • Execute + Data
  • Extension
  • LLM
  • Memory
  • Execute + Data + Streaming
Press “Copy nodes”, open the editor and hit Ctrl+V on the canvas.

Pick your own connection or knowledge base first — the graph carries REPLACE_ME.

Inputs

PortWirePayloadNotes
VK connectionvk_configDatadata—

Outputs

PortWirePayloadNotes
Agent extensiontool_outExtensionlink_extension—

Configuration

FieldTypeDefaultDescription
VK connectionconnection_idstring""

Saved workspace VK connection. A node wired to the 'vk_config' port wins over this field.

connection: vkoverridden by port: vk_config

Dry rundry_runbooleanfalse

The model 'performs' mutating actions, but VK is never called.

Enabled actionsenabled_actionsarray<string>["history","search","conversation","members"]

Which actions the model may call. Each is toggled separately, and the tool list the model actually sees is narrowed further by the type of the current chat. Only the read actions are on by default. VK has no ban, mute or admin promotion at all.

Restrict to peer IDpeer_idstring""

Pin the tool to one chat. Blank = the chat of the running turn. The model NEVER chooses the chat itself.

supports templates