LoomCycle Memory icon

LoomCycle Memory

Read and write loomcycle substrate memory over HTTP

LoomCycle Memory

AI-generated

Summary

Read, list, create, or delete LoomCycle memory entries for a scope and scope ID. Set Entry overwrites an existing value for the same key; optional settings can request embedding computation and a time-to-live.

Inputs

  • Scope Name or ID (required) — The memory scope, such as agent or user. The picker loads scopes from LoomCycle; expressions can specify a scope dynamically.
  • Scope ID (required) — The identifier within the selected scope, such as an agent ID or user ID.
  • Key Prefix — For List Entries, return only keys that start with this prefix.
  • Limit — For List Entries, the maximum number of results; defaults to 50.
  • Key (required) — The entry key to get, set, or delete.
  • Value (required) — For Set Entry, the JSON value to store. LoomCycle stores it as supplied; Get Entry returns the stored value.
  • Compute Embedding — For Set Entry, synchronously request embedding computation using the configured embedder. The key-value entry is stored regardless of whether an embedding lands.
  • TTL Seconds — For Set Entry, how long the entry lasts in seconds. Zero (the default) means no expiry.

Output shape

A list of n8n items, each containing the operation response in its json field.

List Entries and Get Entry return the LoomCycle API response; the exact response fields are not specified here. Set Entry returns the API response, including whether an embedding landed. Delete Entry returns {"ok":true,"scope":...,"scope_id":...,"key":...}; deleting a missing entry is treated as successful. Errors are raised unless the workflow is configured to continue on fail.

Links

Discussion