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 datasets and their related entities. Specifically, for the "Dataset" resource and the "Add Generation" operation, it adds a generation (an AI-generated output or result) to an existing dataset by specifying the dataset's ID and the generation's ID.
This functionality is useful in scenarios where you want to organize and associate AI-generated content with datasets for further analysis, training, or processing. For example, after generating multiple AI outputs, you can add them to a dataset to keep track of all related generations in one place.
Properties
| Name | Meaning |
|---|---|
| Dataset ID | The unique identifier of the dataset to which a generation will be added. |
| Generation ID | The unique identifier of the generation that should be added to the specified dataset. |
Output
The node outputs a JSON object under the json field containing the response from the Literal AI API after adding the generation to the dataset. This typically includes confirmation details or metadata about the updated dataset.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for the Literal AI API.
- The node uses the official Literal AI client library (
@literalai/client) to interact with the API. - Proper configuration of the API key credential within n8n is necessary for authentication.
Troubleshooting
Common issues:
- Invalid or missing Dataset ID or Generation ID parameters will cause the API call to fail.
- Incorrect API key or expired credentials will result in authentication errors.
- Network connectivity problems may prevent successful communication with the Literal AI API.
Error messages:
- Errors returned from the API are captured and can be output if the node is set to continue on failure.
- Typical error messages might include "Dataset not found," "Generation not found," or "Unauthorized."
Resolutions:
- Verify that the Dataset ID and Generation ID are correct and exist in your Literal AI account.
- Ensure the API key credential is valid and has the necessary permissions.
- Check network connectivity and retry if transient errors occur.
Links and References
- Literal AI API Documentation (Assumed URL; replace with actual if known)
- n8n Documentation on Credentials
- Literal AI Client Library on npm