VK TeamsInstall

Summary

Send a file to a VK Teams chat, either by uploading binary data from an input item or reusing an existing file ID. Optionally add a caption, formatting, an inline keyboard, and a reply or forwarded-message relation.

Inputs

• Chat ID (required) — Destination chat ID.
• File Source — Choose Binary to upload the file from the input item, or File ID to reuse an existing file or voice ID on the same VK Teams server.
• Input Binary Field (required) — Binary property to upload when File Source is Binary; defaults to data. The binary data must include a file name.
• File ID (required) — Existing VK Teams file or voice ID when File Source is File ID. This path does not read or upload binary data.
• Caption — Optional caption for the file.
• Formatting — Choose server parsing or explicit format ranges for the caption. Parse Mode supports None, HTML, or MarkdownV2; Format JSON supplies range data. The two formatting methods are mutually exclusive.
• Send Mode — Choose None, Reply, or Forward. Reply and Forward are mutually exclusive; fields for the other modes are ignored.
• Reply Message IDs (JSON) (required) — For Reply mode, provide a nonempty array of unique message ID strings.
• Forward Chat ID (required) — For Forward mode, provide the source chat ID.
• Forward Message IDs (JSON) (required) — For Forward mode, provide a nonempty array of unique message ID strings from the source chat. Keep IDs as strings.
• Keyboard — Optionally add an inline keyboard using configured rows and callback or URL buttons, provide a dynamic keyboard as JSON, or select None.

Output shape

One output item per input item, with the VK Teams API response in json.

The operation sends the file to the selected chat. With Binary source it uploads the selected binary field; with File ID source it passes the existing ID to VK Teams. API or validation errors fail the item, unless Continue On Fail is enabled, in which case the item contains an error field.

Links

• n8n community nodes installation guide