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. Specifically, for the Thread resource with the Get Threads Profile operation, it retrieves profile information of a Threads user based on their handle. This is useful for gathering public profile details such as username, bio, follower count, and other metadata from the Threads platform.
Practical examples include:
- Monitoring competitor profiles on Threads.
- Aggregating influencer profile data for marketing campaigns.
- Enriching user databases with social media profile information.
Properties
| Name | Meaning |
|---|---|
| Handle | The unique handle (username) of the Threads profile to retrieve. For example, "zuck". |
Output
The node outputs JSON data containing the profile information of the specified Threads user. This typically includes fields such as username, display name, biography, follower counts, and other publicly available profile metadata.
If the node supports binary data output, it would generally be used for profile images or media associated with the profile, but this is not explicitly indicated in the provided code snippet.
Dependencies
- Requires an API key credential for authentication with the Scrape Creators API service.
- The node makes HTTP requests to
https://api.scrapecreators.comwith appropriate headers including the API key. - No additional environment variables are indicated beyond the API key credential.
Troubleshooting
- Invalid or missing API key: Ensure that a valid API key credential is configured in n8n for this node; otherwise, authentication will fail.
- Handle not found or invalid: If the provided handle does not exist on Threads or is misspelled, the API may return an error or empty result.
- Rate limiting: The external API might enforce rate limits; excessive requests could lead to temporary blocking.
- Network issues: Connectivity problems can cause request failures; verify network access to the API endpoint.
Links and References
- Scrape Creators API Documentation (general reference for the API)
- Threads platform official site for understanding profile data structure (no direct link provided)