Actions7
Overview
The node "Game Boost" interacts with the Game Boost API to perform various operations related to game accounts. Specifically, the "Bulk Update Account Status" operation allows users to update the status of multiple game accounts in bulk between two specified states (e.g., from "Draft" to "Listed"). This is useful for managing large numbers of game accounts efficiently without updating each account individually.
Common scenarios include:
- Transitioning a batch of game accounts from draft mode to listed mode before making them publicly available.
- Reverting multiple accounts back to draft for further editing or review.
- Automating status updates as part of a larger workflow involving game account management.
Practical example:
- A user wants to list all draft accounts for a particular game on the platform. They select the target game and specify the status change from "Draft" to "Listed". The node processes this bulk update, saving time and reducing manual effort.
Properties
| Name | Meaning |
|---|---|
| Target Game Name or ID | The game on the platform whose accounts will be updated. Choose from a dropdown list or specify an ID via expression. |
| From | The current status of the accounts to update. Options: "Draft" or "Listed". |
| To | The new status to assign to the accounts. Options: "Draft" or "Listed". |
| Game Name or ID | Similar to "Target Game Name or ID", specifies the game context for the operation. Required field. |
Note: There is also a hidden notice property that provides links to community Discord servers for developer discussions.
Output
The node outputs JSON data representing the result of the bulk update operation. The exact structure depends on the API response but typically includes confirmation of updated accounts and their new statuses.
If the output is an array of objects containing a json property, it returns this directly; otherwise, it wraps the response in a JSON object.
No binary data output is indicated.
Dependencies
- Requires an API key credential for authenticating with the Game Boost API.
- Uses internal methods to load options dynamically, such as fetching available game slugs.
- No other external dependencies are evident from the static code.
Troubleshooting
Common issues:
- Invalid or missing API credentials will prevent successful API calls.
- Selecting a game slug that does not exist or is misspelled may cause errors or empty results.
- Attempting to update accounts when none match the "From" status could result in no changes.
Error messages:
- Authentication failures likely indicate incorrect or expired API keys.
- Validation errors if required properties like "Target Game Name or ID" or "Game Name or ID" are not provided.
- API rate limits or server errors from the Game Boost service.
Resolution tips:
- Verify API credentials are correctly configured in n8n.
- Ensure the selected game exists and matches the platform's naming conventions.
- Check network connectivity and API service status if errors persist.
Links and References
- GameBoost Official Discord Server
- Nskha Discord Server (Unofficial)
- n8n Expressions Documentation (for specifying dynamic values)