All nodes/Integrations/VK
VK Get File
Downloads a VK message attachment and stores it as a file reference usable by an LLM/vision node or for sending back. Takes a conversation_message_id from the recorded history ({{ nodes.vk_history_1.rows[0].platform_message_ref }}): VK's links expire, so the history keeps an attachment reference rather than a URL and the message is re-read for a fresh link.
Type in the graph: vk_get_file
Exec
An error output can be enabled to handle failures on their own path.
Try it
Minimal working scenario
- Execute
- Execute + Data
Pick your own connection or knowledge base first — the graph carries REPLACE_ME.
Inputs
| Port | Wire | Payload | Notes |
|---|---|---|---|
VK connectionvk_config | Datadata | — |
Outputs
| Port | Wire | Payload | Notes |
|---|---|---|---|
Fileoutput | Execute + Dataexecute_data | file | |
Erroron_error | Execute + Dataexecute_data | — | shown when expose_error_output = true |
Configuration
| Field | Type | Default | Description |
|---|---|---|---|
VK connectionconnection_id | string | "" | Saved workspace VK connection. A node wired to the 'vk_config' port wins over this field. connection: vkoverridden by port: vk_config |
Message IDconversation_message_id | string | "" | conversation_message_id of the message carrying the attachment — the platform_message_ref field of history records ({{ nodes.vk_history_1.rows[0].platform_message_ref }}). supports templates |
Peer IDpeer_id | string | "" | peer_id of the conversation or direct chat. Blank = the chat of the running VK turn (a run started anywhere else then fails: there is no chat to infer). VK peer_id: a user id (12345), a community with a minus (-98765), a conversation is 2000000000 + its number (conversation 5 → 2000000005). Templates are supported supports templates |
| Advanced | |||
Attachment indexindex | integer | 0 | Which of the message's attachments to download when there are several (0 = the first). |
Shared fields
Every node has these three — the platform adds them, not the node author.
expose_error_output— When enabled, show an execution output to connect nodes that run if this step fails.