All nodes/Integrations/VK
VK Chat Info
Information about a conversation and its members. Actions: conversation (metadata), members (the exact list — requires the community to hold the 'administrator' access level inside that conversation), known_members (an APPROXIMATE roster from our own observations: people who never posted are missing, because VK does not report them to a community). known_members answers from our tables and needs no connection.
Type in the graph: vk_chat_info
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 |
|---|---|---|---|
Chat infooutput | Execute + Dataexecute_data | — | |
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 |
Actionaction | string | conversation | conversation — the conversation's settings and title. members — the exact participant list (requires the community's 'administrator' access level in that conversation). known_members — an APPROXIMATE list from our observations: people who never posted are not there. Options: |
Limitlimit | integer | 200 | Maximum number of records for known_members. shown when «Action» = Members (from observation) |
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 |
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.