Heroes Profile icon

Heroes Profile

Get data from Heroes Profile API and normalize it into REST API style JSON

Actions26

Hero → Hero Stats

AI-generated

Overview

The "Hero Stats" operation of the Heroes Profile node fetches detailed statistical data about heroes from the Heroes Profile API. It allows users to retrieve hero performance metrics filtered by various parameters such as game type, patch version, and grouping preferences. This node is useful for game analysts, content creators, or players who want to analyze hero statistics across different game modes and patches to inform strategy or content.

Practical examples include:

  • Retrieving hero stats for a specific patch to understand meta shifts.
  • Comparing hero performance in Quick Match versus Ranked modes.
  • Grouping hero stats by map to identify map-specific strengths or weaknesses.

Properties

Name Meaning
Mode Select the response format: JSON or CSV.
Game Type Choose the game mode to filter stats by, e.g., Quick Match, Unranked Draft, Hero League, etc.
Timeframe Type Select the patch type: Major or Minor.
Timeframe Specify the patch number (e.g., "2.65") to get stats for that particular patch.
Group By Map Boolean option to group results by map, enabling map-specific hero statistics aggregation.

Output

The node outputs JSON data containing hero statistics structured according to the selected filters. The JSON typically includes hero identifiers, performance metrics, and optionally grouped data by map if enabled. If CSV mode is selected, the output will be in CSV format representing the same data.

No binary data output is produced by this node.

Dependencies

  • Requires an API key credential for the Heroes Profile API.
  • The node makes HTTP requests to https://api.heroesprofile.com/api.
  • Proper configuration of the API credential within n8n is necessary for authentication.

Troubleshooting

  • Common issues:

    • Invalid or missing API credentials will cause authentication errors.
    • Providing an incorrect patch number or timeframe may result in empty or error responses.
    • Selecting incompatible combinations of properties (e.g., unsupported game types) might yield no data.

  • Error messages:

    • Authentication failures: Verify that the API key credential is correctly set up.
    • Request errors due to invalid query parameters: Double-check property values like patch numbers and game types.
    • Network errors: Ensure network connectivity and that the API endpoint is reachable.

Links and References

Discussion