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

The node "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 64 TikTok endpoints, 56 Instagram endpoints, 16 YouTube endpoints, and 13 X/Twitter endpoints, enabling users to retrieve detailed information such as video data, user profiles, analytics, posts, stories, reels, tweets, channels, and search results.

This node is beneficial for scenarios where comprehensive social media data aggregation is needed from multiple platforms within a single workflow. For example, marketers can use it to batch fetch video statistics from TikTok and YouTube, social engagement metrics from Instagram posts, or tweet details from X/Twitter, facilitating cross-platform analysis and reporting.

Practical examples include:

  • Batch retrieving video information from TikTok to analyze trending content.
  • Gathering Instagram reel and story data for influencer marketing campaigns.
  • Fetching YouTube channel and video metadata for content performance tracking.
  • Collecting tweets and user timeline data from X/Twitter for sentiment analysis.

Properties

Name Meaning
Platform Select the social media platform to work with. Options:
- TikTok (64 endpoints): Access TikTok video, user, analytics, and shop data
- Instagram (56 endpoints): Access Instagram post, user, story, and reel data
- YouTube (16 endpoints): Access YouTube video, channel, and search data
Operation The specific operation to perform on the selected platform (not listed here but dynamically set)
Other parameters Various input parameters depending on the operation, including identifiers like video_id, username, tweet_id, channel_id, search_query, pagination tokens, counts, etc. These are used to specify which data to retrieve and how to paginate results.

Note: The node dynamically accepts many other parameters relevant to the chosen operation and platform, such as video IDs, user IDs, usernames, search queries, pagination tokens, and limits. These parameters are automatically assigned to either query parameters (for GET requests) or request body (for other HTTP methods).

Output

The node outputs an array of JSON objects representing the data retrieved from the selected social media platform's API endpoint. Each item corresponds to one piece of data returned by the API, such as video details, user profiles, tweets, or search results.

If the API response contains a data field, that is extracted and converted into the output JSON array; otherwise, the entire response is used.

The node does not explicitly handle binary data output.

Dependencies

  • Requires an API key credential for authenticating with the TikHub API service.
  • The base URL for all requests is https://api.tikhub.io.
  • The node uses internal helper functions to make HTTP requests to TikHub endpoints.
  • No additional external dependencies beyond the TikHub API and n8n core modules.

Troubleshooting

  • Unknown operation error: If the selected operation is not recognized for the chosen platform, the node throws an error indicating the unknown operation. Ensure the operation name matches one of the supported endpoints for the platform.
  • Parameter errors: Missing or invalid parameters required by the API endpoint may cause request failures. Verify that all necessary identifiers (e.g., video_id, username) are provided and correctly formatted.
  • API authentication issues: Failure to authenticate with the TikHub API due to missing or invalid API credentials will result in errors. Confirm that the API key credential is configured properly in n8n.
  • Rate limiting or quota exceeded: The TikHub API may enforce rate limits. If requests fail due to rate limiting, consider adding delays or reducing batch sizes.
  • Continue on Fail: If enabled, the node will continue processing subsequent items even if some fail, returning error messages in the output JSON for failed items.

Links and References

Discussion