Actions7
Overview
The "Get Owned Games" operation for the Steam resource retrieves a list of games owned by a specific Steam user. This node is useful for automating workflows that require information about a user's Steam game library, such as generating reports, syncing game data with other services, or personalizing content based on owned games.
Example scenarios:
- Fetching a user's owned games to recommend new titles.
- Creating a dashboard showing all games in a user's Steam library.
- Integrating Steam game ownership data into a gaming community platform.
Properties
| Name | Type | Meaning |
|---|---|---|
| Steam ID | String | The unique identifier for a Steam user. Required to fetch the list of owned games. |
| Simplify | Boolean | Whether to return a simplified version of the response instead of the raw data. Defaults to false. |
Output
- json:
- If "Simplify" is enabled, the output contains a streamlined list of owned games with essential details (such as app IDs and names).
- If "Simplify" is disabled, the output includes the full raw response from the Steam Web API, which may contain detailed metadata about each game and additional fields.
Note: The node does not output binary data.
Dependencies
- External Service: Requires access to the Steam Web API.
- API Key: You must configure n8n with valid Steam API credentials (
steamApi). - n8n Configuration: Ensure the Steam API key is set up in your n8n credentials.
Troubleshooting
- Invalid Steam ID: If an incorrect or non-existent Steam ID is provided, the node may return an error or an empty list. Double-check the Steam ID format and value.
- Missing API Key: If the Steam API credential is not configured, the node will fail to authenticate. Add your Steam API key in n8n's credentials section.
- API Rate Limits: Excessive requests may be throttled by Steam. If you encounter rate limit errors, reduce the frequency of your requests.