Game Boost icon

Game Boost

Get data from Game Boost API

Actions7

Bulk Update Account Status

AI-generated

Overview

The node "Game Boost" interacts with the Game Boost API to perform various operations related to game accounts and statuses. Specifically, the "Bulk Update Account Status" operation allows users to update the status of multiple game accounts in bulk, transitioning them from one status category to another (e.g., from "Draft" to "Listed"). This is useful for managing large numbers of game accounts efficiently without updating each individually.

Practical scenarios include:

  • Automatically promoting a batch of game accounts from draft status to listed status after review.
  • Managing account visibility or availability on the platform by changing their status en masse.
  • Streamlining workflows where multiple accounts need synchronized status updates based on external triggers or schedules.

Properties

Name Meaning
Target Game Name or ID The specific game on the platform whose accounts you want to update. Choose from a list of available games or specify an ID.
From The current status of the accounts to be updated. Options: "Draft" or "Listed".
To The new status to assign to the accounts. Options: "Draft" or "Listed".
Game Name or ID Another field to specify the game name or ID, used in some operations including bulk update and fetching all accounts.

Note: The "Target Game Name or ID" and "Game Name or ID" fields both allow selecting a game via a dropdown loaded dynamically from the platform's available games.

Output

The node outputs JSON data representing the result of the bulk update operation. The exact structure depends on the API response but generally includes confirmation of the update action, such as counts of updated accounts or status messages.

If the output contains binary data, it would represent associated files or media linked to the accounts, but this is not indicated explicitly in the provided code or properties.

Dependencies

  • Requires an API key credential for authenticating with the Game Boost API.
  • Uses dynamic option loading methods to fetch available game slugs and account data fields from the API.
  • Must be configured with valid credentials and network access to the Game Boost service.

Troubleshooting

  • Common issues:
    • Invalid or missing API credentials will cause authentication failures.
    • Selecting a non-existent game slug or ID may result in errors or empty responses.
    • Attempting to update accounts when none match the "From" status could lead to no changes being made.
  • Error messages:
    • Authentication errors typically indicate invalid or expired API keys; reconfigure credentials.
    • Validation errors if required parameters like target game or statuses are missing.
    • Network or timeout errors suggest connectivity problems with the Game Boost API endpoint.

Links and References

Discussion