VLM Run icon

VLM Run

Interact with VLM Run API

Actions8

Artifacts

AI-generated

Overview

This node operation retrieves artifacts from the VLM Run API based on the specified artifact type (agent or chat), object ID, and either session ID or execution ID. It supports fetching binary data artifacts such as images, videos, audio, documents, and URLs, and prepares them for further processing in n8n workflows. This operation is useful for workflows that need to access and utilize specific artifacts generated or stored in the VLM Run system, such as retrieving chat session data or agent execution results.

Use Case Examples

  1. Retrieve a chat artifact by providing the object ID and session ID to analyze chat session data.
  2. Fetch an agent artifact using the object ID and execution ID to process agent execution results.

Properties

Name Meaning
Artifact Type Type of artifact to retrieve, either 'agent' or 'chat'.
Object ID Object ID for the artifact in the format _<6-hex-chars>. Session ID
Execution ID Execution ID for the artifact, required when artifact type is 'agent'.
Output Binary Binary data of the retrieved artifact, prepared for use in subsequent workflow nodes. JSONobjectId - The object ID of the artifact.sessionId - The session ID associated with the artifact (for chat type).executionId - The execution ID associated with the artifact (for agent type).type - The type of artifact, derived from the object ID prefix.filename - The filename assigned to the artifact binary data. Dependencies VLM Run API service accessed via an API key credential Troubleshooting Ensure the object ID follows the required format: _<6-hex-chars>. Invalid formats will cause errors.Provide the correct session ID for chat artifacts and execution ID for agent artifacts as required.For URL artifacts, ensure the URL is accessible and returns valid content; otherwise, processing will fail.Common error messages include invalid object ID format and failure to process URL artifacts, which can be resolved by verifying input values and network accessibility.

Discussion