skopon-media-tasks

Skopon n8n node for asynchronous media workflow tasks

Package Information

Released: this month
Downloads: 0 weekly / 0 monthly
Latest Version: 0.1.1
Author: skopon

Documentation

Skopon Media Tasks

Skopon n8n node with one action node and four operations: create task, query task, cancel task, and upload file. This package is independently implemented against the provider's public API documentation. It is not an official integration and has no separate license server. Published on npm for the team's self-hosted n8n instances; the npm package is publicly downloadable.

Local setup

cd n8n-node/skopon-media-tasks
npm install
npm test
npm pack --ignore-scripts

Install n8n-nodes-skopon-media-tasks in a self-hosted n8n instance under Settings → Community Nodes, or copy the generated .tgz into your deployment and install it from that local file. Configure Skopon Media API credentials with a provider API Key.

Operations

  • Create Task: workflow ID, optional nodeInfoList JSON, optional access password, optional Webhook URL. Returns the provider response containing data.taskId.
  • Query Task: returns status or output for an existing workflow task. This uses the provider's legacy /task/openapi/outputs endpoint because it matches the workflow creation API; the provider currently labels that query endpoint deprecated.
  • Cancel Task: cancels a queued or running workflow task.
  • Upload File: accepts n8n binary data, defaults to binary property data, and returns data.fileName. Pass that value as a node input when creating a task. The provider's upload API accepts image, audio, video, and ZIP formats.

Completion webhook (no polling)

  1. Create a separate n8n workflow with a built-in Webhook trigger. Set HTTP method to POST, choose a hard-to-guess path, and activate the workflow. The callback URL must be publicly reachable over HTTPS.
  2. Copy its production URL into Create Task → Webhook URL. The task creation response contains data.taskId; store it with your business record so the callback can be correlated.
  3. The provider sends a TASK_END callback with taskId and eventData. eventData may be a JSON string. Parse it in the receiving workflow, match taskId to the stored task, and handle duplicate callbacks idempotently.
  4. The public API documentation does not specify a callback signature. Before trusting a callback for sensitive actions, call Query Task once using its taskId to verify the result with the provider. This is event-driven verification, not periodic polling.

The Webhook workflow is independent of the create-task execution; creating a task does not keep an n8n execution waiting. Use the production callback URL rather than n8n's temporary test URL. If callbacks fail, query the task manually for recovery.

Scope and naming

The package, node, and credential names use only the internal Skopon brand. The provider domain is fixed in source code and cannot be changed from workflow inputs. The API Key is sent only to that domain. The package contains no code or assets from other community nodes.

Discussion