Actions7
- Tweet Actions
- User Actions
Overview
This node, named "X Scraper by Lab3," is designed to scrape data from the social platform "X" (formerly Twitter). Specifically, for the User resource and the Get Pending Messages operation, it retrieves pending direct messages for a specified user. It allows filtering these messages based on the minimum follower count of the message sender.
Practical scenarios where this node is useful include:
- Automating the monitoring of incoming direct messages that meet certain criteria (e.g., only messages from users with a minimum number of followers).
- Integrating message retrieval into workflows for customer support or social media management.
- Filtering and processing messages before further actions like replying or storing them.
Properties
| Name | Meaning |
|---|---|
| Minimum Follower Count | Minimum number of followers required for the message sender. Only messages from senders meeting this threshold will be retrieved. |
Output
The node outputs an array of JSON objects representing the pending messages that match the filter criteria. Each object corresponds to a single message and contains details about the message and its sender.
- The exact structure of each message object depends on the underlying scraper implementation but typically includes fields such as message content, sender information, timestamps, and possibly metadata related to the message status.
- This node does not output binary data.
Dependencies
- Requires an API key credential with authentication tokens and cookies necessary to access the X platform's data.
- The node expects credentials containing at least the following tokens: guest ID, kdt, twid, ct0, and auth token.
- No additional external services are explicitly required beyond the authenticated access to the X platform.
Troubleshooting
- Missing Credentials Error: If the required authentication tokens are missing in the provided credentials, the node will throw an error listing which tokens are absent. Ensure all required tokens are correctly configured in the credential.
- Failed Initialization: Errors during scraper initialization indicate issues with authentication or network connectivity. Verify that the API keys and tokens are valid and that the network connection to the X platform is stable.
- Empty or Unexpected Output: If no messages are returned, check that the username associated with the credentials has pending messages and that the minimum follower count filter is not too restrictive.
- Continue On Fail: If enabled, the node will continue processing other items even if one fails, returning error details in the output JSON.
Links and References
- X Platform Developer Documentation (for general API concepts; note that this node uses scraping techniques)
- n8n Documentation for guidance on using credentials and handling node errors