LoomCycle WebhookInstall

Summary

Create, fork, inspect, list, or retire LoomCycle inbound webhook definitions. Create and fork can promote a version to make its endpoint active; the endpoint name also supplies its path segment.

Inputs

• Operation (required) — Choose Create, Fork, Get, List Versions, or Retire.
• Name (required) — Webhook definition name and inbound endpoint path segment; used by Create, Get, List Versions, and Retire.
• Parent Def ID (required) — For Fork, the ID of the definition to branch from. Fields omitted from the overlay are inherited from the parent.
• Def ID (Optional) — For Retire, specify a particular definition version to retire. Leave blank to retire the active version for the given name.
• Agent Name or ID — For Create, agent to spawn when the webhook fires. Leave blank if publishing to a channel instead; may be set with an expression.
• Channel Name or ID — For Create, channel to publish the inbound payload to. Can be used instead of or alongside an agent; may be set with an expression.
• Enabled — For Create, whether LoomCycle serves the endpoint. Defaults to true.
• Description — Operator-visible description for a created or forked version.
• Advanced Overlay (JSON) — For Create, JSON fields such as auth, rate_limit, payload_mapping, or sync_response; agent, channel, and enabled fields override matching overlay keys. For Fork, the JSON is a diff merged onto the parent.
• Promote to Active — For Create or Fork, whether to promote the new version immediately. Defaults to true.

Output shape

A single n8n item containing a result field with the LoomCycle webhook-definition API response.

The response contents depend on the operation. Authentication secrets are referenced through environment variable names resolved by the LoomCycle deployment; plaintext secrets are not accepted in the overlay. Errors are raised as node errors unless Continue On Fail is enabled.

Links

• n8n community nodes installation guide