SL LLMs icon

SL LLMs

StrangeLogic LLM Node
Join our community

Actions2

Overview

This node, named "SL LLMs" (StrangeLogic LLM Node), provides two main operations: generating text responses from a large language model (LLM) and processing videos. For the Process Video operation, the node accepts a video URL and interacts with an external API to process the video. The current implementation for video processing appears to simulate a 90-second wait timer and then returns a completion status message. This could be useful in workflows where you want to trigger or simulate video processing tasks that take time, such as transcoding, analysis, or extracting metadata.

Practical examples:

  • Triggering a video processing job on an external service and waiting for it to complete.
  • Integrating video content analysis into an automation workflow.
  • Simulating or pacing video processing steps within a larger pipeline.

Properties

Name Meaning
Video URL URL of the video to be processed.
Model Type Not applicable for Process Video operation (used only for text generation).
Prompt Not applicable for Process Video operation (used only for text generation).

Note: For the "Process Video" operation, only the Video URL property is relevant and used.

Output

The output JSON structure for the Process Video operation contains a simple status object indicating the completion of a simulated 90-second timer:

{
  "status": "completed",
  "message": "90-second timer completed"
}

This output signals that the video processing step (simulated by the timer) has finished. No actual video data or detailed processing results are returned by this node in its current form.

Dependencies

  • Requires an API key credential for authentication with an external AI/video processing service.
  • The node makes HTTP POST requests to an external domain specified in the credentials.
  • The external API endpoint used for video processing is ${domain}/process-video.
  • The node expects the credential to provide at least an API key and a domain URL.

Troubleshooting

  • No credentials returned!
    This error occurs if the required API key credential is not configured or accessible. Ensure that the API key credential is properly set up in n8n before running the node.

  • Timeouts or network errors during HTTP request
    Since the node waits 90 seconds per item and makes HTTP requests, network issues or slow responses may cause failures. Check network connectivity and API availability.

  • Continue On Fail behavior
    If enabled, the node will continue processing subsequent items even if one fails, returning error details in the output JSON under an error field.

Links and References

Discussion