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 Threads. Specifically, the "Get Threads Post" operation allows users to retrieve detailed information about a specific Threads post by providing its URL. This is useful for scenarios such as social media monitoring, content analysis, competitive research, or archiving posts from Threads.

For example, a marketing analyst could use this node to fetch engagement metrics and content details of a particular Threads post to evaluate its performance or sentiment.

Properties

Name Meaning
URL The full URL of the Threads post you want to retrieve data from. Example: https://www.threads.com/@zuck/post/DKudiKcRO4i

Output

The node outputs JSON data containing detailed information about the specified Threads post. This typically includes metadata such as the post content, author details, timestamps, engagement statistics (likes, comments, shares), and possibly media attachments if present.

If the post contains any binary data (e.g., images or videos), it would be included in the output's binary field, allowing further processing or downloading within n8n workflows.

Dependencies

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

Troubleshooting

  • Invalid URL or Post Not Found: If the provided URL is incorrect or the post does not exist, the API may return an error or empty response. Verify the URL format and ensure the post is publicly accessible.
  • Authentication Errors: Missing or invalid API key will cause authentication failures. Ensure the API key credential is correctly set up in n8n.
  • Rate Limits: The API might enforce rate limits; excessive requests could lead to temporary blocking. Check your API usage and consider adding delays or retries.
  • Network Issues: Connectivity problems can cause request failures. Confirm network access to the API endpoint.

Links and References

Discussion