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 - Add Generations operation, it allows users to add multiple generation IDs to an existing dataset by specifying the dataset's ID and a list of generation IDs.
Common scenarios where this node is beneficial include:
- Aggregating multiple AI-generated outputs (generations) into a single dataset for further analysis or processing.
- Managing datasets dynamically by appending new generations as they are created in other parts of an automation workflow.
- Organizing and curating AI-generated content efficiently within a project.
Practical example:
- After generating several text completions or image generations via an AI model, you can use this node to add all those generation IDs at once to a specific dataset for tracking and evaluation.
Properties
| Name | Meaning |
|---|---|
| Dataset ID | The unique identifier of the dataset to which generations will be added. |
| Generation IDs | A comma-separated list of generation IDs that you want to add 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 generations to the dataset. This typically includes confirmation details about the updated dataset or the added generations.
If the operation succeeds, the output structure looks like:
{
"content": {
// API response confirming the addition of generations to the dataset
}
}
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the Literal AI API.
- Requires an API key credential configured in n8n to authenticate requests to the Literal AI service.
- The node depends on the
@literalai/clientlibrary bundled internally for API communication.
Troubleshooting
- Invalid Dataset ID or Generation IDs: If the provided dataset ID or any generation ID is incorrect or does not exist, the API may return an error. Verify that all IDs are valid and correctly formatted.
- Malformed Generation IDs List: Ensure the generation IDs are provided as a comma-separated string without extra spaces or invalid characters.
- API Authentication Errors: If the API key credential is missing, expired, or invalid, authentication errors will occur. Confirm that the API key is correctly set up in n8n credentials.
- Network Issues: Connectivity problems between n8n and the Literal AI API can cause request failures. Check network access and proxy settings if applicable.
- Error Messages: The node returns error messages from the API in the output if
continueOnFailis enabled; otherwise, it throws exceptions. Review these messages for clues on resolving issues.
Links and References
- Literal AI API Documentation (hypothetical link)
- n8n Documentation on Credentials
- n8n Node Development Guide