Actions4
- User Actions
- Search Actions
Overview
This node integrates with the Horizon Data Wave Twitter (X) API to perform searches for Twitter posts based on user-defined queries and advanced filtering options. It is useful for scenarios where you want to programmatically search tweets matching specific criteria such as keywords, phrases, hashtags, language, date ranges, user mentions, and engagement metrics like minimum likes or retweets.
Practical examples include:
- Monitoring social media sentiment around cryptocurrencies by searching tweets containing "crypto OR bitcoin".
- Finding tweets from or mentioning specific accounts within a certain timeframe.
- Filtering tweets in a particular language or with minimum engagement thresholds for marketing analysis.
Properties
| Name | Meaning |
|---|---|
| Query | The main search query string, e.g., keywords or boolean expressions like crypto OR bitcoin. |
| Count | Maximum number of tweet results to return (default 20). |
| Advanced Search Options | A collection of optional filters to refine the search: |
| - Exact Phrase | Tweets containing this exact phrase. |
| - Any of These Words | Tweets containing any of these comma-separated words. |
| - None of These Words | Tweets containing none of these comma-separated words. |
| - These Hashtags | Tweets containing these comma-separated hashtags (without #). |
| - Language | Language filter for tweets; options include English, Arabic, Chinese (Simplified), French, German, Hindi, Japanese, Korean, Portuguese, Russian, Spanish. Default is English. |
| - From These Accounts | Tweets from these comma-separated usernames. |
| - To These Accounts | Tweets sent to these comma-separated usernames. |
| - Mentioning These Accounts | Tweets mentioning these comma-separated accounts (with @). |
| - Minimum Replies | Minimum number of replies a tweet must have. |
| - Minimum Likes | Minimum number of likes a tweet must have. |
| - Minimum Retweets | Minimum number of retweets a tweet must have. |
| - From Date | Starting date/time for the search (converted to UNIX timestamp). |
| - To Date | Ending date/time for the search (converted to UNIX timestamp). |
| - Search Type | Type of search results: "Top" or "Latest". Default is "Top". |
| Timeout | Request timeout in seconds (range 20-1500, default 300). |
Output
The node outputs an array of JSON objects representing the tweets that match the search criteria. Each item corresponds to one tweet's data as returned by the Horizon Data Wave Twitter API. The structure depends on the API response but typically includes tweet content, metadata, user information, timestamps, and engagement statistics.
No binary data output is indicated.
Dependencies
- Requires an API key credential for authentication with the Horizon Data Wave Twitter API.
- The base URL for API requests is
https://api.horizondatawave.ai. - The node uses HTTP POST requests to various endpoints depending on the operation.
- The user must configure the node with valid credentials that include an account ID.
Troubleshooting
- Missing Credentials: If no API credentials are provided or the account ID is missing, the node will throw errors indicating these issues. Ensure credentials are properly set up.
- Timeouts: Requests may time out if the timeout value is too low or network issues occur. Adjust the timeout property accordingly.
- Invalid Query or Filters: Incorrectly formatted queries or filter values (e.g., malformed dates or invalid usernames) may cause API errors. Validate inputs before running.
- API Rate Limits: Excessive requests might be throttled by the API. Implement delays or reduce request frequency if encountering rate limit errors.
- Empty Results: If no tweets match the criteria, the output will be empty. Try broadening the search parameters.
Links and References
- Horizon Data Wave API Documentation (assumed base URL, check official docs)
- Twitter Search Operators: https://developer.twitter.com/en/docs/twitter-api/v1/rules-and-filtering/search-operators