VLM Run icon

VLM Run

Interact with VLM Run API

Execute Agent

AI-generated

Overview

The node executes an agent by sending a prompt and associated files to the VLM Run API. It supports uploading either a single file or multiple files with custom keys, then triggers the agent execution with the uploaded file URLs and a callback URL for asynchronous processing. This is useful for automating workflows where an agent processes files and returns results via a callback, such as document analysis, media processing, or custom AI agent tasks.

Use Case Examples

  1. Uploading a single file to an agent for processing and receiving results asynchronously via a callback URL.
  2. Uploading multiple files with custom keys to an agent, enabling complex workflows that require multiple inputs.
  3. Using the node to trigger an AI agent with a prompt and files, then handling the agent's output through a callback endpoint.

Properties

Name Meaning
Prompt The prompt associated with the selected agent, providing instructions or context for the agent's execution.
Multiple Files Boolean flag indicating whether to upload multiple files with custom keys instead of a single file.
File File data from the previous node to be uploaded when multiple files is false.
File Mappings Collection of custom key to file URL mappings used when multiple files is true. Each mapping includes a key (identifier) and a URL (file location).
Callback URL URL to call when the agent processing is complete, used for asynchronous notification.

Output

JSON

  • json - The JSON response from the agent execution API call, containing details about the execution result.

Dependencies

  • VLM Run API service for uploading files and executing agents

Troubleshooting

  • Ensure that when 'Multiple Files' is enabled, at least one file mapping with both key and URL is provided; otherwise, the node throws an error.
  • If uploading a single file, the file data must be correctly passed from the previous node; failure to upload or obtain a public URL will cause an error.
  • The callback URL is required and must be valid to receive asynchronous processing results; missing or invalid URLs will cause errors.

Discussion