Actions7
Overview
The node "Game Boost" integrates with the Game Boost API to retrieve and manipulate game account data. Specifically, the "Get All Accounts" operation fetches multiple user accounts associated with a specified game or all games on the platform. It supports pagination to efficiently handle large datasets and can optionally include detailed in-game data such as skins, gems, achievements, and levels.
This node is beneficial for scenarios where you need to analyze or manage bulk game account information, such as:
- Aggregating user account statuses for reporting.
- Exporting account data for marketing or customer support.
- Synchronizing game account details with other systems.
- Monitoring account lifecycle stages (e.g., Draft, Listed, Sold).
Example use case: A game marketplace operator wants to pull all active accounts listed for sale in a particular game to update their inventory dashboard.
Properties
| Name | Meaning |
|---|---|
| Game Name or ID | Select the specific game by name or ID from a dynamically loaded list of available games on the platform. |
| All Games | Boolean flag to indicate whether to retrieve accounts across all games instead of a single selected game. |
| Get All Accounts | Boolean flag to determine if the node should fetch all accounts using pagination or just return the first 10 accounts. |
| With Account In-Game Data | Boolean flag to include detailed in-game data (such as skins, gems, achievements, levels) for each account in the response. |
| Status | Filter accounts by their status. Options include: All, Draft, Listed, Pending, Processing, Refunded, Sold. |
Additional informational notices are included in the UI to guide users about potential delays when fetching large datasets and to provide community support links.
Output
The output is an array of JSON objects representing game accounts matching the query parameters. Each object contains account details such as identifiers, status, and optionally enriched in-game data if requested.
If the "Get All Accounts" option is enabled, the node handles pagination internally and returns all matching accounts; otherwise, it returns only the first page (up to 10 accounts).
No binary data output is indicated by the source code.
Dependencies
- Requires an API key credential for authenticating with the Game Boost API.
- The node depends on internal methods to load options dynamically (e.g., game slugs).
- Pagination and data retrieval logic are handled by an external execute function imported as
executeGameboost. - No additional external services beyond the Game Boost API are required.
Troubleshooting
- Long execution times: Enabling "Get All Accounts" with many records may cause slow responses due to pagination. Consider filtering by game or status to reduce data volume.
- Empty results: Ensure the correct game slug or ID is selected and that the account status filter matches existing accounts.
- Authentication errors: Verify that the API key credential is correctly configured and has sufficient permissions.
- Invalid property values: Use the provided dropdowns or expressions to specify valid game IDs and statuses.
Common error messages likely relate to API connectivity, invalid credentials, or exceeding rate limits. Checking API key validity and network access usually resolves these issues.