Actions41
- Step/Generation Actions
- Thread Actions
- User Actions
- Dataset Actions
- Experiment Actions
- File Actions
- Prompt Actions
- Score Actions
Overview
This node integrates with the Literal AI API to manage user data within the Literal AI platform. Specifically, for the User - Delete operation, it deletes a user identified by a given User ID. This is useful in scenarios where you want to programmatically remove users from your Literal AI workspace or system, such as cleaning up test users, managing user lifecycle, or automating user management workflows.
Practical example:
You have an automated workflow that deactivates and removes users who no longer need access to your AI services. By providing their User ID to this node's delete operation, you can ensure they are removed from the Literal AI system without manual intervention.
Properties
| Name | Meaning |
|---|---|
| User ID | The unique identifier of the target user to be deleted. This must be provided as a string. |
Output
The node outputs a JSON object under the json field containing the response from the Literal AI API after attempting to delete the user. The exact structure depends on the API's response but typically confirms successful deletion or provides error details if the operation failed.
No binary data output is produced by this operation.
Example output JSON structure (conceptual):
{
"content": {
"success": true,
"message": "User deleted successfully",
"userId": "the-deleted-user-id"
}
}
or in case of failure:
{
"content": {
"error": "User not found"
}
}
Dependencies
- Requires an active connection to the Literal AI API via an API key credential.
- The node expects the API key to be configured in n8n credentials for authentication.
- No other external dependencies are required.
Troubleshooting
Common issues:
- Providing an invalid or non-existent User ID will likely result in an error from the API indicating the user was not found.
- Missing or incorrect API key credentials will cause authentication failures.
- Network connectivity issues may prevent communication with the Literal AI API.
Error messages and resolutions:
"User not found": Verify the User ID is correct and exists in the Literal AI system."Authentication failed"or similar: Check that the API key credential is correctly set up and has necessary permissions.- Timeout or network errors: Ensure your environment has internet access and the Literal AI API endpoint is reachable.
To handle errors gracefully, enable the node’s "Continue On Fail" option to allow workflows to proceed even if user deletion fails.
Links and References
- Literal AI API Documentation (hypothetical link; replace with actual if available)
- n8n documentation on API Credentials
- n8n community forums for troubleshooting and examples