Overview
This node integrates with Tencent Video on Demand (VOD) service to manage video upload and processing tasks. It supports operations such as uploading videos from a URL, confirming the status of upload or processing tasks, composing media by merging multiple video tracks, and submitting various media processing tasks.
Common scenarios where this node is useful include:
- Automating video uploads to Tencent VOD from external URLs.
- Checking the progress or result of video upload or processing tasks.
- Combining multiple video segments into a single video file.
- Submitting custom media processing jobs like transcoding or editing.
For example, you can use this node to upload a video hosted elsewhere, then periodically confirm the upload task status until it completes successfully.
Properties
| Name | Meaning |
|---|---|
| Task ID | The unique identifier of the task to confirm its status. Required for the "Confirm" operation. |
(Note: Only the "Confirm" operation properties are listed here as requested.)
Output
The node outputs an array of JSON objects, each representing the result of the operation performed on an input item. For the "Confirm" operation, each output object contains:
success: Boolean indicating if the operation succeeded.taskId: The ID of the task that was confirmed.Response: The detailed response object returned by Tencent VOD API describing the task status and related information.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for Tencent VOD service (an API secret ID and secret key).
- Uses HTTPS requests to Tencent VOD API endpoints.
- Node configuration must include valid Tencent VOD API credentials.
Troubleshooting
- Missing or invalid Task ID: Ensure the Task ID property is provided and correct when using the Confirm operation.
- API errors: If the Tencent VOD API returns an error, the node throws an error with the message from the API. Check the error message for details such as invalid credentials, expired tasks, or malformed requests.
- JSON parsing errors: The node expects valid JSON responses from the API. Network issues or unexpected responses may cause parsing failures.
- Credential issues: Make sure the API credentials are correctly configured in n8n and have sufficient permissions.