Videomatik icon

Videomatik

Create and edit data in videomatik

Actions5

Overview

The Videomatik node, when configured with the Template resource and the Get Compositions operation, retrieves a list of compositions associated with a specific template from the Videomatik API. This is useful in scenarios where you need to programmatically access all available compositions for a given template—such as dynamically populating dropdowns, automating video creation workflows, or integrating template data into other systems.

Practical Example:
Suppose you have a template for a marketing video and want to fetch all its possible compositions (variations) to let users select which one to use for rendering personalized videos.


Properties

Name Type Meaning
Template ID String The unique identifier of the template whose compositions you want to retrieve. Required.

Output

The node outputs a JSON array containing the compositions related to the specified template. Each item in the output represents a composition object as returned by the Videomatik API. The exact structure depends on the API response, but typically includes fields such as composition IDs, names, and possibly metadata about each composition.

Example Output:

[
  {
    "id": "composition_1",
    "name": "Intro Sequence",
    // ...other composition-specific fields
  },
  {
    "id": "composition_2",
    "name": "Outro Sequence"
    // ...other composition-specific fields
  }
]

Dependencies

  • External Service: Requires access to the Videomatik API.
  • API Key: You must configure valid Videomatik API credentials in n8n under the name videomatikApi.

Troubleshooting

  • Missing or Invalid Template ID:
    If the "Template ID" is missing or incorrect, the node will likely return an error indicating that the template was not found. Double-check the Template ID value.

  • Authentication Errors:
    If your API credentials are invalid or missing, you may receive authentication errors. Ensure that the videomatikApi credential is correctly set up in n8n.

  • API Connectivity Issues:
    Network problems or incorrect API endpoints can result in connection errors. Verify network connectivity and endpoint configuration.

  • Error Handling:
    If an error occurs and "Continue On Fail" is enabled, the node will output an object with an error field containing the error message for the failed item.


Links and References

Discussion