Skopon End icon

Skopon End

Builds the Skopon task completion payload from workflow results

Skopon End

AI-generated

Summary

Builds a Skopon task completion object from the configured results, task ID, client ID, status, and optional error details. Optionally POSTs that completion to a mock callback URL when a valid mission ID is supplied, then outputs the completion object for downstream nodes.

Inputs

  • Task ID (required) — Skopon task ID; defaults to the current execution ID. If blank, the node tries the execution ID again, then errors if still empty.
  • Results — JSON array or object to include in the completion. An object is wrapped in an array; blank input uses a default result item.
  • Client ID (required) — Client identifier, defaulting to request_id from the start node. Must be non-empty.
  • Status — Completion status: SUCCESS or FAILED; defaults to SUCCESS.
  • Error Code — Error code for a failed task. A code or error message is required when status is FAILED; both are cleared for SUCCESS.
  • Error Message — Error message for a failed task. A code or error message is required when status is FAILED; both are cleared for SUCCESS.
  • Mock Completion URL — Optional callback URL. When non-empty and paired with a positive integer Mock Mission ID, the node POSTs the completion to this URL.
  • Mock Mission ID — Positive integer mission ID required with Mock Completion URL to invoke the callback.
  • Mock Authorization — Optional Authorization header value for the mock callback request.

Output shape

One n8n item per input item, each containing a completion object in json.

The object contains taskId, status, errorCode, errorMessage, results, and clientId. A configured mock callback receives these values as snake_case fields plus mission_id; the Authorization header is sent only when configured. Invalid results JSON, missing required IDs, failed status without error details, or callback errors cause an operation error unless Continue On Fail is enabled.

Links

Discussion