Petals MemoryInstall

Summary

Ingests raw document text into Petals memory, using a supplied document ID or a SHA-256 hash of the content, and can replace an existing document with that ID. Set the content type and optional metadata to control how the document is stored and surfaced.

Inputs

• Content (required) — Raw document text to ingest.
• Document ID — Stable ID in your namespace. If blank, the node derives a SHA-256 ID from the content, so unchanged content produces the same ID.
• Content Type — HTML, Markdown, or Text; defaults to Markdown. HTML is converted to Markdown server-side.
• Update Existing — Whether to replace an existing document with the same ID; defaults to false.
• Additional Fields: Author — Optional author or byline.
• Additional Fields: Scope — Optional personal or reference scope; defaults to personal.
• Additional Fields: Timestamp — Optional ISO 8601 timestamp; defaults to ingestion time.
• Additional Fields: Title — Optional title shown in source listings and reference cards.

Output shape

One or more items containing the Petals API response.

The node sends one document ingestion request per input item. It wraps a single response object as one output item; if the API returns an array, each row becomes an output item. With Continue On Fail enabled, a failed input produces an item containing an error message.

Links

• n8n community nodes installation guide