Videomatik icon

Videomatik

Create and edit data in videomatik
Join our community

Actions5

Overview

This node interacts with the Videomatik API to manage video requests. Specifically, for the Video Request resource and the Get operation, it retrieves details of a specific video request by its ID. This is useful in workflows where you need to fetch the status or metadata of a previously created video request, such as checking processing progress, retrieving results, or auditing request information.

Practical Example:
You might use this node after submitting a video creation job to periodically check the status of that job, or to retrieve the final output details once processing is complete.

Properties

Name Type Meaning
ID String The unique identifier of the video request to retrieve. (Required)

Output

The node outputs a JSON object containing the details of the requested video. The exact structure depends on the Videomatik API response, but typically includes fields such as:

{
  "id": "string",
  "status": "string",
  "createdAt": "string",
  "updatedAt": "string",
  // ...other metadata fields returned by the API
}

If an error occurs and "Continue On Fail" is enabled, the output will be:

{
  "error": "Error message string"
}

Dependencies

  • External Service: Requires access to the Videomatik API.
  • Credentials: Needs a configured videomatikApi credential in n8n.
  • Environment: No special environment variables are required beyond standard n8n setup.

Troubleshooting

Common Issues:

  • Invalid ID: If the provided ID does not exist, the API may return a "not found" error.
  • Authentication Errors: Missing or incorrect API credentials will result in authentication failures.
  • Network Issues: Connectivity problems can cause timeouts or failed requests.

Error Messages:

  • "error": "Request failed with status code 404" – The specified video request ID does not exist.
  • "error": "Unauthorized" – Check your Videomatik API credentials.
  • "error": "Network Error" – Ensure n8n can reach the Videomatik API endpoint.

How to Resolve:

  • Double-check the ID value.
  • Verify and update your Videomatik API credentials in n8n.
  • Ensure network connectivity between your n8n instance and the Videomatik API.

Links and References

Discussion