Heroes Profile icon

Heroes Profile

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

Actions26

Player → MMR Data (by Role)

AI-generated

Overview

This node fetches Matchmaking Rating (MMR) data for a player in the game "Heroes of the Storm," specifically filtered by the player's role. It queries an external API to retrieve detailed MMR statistics based on the selected role, game type, region, and battletag. This is useful for players or analysts who want to track performance metrics segmented by roles such as Tank, Bruiser, Healer, etc., helping them understand strengths and weaknesses in different gameplay contexts.

Practical examples:

  • A player wants to see their MMR as a Healer in Hero League matches in North America.
  • An esports analyst gathers MMR data for multiple players focusing on the Ranged Assassin role to compare skill levels.
  • A coach tracks team members’ MMR trends by role to optimize team composition.

Properties

Name Meaning
Role Select the player's role to filter MMR data. Options: Tank, Bruiser, Ranged Assassin, Melee Assassin, Healer, Support
Mode Choose the response format from the API. Options: JSON, CSV
Game Type Select the type of game mode. Options: Quick Match, Unranked Draft, Hero League, Team League, Storm League, ARAM
Battletag Enter the player's unique battletag identifier
Region Select the server region. Options: North America, Europe, Korea, China

Output

The node outputs JSON or CSV data containing the MMR statistics for the specified player role and filters. The JSON output typically includes structured fields representing MMR values, ranks, and possibly additional metadata related to the player's performance in that role. If CSV mode is selected, the output will be a CSV-formatted string with similar data.

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 within n8n is necessary for authentication.

Troubleshooting

  • Missing or invalid API key: The node will fail if the API key credential is not set or invalid. Ensure the API key is correctly configured.
  • Invalid battletag or parameters: If the battletag or other required parameters are missing or incorrect, the API may return errors or empty results. Double-check input values.
  • Unsupported region or role: Selecting unsupported or empty options might cause the API to reject the request or return no data.
  • Network issues: Connectivity problems can cause request failures; verify network access to the API endpoint.
  • Response format mismatch: Choosing CSV mode but expecting JSON output (or vice versa) can lead to parsing errors downstream.

Links and References

Discussion