Scrape Creators icon

Scrape Creators

Get real time social media data

Overview

The node "Scrape Creators" provides real-time social media data scraping capabilities across multiple platforms, including Truth Social. Specifically, the "Get TruthSocial User Posts" operation retrieves posts from a specified Truth Social user profile by their handle. This is useful for monitoring public content from influencers, brands, or any public profiles on Truth Social without needing official API access.

Practical examples:

  • A marketing analyst can track posts from competitors or key opinion leaders on Truth Social.
  • A social media manager can aggregate posts from multiple Truth Social handles to analyze trends or sentiment.
  • Researchers can collect publicly available posts for social studies or sentiment analysis.

Properties

Name Meaning
Handle The handle (username) of the Truth Social profile whose posts you want to retrieve. For example, "realDonaldTrump".

Output

The output contains a JSON field with the scraped posts from the specified Truth Social user. Each item in the output corresponds to a post and typically includes details such as post content, timestamps, and possibly metadata like likes or comments count depending on what the underlying scraping service returns.

If binary data were returned (e.g., images or videos), it would be included in a separate binary property, but this node primarily outputs JSON data representing textual posts.

Dependencies

  • Requires an API key credential for the Scrape Creators service.
  • The node makes HTTP requests to https://api.scrapecreators.com using this API key.
  • Proper configuration of the API key credential in n8n is necessary for authentication.

Troubleshooting

  • Common issues:

    • Invalid or missing API key will cause authentication errors.
    • Providing an incorrect or non-existent Truth Social handle may result in empty results or errors.
    • Network connectivity issues can prevent successful API calls.
  • Error messages:

    • Authentication failures usually indicate problems with the API key; verify the key is correct and active.
    • "User not found" or similar errors suggest the handle does not exist or is private.
    • Rate limiting errors may occur if too many requests are made in a short time; consider adding delays or checking API usage limits.

Links and References

Discussion