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 Twitter user profile information. Specifically, the "User" resource with the "Get Profile" operation allows you to fetch detailed profile data for a specified Twitter username, handle, or URL.

Common scenarios where this node is beneficial include:

  • Enriching customer data by fetching their Twitter profile details.
  • Monitoring public figures or competitors by retrieving their latest profile information.
  • Automating social media analytics workflows that require user profile metadata.

For example, you can input a Twitter handle like "elonmusk" and get back structured profile data such as name, bio, follower count, and other public details.

Properties

Name Meaning
User Twitter username, handle, or URL of the user whose profile you want to retrieve.
Timeout Timeout in seconds for the API request; must be between 20 and 1500 seconds.

Output

The output is a JSON object containing the Twitter user's profile data as returned by the Horizon Data Wave Twitter API. This typically includes fields such as username, display name, biography, follower counts, and other public profile attributes.

If multiple items are returned (though for "Get Profile" it is usually a single user), each item will be output as a separate JSON object.

The node does not output binary data.

Dependencies

  • Requires an API key credential for authentication with the Horizon Data Wave Twitter API.
  • The base URL used for requests is https://api.horizondatawave.ai.
  • The node sends POST requests to /api/twitter/user endpoint with parameters including the user identifier and timeout.
  • Proper configuration of the API key credential within n8n is necessary for successful execution.

Troubleshooting

  • No credentials provided!
    This error occurs if the required API authentication token is missing. Ensure you have configured the API key credential correctly in n8n.

  • Account ID is missing in credentials!
    The node expects an account ID within the credentials. Verify that your API key credential includes this information.

  • Timeout issues
    If the timeout value is set outside the allowed range (20-1500 seconds), the request may fail or hang. Use a valid timeout value.

  • API errors with HTTP status codes
    The node captures detailed API error messages including HTTP status, error headers, request IDs, and execution times. Review these details to diagnose issues such as rate limiting, invalid parameters, or server errors.

  • Handling failures
    If "Continue On Fail" is enabled, the node outputs error details in the JSON response instead of stopping execution, allowing workflows to handle errors gracefully.

Links and References

Discussion