Videomatik icon

Videomatik

Create and edit data in videomatik

Actions5

Overview

This node allows you to delete a Video Request from the Videomatik platform by specifying its unique ID. It is useful in scenarios where you need to programmatically remove video requests, such as cleaning up test data, retracting obsolete requests, or managing your video request lifecycle within automated workflows.

Example use cases:

  • Automatically deleting failed or outdated video requests.
  • Integrating with other systems to ensure only relevant video requests remain active.
  • Building admin tools for content moderation or user support.

Properties

Name Type Meaning
ID String The unique identifier of the Video Request you want to delete. This field is required.

Output

The output will be a JSON object reflecting the response from the Videomatik API after attempting to delete the specified Video Request. Typically, this may include a success message, status, or error details if the deletion fails.

Example output:

{
  "success": true,
  "message": "Video Request deleted successfully."
}

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

{
  "error": "Video Request not found"
}

Dependencies

  • External Service: Requires access to the Videomatik API.
  • Credentials: You must configure the videomatikApi credential in n8n for authentication.

Troubleshooting

Common issues:

  • Invalid or missing ID: If the provided ID does not exist or is empty, the API will likely return an error such as "Video Request not found".
  • Authentication errors: If the videomatikApi credentials are not set up correctly, you may receive authentication or authorization errors.
  • Network/API errors: Issues with connectivity to the Videomatik API can result in timeout or network-related errors.

Error handling:

  • If "Continue On Fail" is enabled, errors will be returned in the output under the error field, allowing the workflow to proceed.
  • If not enabled, the node will throw and stop execution on the first encountered error.

Links and References

Discussion