Robolly icon

Robolly

Get Data From Robolly

Overview

The node "Robolly" integrates with the Robolly service to generate videos based on predefined templates. It allows users to select a video template, customize elements within that template, and specify output video parameters such as format, duration, and frame rate. This node is useful for automating video creation workflows where dynamic content needs to be rendered into video format, such as marketing videos, social media clips, or personalized video messages.

Typical use cases include:

  • Generating promotional videos by filling in template placeholders with custom text or images.
  • Creating short video snippets with specific durations and frame rates.
  • Converting generated videos into different encoding formats locally for compatibility or compression purposes.

Properties

Name Meaning
Video Template Name or ID Select a video template from a list or specify its ID via expression. This defines the base video structure to generate.
Video Format Output video container format. Currently supports MP4 (.mp4) which offers wide compatibility and good compression.
Duration Length of the generated video in seconds.
FPS Frames per second for the video. Options: 24, 30, 50, 60 FPS. Determines smoothness and quality of motion.
Change Encoding Optionally convert the generated video locally into one of several formats/codecs: GIF, WebM, WebP, AV1, H.264 (AVC), HEVC (H.265), VP9, or no conversion.
Change File Extension When converting encoding, optionally change the file extension of the output video file. Options include keeping it same as encoding or forcing MP4 extension.
JSON Data (When movieGeneration mode is enabled) Raw JSON data for API integration to manually request video generation.
Attempts Number of retry attempts when requesting the resource URL during movie generation mode.
Template Elements A collection of elements within the selected video template to modify. Each element has a name/ID and a value to set, allowing customization of text, images, or other dynamic parts of the video template.
Hidden Render Link Whether to encode the render link in Base64 to create a hidden render link, used for obfuscation or security.
Movie Generation Boolean flag to switch between standard video generation and manual API integration using JSON data.

Output

The node outputs an array of items, each containing a json property with the result of the video generation operation. The exact structure depends on the operation but typically includes metadata about the generated video and possibly URLs or binary references to the video file.

If the node performs local video encoding conversion, the output will reflect the converted video format accordingly.

Binary data output is not explicitly detailed but may be present if the node handles video files directly.

Dependencies

  • Requires an API key credential for authenticating with the Robolly service.
  • Depends on Robolly's API endpoints for fetching templates, template elements, and generating videos.
  • Local video encoding conversions imply dependencies on local codecs or libraries capable of performing these conversions (not detailed in the source).
  • n8n environment must have internet access to communicate with Robolly APIs.

Troubleshooting

  • Common Issues:

    • Invalid or missing API credentials will cause authentication failures.
    • Specifying a non-existent template or element ID will result in errors or empty results.
    • Network issues can cause request timeouts; the "Attempts" property helps mitigate transient failures.
    • Incorrect video format or encoding options might lead to unsupported output files.
  • Error Messages:

    • Authentication errors: Verify API key validity and permissions.
    • Template not found: Check the template ID or name correctness.
    • Element modification errors: Ensure element names/IDs exist in the chosen template.
    • Conversion failures: Confirm local environment supports requested encoding formats.

Links and References


This summary is based solely on static analysis of the provided source code and property definitions.

Discussion