Actions59
- Facebook Actions
- Facebook Ad Library Actions
- Google Ad Library Actions
- Google Search Actions
- Instagram Actions
- LinkedIn Actions
- LinkedIn Ad Library Actions
- Pinterest Actions
- Reddit Actions
- Thread Actions
- TikTok Actions
- Truth Social Actions
- Twitter (X) Actions
- YouTube Actions
Overview
The "Scrape Creators" node provides real-time social media data scraping capabilities across multiple platforms, including Threads. Specifically, the "Get Threads User Posts" operation retrieves posts made by a user on the Threads platform based on their handle. This is useful for monitoring user activity, gathering content for analysis, or aggregating posts for marketing and research purposes.
Practical examples:
- A marketer wants to track all recent posts from a competitor's Threads profile.
- A social media analyst collects posts from influencers to analyze trends.
- A developer builds an app that displays a user's Threads posts in a custom dashboard.
Properties
| Name | Meaning |
|---|---|
| Handle | The handle (username) of the Threads profile whose posts you want to retrieve. For example, "zuck". |
Output
The node outputs JSON data containing the posts retrieved from the specified Threads user profile. Each item in the output typically represents a single post with details such as content, timestamps, and possibly metadata like likes or comments count.
If the node supports binary data output (not explicitly shown here), it would likely be related to media attached to posts (images, videos), but this is not detailed in the provided code.
Dependencies
- Requires an API key credential for authentication with the Scrape Creators service.
- The node makes HTTP requests to
https://api.scrapecreators.comusing this API key. - No other external dependencies are indicated.
Troubleshooting
Common issues:
- Invalid or missing API key will cause authentication failures.
- Providing an incorrect or non-existent Threads handle may result in empty results or errors.
- Network connectivity problems can prevent successful API calls.
Error messages:
- Authentication errors usually indicate invalid API credentials; verify and update your API key.
- "User not found" or similar errors suggest the handle does not exist on Threads.
- Rate limiting errors may occur if too many requests are sent in a short time; consider adding delays or upgrading your plan.
Links and References
- Scrape Creators API Documentation (general reference for API usage)
- Threads platform official site for understanding user handles and posts structure
Note: This summary is based solely on static analysis of the provided source code and property definitions without runtime execution.