HDW Twitter icon

HDW Twitter

Integrate with Horizon Data Wave Twitter (X) API
Join our community

Actions4

Overview

This node integrates with the Horizon Data Wave Twitter (X) API to retrieve posts made by a specified Twitter user. It is designed to fetch a list of recent tweets or posts from a given username, handle, or URL on Twitter. This functionality is useful for social media monitoring, sentiment analysis, content aggregation, or any workflow that requires automated access to a user's Twitter activity.

Practical examples include:

  • Automatically collecting the latest tweets from a public figure or brand for marketing analysis.
  • Aggregating posts from multiple users to monitor trends or topics.
  • Feeding user posts into a sentiment analysis or natural language processing pipeline.

Properties

Name Meaning
User Twitter username, handle, or URL from which to retrieve posts.
Count Maximum number of posts to return.
Timeout Timeout in seconds for the API request; must be between 20 and 1500 seconds.

Output

The node outputs an array of JSON objects, each representing a single Twitter post retrieved from the specified user. The exact structure of each post object depends on the API response but typically includes fields such as tweet content, timestamp, metadata, and engagement metrics.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for authentication with the Horizon Data Wave Twitter API.
  • The node makes HTTP POST requests to https://api.horizondatawave.ai/api/twitter/user/posts.
  • The API key must include an account ID used in requests.
  • Proper configuration of the API key credential within n8n is necessary for successful execution.

Troubleshooting

  • Missing Credentials: If no API key credential is provided or if the account ID is missing in the credentials, the node will throw an error indicating these issues.
  • Timeout Issues: Setting the timeout outside the allowed range (20-1500 seconds) may cause unexpected failures or delays.
  • API Errors: The node captures detailed API error information including HTTP status, error messages, request IDs, and execution times. Common errors might relate to invalid usernames, rate limits, or network issues.
  • Continue On Fail: If enabled, the node will output error details in the JSON output instead of stopping execution, allowing workflows to handle errors gracefully.

Links and References

Discussion