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 node "Scrape Creators" provides real-time social media data scraping capabilities across multiple platforms, including Twitter (X). Specifically, the "Get Twitter Profile" operation allows users to retrieve detailed profile information for a specified Twitter handle. This is useful for social media analysts, marketers, or developers who want to programmatically access public Twitter profile data without using the official Twitter API.
Practical examples include:
- Fetching profile details of influencers or competitors to analyze their social presence.
- Automating the collection of user profile data for sentiment analysis or audience research.
- Integrating Twitter profile data into dashboards or CRM systems.
Properties
| Name | Meaning |
|---|---|
| Handle | The Twitter username (without the '@') of the profile to retrieve. Example: "elonmusk". |
Output
The node outputs JSON data containing the Twitter profile information corresponding to the provided handle. The exact structure depends on the response from the underlying scraping service but typically includes fields such as username, display name, bio, follower count, following count, profile image URL, and other publicly available profile metadata.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential for the Scrape Creators service.
- The node makes HTTP requests to
https://api.scrapecreators.comwith appropriate headers including the API key. - Users must configure the API key credential in n8n to authenticate requests.
Troubleshooting
Common issues:
- Invalid or missing API key will result in authentication errors.
- Providing a non-existent or misspelled Twitter handle may return empty or error responses.
- Rate limits imposed by the Scrape Creators API could cause request failures if exceeded.
Error messages:
- Authentication errors typically indicate problems with the API key; verify that the key is correctly set up.
- "User not found" or similar errors suggest the handle does not exist or is private.
- Network or timeout errors may require checking internet connectivity or API service status.
Links and References
- Scrape Creators API Documentation (for detailed API usage and limitations)
- Twitter Help Center (for understanding Twitter profile data fields)