Loopman icon

Loopman

Wait for human validation on tasks created by MCP Client

Loopman

AI-generated

Summary

Poll Loopman API for human‑validated tasks and route execution based on approval decision

Inputs

  • loopmanCredentials (required) — Loopman API credentials (API key and authentication domain) required to authenticate polling requests

Output shape

a decision payload (JSON) containing the outcome ('approved', 'rejected' or 'needs_changes') and a timestamp; delivered on the corresponding output port (Approved, Rejected, Needs Changes)

Only one output port carries data; the other two are empty. The payload includes decision and optional metadata.

Examples

Example 1: Human approval of a task

Configure upstream MCP Client to create a task; Loopman node polls and returns data on the Approved output port.

Example 2: Task rejected by reviewer

Human rejects the task; Loopman node routes the decision to the Rejected output port.

Discussion