Literal AI icon

Literal AI

Use the Literal AI API

Actions41

Overview

This node integrates with the Literal AI API to manage datasets and their related entities. Specifically, for the "Dataset" resource with the "Get One" operation, it retrieves detailed information about a single dataset by its unique identifier. This is useful when you want to fetch metadata, contents, or configuration of a specific dataset within your AI workflows.

Common scenarios include:

  • Fetching dataset details before processing or analysis.
  • Verifying dataset existence or properties in automation pipelines.
  • Using dataset information to conditionally branch logic in workflows.

Example: You have a dataset ID from a previous step and want to retrieve its full details to decide how to process its items further.

Properties

Name Meaning
Dataset ID The unique identifier of the dataset to retrieve. It is required to specify which dataset to get.

Output

The node outputs a JSON object under the content field containing the dataset details as returned by the Literal AI API. This typically includes dataset metadata such as name, description, type, and possibly associated items or configurations depending on the API response.

No binary data output is produced by this operation.

Example output structure (simplified):

{
  "content": {
    "id": "string",
    "name": "string",
    "description": "string",
    "metadata": { /* optional metadata object */ },
    "type": "string",
    // other dataset-specific fields...
  }
}

Dependencies

  • Requires an API key credential for the Literal AI API to authenticate requests.
  • The node uses the official Literal AI client library (@literalai/client) bundled internally.
  • No additional environment variables are needed beyond the configured API key credential.

Troubleshooting

  • Invalid Dataset ID: If the provided dataset ID does not exist or is malformed, the API will likely return an error. Verify the ID correctness.
  • Authentication Errors: Ensure the API key credential is valid and has sufficient permissions.
  • JSON Parsing Issues: Some parameters expect JSON strings; ensure proper formatting if extending usage.
  • API Rate Limits: Excessive calls may be throttled by the Literal AI service.

If errors occur, enabling "Continue On Fail" allows the workflow to proceed while capturing error messages in the output.

Links and References

Discussion