LoomCycle: Run CompletedInstall

Summary

Watch LoomCycle runs for selected terminal statuses and emit matching run records as trigger items. Use SSE push for near real-time events, or polling when SSE is unavailable.

Inputs

• User ID — User to watch. If empty, uses the credential’s Default User ID; a user ID is required from one of these sources.
• Statuses — Terminal statuses to trigger on: completed, failed, or cancelled. Defaults to completed; if none are selected, the implementation watches all three.
• Transport — SSE (Push) is the default and reconnects after stream errors. Polling periodically lists runs and deduplicates by agent ID.
• Poll Interval (Seconds) — Polling frequency, from 5 to 3600 seconds; defaults to 30. Shown for Polling mode.
• Agent Name — Filter by agent name in SSE mode only.
• Parent Agent ID — Filter for runs whose parent agent ID matches; applied in both modes.
• Surface Stream Open/Close Events — In SSE mode, emit a synthetic row with __meta: "stream_close" when the stream closes or reconnects. Defaults to false.
• Reconnect Backoff (Ms) — Base delay between SSE reconnection attempts, multiplied by the attempt count up to 4×. Defaults to 1000 ms.

Output shape

Trigger items containing run-state records; polling may emit multiple records in one batch, while SSE emits each matching event as it arrives.

SSE connections are reopened after errors with backoff; after five consecutive failed attempts, the trigger emits an error. Polling stores seen agent IDs in node static data, capped at 1000, to avoid re-emitting runs. A manual SSE trigger waits up to 30 seconds for one event; a manual polling trigger checks once. If enabled, SSE stream-close metadata is emitted as a separate row.

Links

• n8n community nodes installation guide