LoomCycle Schedule icon

LoomCycle Schedule

Manage loomcycle substrate-native scheduled runs over HTTP

LoomCycle Schedule

AI-generated

Summary

Manage LoomCycle scheduled-run definitions: create or fork versions, retrieve or list definitions, and retire a definition. Create sets the cron, agent, and prompt; fork inherits a parent definition and applies an optional JSON overlay plus per-fire credentials.

Inputs

  • Operation (required) — Choose Create, Fork, Get, List Versions, or Retire.
  • Name (required) — Schedule definition name, used by Get, List Versions, Create, and Retire.
  • Def ID (Optional) — For Retire, optionally target a specific version; if empty, retires the active version for the name.
  • Parent Def ID (required) — For Fork, the template version to inherit.
  • Cron Expression (required) — For Create, the schedule's cron expression; the server validates it.
  • Agent Name or ID (required) — For Create, the agent spawned on each scheduled fire. The picker loads agents from the YAML configuration and AgentDef registry; expressions are supported.
  • Prompt (required) — For Create, the prompt sent on each fire. It is wrapped as trusted text by default, or as an untrusted block when Treat Prompt as Untrusted is enabled.
  • Description — Optional operator-visible description for a created or forked version.
  • Per-Fire Credentials — Optional name/value pairs injected into each scheduled run. Values are template strings; forks of templates with required credentials must supply every required key.
  • Overlay (JSON) — For Fork, a JSON object of fields to merge onto the parent definition. Per-Fire Credentials are added as user_credentials.
  • Additional Fields — For Create: Catch-Up Max limits missed fires replayed after downtime (0 means none); Enabled defaults true; Required Credentials lists keys forks must supply; Timezone sets the cron evaluation timezone; User ID and User Tier scope the run and can select a tier-specific cron; Treat Prompt as Untrusted changes prompt segment handling.
  • Promote to Active — For Create or Fork, whether to activate the new version immediately; defaults to true.

Output shape

One n8n item per input item, with the response nested under json.result for all operations.

Create and Fork send an operation-specific definition request to LoomCycle. Get returns the active row for a name; List Versions returns its versions and lineage; Retire marks the selected version, or the active version for the name, as retired. API or validation errors fail the operation unless Continue On Fail is enabled, in which case the item contains an error field.

Links

Discussion