Overview
This node fetches posts from VK (VKontakte) social network groups or user subscriptions. It can either retrieve posts from specific sources (groups or users) defined by their IDs or fetch posts from the authenticated user's subscribed groups, optionally excluding some sources.
Common scenarios include:
- Monitoring new posts in selected VK groups or pages.
- Triggering workflows based on new content from a user's VK subscriptions.
- Aggregating posts for further processing, analysis, or reposting.
For example, you could use this node to automatically collect posts from several VK groups about technology news and then send summaries via email or post them to another platform.
Properties
| Name | Meaning |
|---|---|
| Get From Subscriptions | Boolean flag to choose whether to get posts from the authenticated user's subscriptions (true) or from specified sources (false). |
| Sources | When not getting from subscriptions, specify one or more sources (VK groups/users) by their Owner ID to fetch posts from. |
| Exclude Sources | When getting from subscriptions, specify one or more sources (Owner IDs) to exclude from fetching posts. |
Notes:
- The "Sources" and "Exclude Sources" properties accept multiple entries.
- Owner ID refers to the VK group or user identifier (group IDs are negative numbers internally but passed as strings).
Output
The node outputs an array of items, each representing a VK post with the following JSON structure:
owner: Information about the post owner (group or profile), including:id: Owner ID.name: Owner's name.link: URL to the owner's VK page.
date: Timestamp of the post.text: Text content of the post.attachments: Array of attachments, each with:id: Attachment identifier.type: Type of attachment (photo,video).url: Direct URL to the attachment media.
id: Post ID.link: Direct URL to the post on VK.
If the post contains unsupported attachment types, a note is appended to the text indicating this.
Binary data output is supported for attachments such as photos and GIF videos, allowing downstream nodes to process media files directly.
Dependencies
- Requires an API authentication token credential for VK API access.
- Uses VK API version 5.199.
- The node relies on n8n's HTTP request helper with authentication support.
- No additional external dependencies beyond VK API and n8n core modules.
Troubleshooting
- Error: Unable to find owner for post — This indicates that the node could not match a post's owner ID to a known group or profile. Ensure the VK API credentials have sufficient permissions and the requested groups/profiles exist.
- Failed to find photo size for post — Occurs if the node cannot determine a valid photo URL from the post attachments. This might be due to changes in VK API response format or missing data.
- API errors with error_code and error_msg — These come directly from VK API responses. Common causes include invalid tokens, rate limits, or incorrect parameters. Check your VK API credentials and usage limits.
- If no posts are returned, verify that the specified sources or subscriptions actually contain recent posts and that the node's filtering criteria (e.g., excluding ads and pinned posts) are appropriate.