Heroes Profile icon

Heroes Profile

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

NexusGaming → Player Profile

AI-generated

Overview

The "Player Profile" operation of the NexusGaming resource in this node fetches detailed player profile data from the Heroes Profile API. It normalizes the data into a REST API style JSON format, making it easier to consume and integrate into workflows. This node is useful for scenarios where you want to retrieve competitive or statistical information about a specific player in the Nexus Gaming community, such as tracking player performance across seasons, divisions, or regions.

Practical examples include:

  • Displaying a player's profile stats on a dashboard.
  • Analyzing player progress over different seasons.
  • Filtering player data by division or region for tournament management.

Properties

Name Meaning
Season Enter a season number (optional). Filters the profile data to a specific competitive season.
Division Select a division (optional). Options include Storm, Heroic, Nexus, Divisions A through E with East/West variants. Filters the profile data by division.
Battletag Enter a battletag (required). The unique identifier of the player whose profile is being fetched.
Region Select a region (required). Options are North America, Europe, Korea, China. Filters the profile data by geographic region.

Output

The node outputs JSON data representing the player's profile information retrieved from the Heroes Profile API. This includes normalized statistics and metadata about the player relevant to the selected season, division, and region. The output structure follows a REST API style JSON format, which typically contains fields such as player stats, rankings, match history, and other profile details.

No binary data output is indicated for this operation.

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: Ensure that the API key credential is correctly set up and valid.
  • Invalid battletag or region: The node requires a valid battletag and region; incorrect values may result in errors or empty responses.
  • Network issues: Connectivity problems can cause request failures; verify network access to the Heroes Profile API endpoint.
  • Empty or malformed response: If the API returns unexpected data, check if the requested season or division exists or if the battletag is correct.

Links and References

Discussion