All nodes/Integrations/VK
VK Conversation History
Reads the recorded history of a VK chat: the messages the bot observed in a conversation or a direct chat, including those that never triggered a scenario. Needs both the 'record history' switch in the deployment AND the 'access to all correspondence' level for the community inside that conversation — otherwise the bot simply never sees the messages. A blank Peer ID means the chat of the running turn. Outputs: Messages (for LLMs), Records (raw rows: platform_message_ref — the message number within the conversation, attachments) and Transcript (plain text).
Type in the graph: vk_history
Exec
An error output can be enabled to handle failures on their own path.
Try it
Minimal working scenario
- Execute
- Execute + Data
Runs as pasted
Inputs
—
Outputs
| Port | Wire | Payload | Notes |
|---|---|---|---|
Messagesoutput | Execute + Dataexecute_data | messages | |
Recordsrows | Datadata | array | |
Transcripttranscript | Datadata | string | |
Erroron_error | Execute + Dataexecute_data | — | shown when expose_error_output = true |
Configuration
| Field | Type | Default | Description |
|---|---|---|---|
Limitlimit | integer | 50 | How many of the most recent messages to return (oldest first in the output). |
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 |
Sincesince | string | "" | Time: a relative window (24h, 7d) or ISO-8601. Blank = no bound. supports templates |
Untiluntil | string | "" | Time: a relative window (24h, 7d) or ISO-8601. Blank = no bound. supports templates |
From useruser_id | string | "" | Only messages by this author (numeric VK id). Blank = everyone. supports templates |
| Advanced | |||
Include botsinclude_bots | boolean | true | Include messages posted as the community itself. |
Include service eventsinclude_service | boolean | false | Include service events (members joining/leaving, title changes). |
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.