n8n-nodes-skopon-do

Skopon DO community node for n8n. It pushes a frontend guide to HiBot, waits on the n8n resume webhook, and outputs the completed or cancelled callback payload.

Request

The node posts to:

• dev: <API Host>/dev/hibot/agent/frontend-guides/push
• all other environments: <API Host>/prod/hibot/agent/frontend-guides/push

The request contains guide_key, request_id, optional mission_id, node_id, callback_url, and tool_input. The Agent Execution Token is sent as a single Authorization: Bearer ... header.

Actions

The Action dropdown is generated from nodes/SkoponDo/actions.json. Add or remove entries there, then rebuild and redeploy the package. Removing an action value already stored in a workflow can make that workflow configuration invalid, so keep values stable when possible.

publish_social_post publishes a video to a bound social account. Its Tool Input is:

{
  "account_id": "social-binding-abc123",
  "topic": "Post title",
  "video_url": "https://cdn.example.com/video.mp4",
  "content": "Post content"
}

HiBot validates the four required fields and reports a final succeeded, failed, cancelled, or expired callback.

say_message writes one assistant message into the current project room. Its Tool Input is:

{
  "content": "任务已经完成"
}

HiBot persists and broadcasts the message before calling the n8n callback. The frontend may render the received content with a typing/SSE animation; it does not need to acknowledge the animation. If the workflow needs to wait for that visual effect, add a short 3–5 second delay after this DO node.

run_flow starts one flow for a selected project member and waits for that FlowRun to reach a terminal state. Use one DO execution per flow. Its Tool Input is:

{
  "flow_unique_id": "flow-sv-content-082",
  "project_member_id": 281,
  "launch_context": {
    "user_need": {
      "status": "selected",
      "requirement": "",
      "matched_tags": []
    },
    "solution": {
      "agent_id": "agent-rec-a",
      "resume_id": "resume-short-video-generated-097",
      "resume_name": "吕景澄"
    }
  }
}

For compatibility, flow_id is also accepted as an alias of flow_unique_id. HiBot validates the member and flow binding but does not restrict the flow type. launch_context is optional and is passed through to the target flow's mission payloads. The callback contains the target FlowRun summary and its persisted outputs.

Callback behavior

After a successful 200 or 202 push response, the node waits indefinitely. A callback with a supported terminal status (completed, cancelled, succeeded, failed, or expired) resumes the execution, immediately receives { "success": true }, and becomes the node output without field conversion.

The n8n resume webhook is a one-time endpoint. It does not provide persistent delivery_id deduplication for the rare case where a callback reaches n8n but its HTTP response is lost in transit. That guarantee requires a separate durable callback receiver.

Development

npm install
npm run build
npm run lint
npm test