TikHub Complete (149 Endpoints) icon

TikHub Complete (149 Endpoints)

Access ALL 149 TikHub social media data endpoints for TikTok (64), Instagram (56), YouTube (16), and X/Twitter (13)

Actions64

Overview

This node, named "TikHub Complete (149 Endpoints)", provides unified access to a wide range of social media data endpoints across four major platforms: TikTok, Instagram, YouTube, and X/Twitter. It supports 149 different API endpoints in total, allowing users to retrieve various types of data such as videos, users, analytics, posts, stories, reels, channels, tweets, timelines, and more.

The specific operation "Get single video comments data" enables fetching comments for a single video on the selected platform. This is useful for social media analysts, marketers, content creators, or developers who want to gather user engagement data, perform sentiment analysis, monitor community feedback, or build dashboards aggregating comments from multiple platforms.

Practical examples:

  • Fetching TikTok video comments to analyze audience reactions.
  • Retrieving YouTube video comments for moderation or sentiment tracking.
  • Collecting Instagram reel comments to measure engagement.
  • Getting X/Twitter tweet replies for customer support or brand monitoring.

Properties

Name Meaning
Platform Select the social media platform to work with. Options: TikTok, Instagram, YouTube, X/Twitter.
作品id/Video id (aweme_id) TikTok-specific: The unique ID of the TikTok video whose comments are to be fetched. Required.
游标/Cursor (cursor) TikTok-specific: Pagination cursor to navigate through comment pages. Optional, default 20.
数量/Number (count) TikTok-specific: Number of comments to fetch per request. Optional, default 20.
视频ID/Video ID (video_id) YouTube-specific: The unique ID of the YouTube video whose comments are to be fetched. Required.
翻页令牌/Pagination token (continuation_token) YouTube-specific: Token used for paginating through comments. Optional.

Note: The properties shown depend on the selected platform and operation. For this operation ("videocomments"):

  • TikTok requires aweme_id and optionally supports cursor and count.
  • YouTube requires video_id and optionally supports continuation_token.
  • Instagram and X/Twitter do not have specified properties for this operation in the provided data.

Output

The node outputs an array of JSON objects representing the comments data retrieved from the selected platform's API. Each item corresponds to a comment or a related data structure returned by the endpoint.

  • The output JSON structure depends on the platform and the specific API response format.
  • The node wraps the raw API response data under the .json property for each output item.
  • If the API returns nested data, it is included as-is within the JSON.
  • No binary data output is indicated for this operation.

Example output snippet (conceptual):

[
  {
    "json": {
      "comment_id": "1234567890",
      "user": {
        "id": "user_1",
        "name": "John Doe"
      },
      "text": "Great video!",
      "created_at": "2024-01-01T12:00:00Z"
    }
  },
  ...
]

Dependencies

  • Requires an API key credential for authenticating with the TikHub API service.
  • The node makes HTTP requests to https://api.tikhub.io.
  • No other external dependencies are required.
  • Users must configure the TikHub API credential in n8n before using this node.

Troubleshooting

  • Unknown operation error: If the node throws an error like Unknown operation: videocomments for platform: tiktok, verify that the operation name and platform are correctly set and supported.
  • API authentication errors: Ensure the TikHub API credential is properly configured and valid.
  • Empty or incomplete data: Check if the video ID or aweme_id is correct and that the video has comments available.
  • Pagination issues: When fetching large numbers of comments, use the cursor (TikTok) or continuation_token (YouTube) properly to paginate through results.
  • Rate limits: The TikHub API may enforce rate limits; handle errors gracefully and consider adding delays or retries.

Links and References

Discussion