Actions2
- Legacy Place Actions
- Legacy User Actions
Overview
The node interacts with the Roblox Legacy API, specifically providing functionality to retrieve the username history of a specified user. This operation is useful for tracking changes in usernames over time, which can be important for audit trails, user management, or historical data analysis within Roblox-related applications.
A practical example would be an admin tool that monitors username changes for compliance or moderation purposes, or a reporting system that shows how a user's identity has evolved.
Properties
| Name | Meaning |
|---|---|
| User ID | The unique identifier of the user whose username history you want to retrieve. |
| Query Parameters | A collection of optional parameters to customize the request: |
| - Limit | Maximum number of username history records to return (minimum 1, default 10). |
| - Cursor | Pagination cursor to fetch subsequent pages of results. |
| - Sort Order | The order in which results are returned; either Ascending ("Asc") or Descending ("Desc"). |
Output
The node outputs JSON data containing the username history records for the specified user. Each record typically includes details such as the previous username, the date/time when the username was changed, and possibly other metadata related to the username change event.
If the node supports pagination, the output may also include pagination cursors or tokens to fetch additional pages of results.
No binary data output is indicated for this operation.
Dependencies
- Requires access to the Roblox Legacy API.
- An API key or authentication token credential is necessary to authorize requests to the Roblox Legacy API.
- Proper configuration of the API credentials within n8n is required to enable successful communication.
Troubleshooting
Common Issues:
- Invalid or missing User ID will cause the request to fail.
- Incorrect or expired API credentials will result in authentication errors.
- Exceeding rate limits imposed by the Roblox Legacy API may cause temporary blocking or throttling.
- Providing invalid query parameter values (e.g., negative limit) may lead to request rejection.
Error Messages:
- "User not found": Verify that the User ID is correct and exists.
- "Unauthorized" or "Authentication failed": Check API credentials and ensure they are valid and have proper permissions.
- "Invalid parameter": Review query parameters for correctness, especially limit and sort order.
- "Rate limit exceeded": Implement retry logic or reduce request frequency.
Links and References
- Roblox Developer Hub
- Roblox Legacy API Documentation (hypothetical link, replace with actual if available)