Actions2
Overview
This node, named "StrangeLogic LLM Node," provides two main operations: generating text responses using various large language models (LLMs) and processing videos via an external video processing service. The "Process Video" operation allows users to submit a video URL along with a prompt, sending this data to a dedicated video processing API endpoint. This can be useful for scenarios such as extracting insights, generating summaries, or analyzing content from videos automatically.
Practical examples include:
- Automatically generating captions or descriptions for a given video.
- Extracting key information or highlights from video content based on a user prompt.
- Integrating video analysis into automated workflows without manual intervention.
Properties
| Name | Meaning |
|---|---|
| Video URL | URL of the video to be processed. |
| Prompt | A prompt that you want the LLM or video processor to respond to or use in processing. |
Note: For the "Process Video" operation, only "Video URL" and "Prompt" are relevant input properties.
Output
The output JSON structure contains the response returned by the external video processing API. It typically includes the processed results related to the video and prompt submitted. If an error occurs during the request, the output will contain an error field with the error message.
No binary data output is indicated for this operation.
Example output JSON structure:
{
"result": "...", // Processed video data or analysis result
"additionalInfo": "..." // Any other metadata or details from the API
}
If an error occurs:
{
"error": "Error message describing what went wrong"
}
Dependencies
- Requires an API key credential for authentication with the external services.
- Sends HTTP POST requests to the video processing endpoint at:
https://k8fm9r7b-8000.uks1.devtunnels.ms/process-video - The node expects the external service to accept JSON payloads containing the prompt and video URL and return JSON responses.
Troubleshooting
Common issues:
- Missing or invalid API credentials will cause the node to throw an error indicating no credentials were returned.
- Network errors or unreachable video processing endpoint may cause request failures.
- Invalid or inaccessible video URLs might lead to processing errors from the external service.
Error messages:
"No credentials returned!": Ensure that the required API key credential is configured correctly in n8n.- Errors from the HTTP request (e.g., timeouts, 4xx/5xx responses) will be surfaced with their message. To handle these gracefully, enable "Continue On Fail" in the node settings.
Resolution tips:
- Verify the API key credential is set up and valid.
- Confirm the video URL is publicly accessible and correctly formatted.
- Check network connectivity to the external video processing endpoint.
- Use "Continue On Fail" option to allow workflow continuation despite individual item errors.
Links and References
- No direct external documentation links are provided in the source code.
- For general guidance on video processing APIs and LLM usage, consider consulting:
- REST API Best Practices
- Large Language Models Overview
- n8n Documentation for configuring credentials and HTTP request nodes.
