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 perform searches specifically for Twitter users. It allows you to input a search query and retrieve a list of Twitter user profiles matching that query. This is useful for scenarios such as social media monitoring, influencer discovery, or market research where you want to find relevant Twitter accounts based on keywords or topics.

For example, you could use this node to search for users related to "crypto OR bitcoin" and get up to 20 matching Twitter profiles returned.

Properties

Name Meaning
Query The search query string used to find Twitter users. Example: crypto OR bitcoin.
Count Maximum number of user results to return. Default is 20.
Timeout Timeout in seconds for the API request, between 20 and 1500 seconds. Default is 300 sec.

Output

The output is an array of JSON objects, each representing a Twitter user profile matching the search query. Each item contains the user's data as returned by the Horizon Data Wave Twitter API. The exact structure depends on the API response but typically includes user details like username, display name, bio, follower count, etc.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for the Horizon Data Wave Twitter API.
  • The node uses the base URL https://api.horizondatawave.ai.
  • The API key must include an account ID which is sent with each request.
  • Proper configuration of the API key credential in n8n is necessary for authentication.

Troubleshooting

  • No credentials provided!
    This error occurs if the API key credential is not set or missing. Ensure you have configured the required API key credential in n8n before running the node.

  • Account ID is missing in credentials!
    The API key credential must contain an account ID. Verify your credential setup includes this information.

  • API errors with HTTP status codes
    The node captures detailed API error messages including HTTP status, error headers, request IDs, and execution time. Common issues might be rate limiting, invalid queries, or timeout errors. Check the error details in the output to diagnose.

  • Timeouts
    If the request times out, consider increasing the Timeout property value within the allowed range (20-1500 seconds).

  • Empty or no results
    Make sure your query string is valid and likely to match existing Twitter users.

Links and References

Discussion