Heroes Profile icon

Heroes Profile

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

Actions26

Player → Hero Stats (All)

AI-generated

Overview

The "Heroes Profile" node integrates with the Heroes Profile API to fetch and normalize player data related to the game Heroes of the Storm. Specifically, for the Player resource and Hero Stats (All) operation, it retrieves comprehensive statistics about a player's performance across all heroes. This is useful for analyzing player skill, hero usage, and performance trends.

Common scenarios include:

  • Tracking a player's overall hero stats for coaching or personal improvement.
  • Aggregating hero performance data for esports analysis.
  • Integrating player stats into dashboards or reports.

Example: A user inputs a battletag, selects a region and optionally filters by game type, then receives detailed JSON-formatted stats for all heroes played by that player.

Properties

Name Meaning
Mode Selects the response format from the API. Options: JSON or CSV.
Game Type Filters stats by game type. Options include: Quick Match, Unranked Draft, Hero League, Team League, Storm League, ARAM, or empty for no filter.
Battletag The player's battletag identifier (required).
Region The server region to query. Options: North America (1), Europe (2), Korea (3), China (5).

Output

The node outputs JSON data containing normalized player hero statistics retrieved from the Heroes Profile API. The structure typically includes aggregated stats per hero such as games played, win rates, and other performance metrics.

If CSV mode is selected, the output will be in CSV format as returned by the API.

No binary data output is indicated.

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 key credential in n8n is necessary.

Troubleshooting

  • Invalid or missing API key: Ensure the API key credential is correctly set up and valid.
  • Incorrect battletag or region: Verify the battletag format and select the correct region; otherwise, the API may return errors or empty results.
  • Unsupported game type: If filtering by game type, ensure the value matches one of the allowed options.
  • API rate limits: Excessive requests may lead to throttling; implement retries or delays if needed.
  • Response format issues: Selecting CSV mode requires handling CSV parsing downstream; otherwise, use JSON mode for easier integration.

Links and References

Note: This summary is based on static code analysis and provided property definitions without runtime execution.

Discussion