LoomCycle Interruption
AI-generatedSummary
List LoomCycle interruptions for a user or run, or resolve a pending interruption with a human answer so the agent can continue.
Inputs
- User ID — For List for User, identifies whose interruptions to list. If empty, the node uses the credential’s Default User ID; execution fails if neither is set.
- Run ID (required) — For List for Run or Resolve, identifies the run that raised the interruption. Use the run_id from a Spawn output or Interrupt Pending trigger.
- Status — For either listing operation, filters by Answered, Cancelled, Expired, or Pending. Defaults to Pending.
- Interrupt ID (required) — For Resolve, identifies the interruption to answer. Get it from a listing result or Interrupt Pending trigger.
- Answer (required) — For Resolve, supplies the human’s answer. If the original ask specified options, the answer must match one; the server validates it.
- Resolved By — For Resolve, sets free-form audit attribution. Defaults to client when empty.
Output shape
A single n8n item containing the LoomCycle API response for a listing, or a result object for Resolve.
Listings return the API response as-is. Resolve wraps the API response in {"result": ...}; if the API returns no body, the result is {"ok":true}. Each input item is processed independently.