Upsert
Upsert a single vector record in a knowledge base.
Type
kb.upsertFolder
kbChannels
Any
Pipe
Value
Scope
Any
Upsert (canvas label KB Upsert) adds or replaces one vector in a knowledge base. Same Vector ID overwrites the previous record.
The store embeds Text for you. On a Strict store, Metadata must match the defined meta fields. On a loose store, metadata is optional key/value pairs. Read only stores reject upsert.
To ingest a file or URL instead of one record, use Add Datasource.
Configure
| Setting | Description |
|---|---|
| Knowledge base | Store to write (required) |
| Vector ID | Id to create or replace (required) |
| Text | Content to embed (required) |
| Metadata | Required on Strict stores; optional key/value pairs otherwise |
Handles
| Handle | Role |
|---|---|
| In (target) | Incoming connection |
| Out (source) | Continues after the upsert |
Pipe schema
The next block reads this on the data pipe (pipe.value). The value is an object:
| Key | Type | Description |
|---|---|---|
success | boolean | Whether the upsert ran |
Use case
- Index a policy snippet or FAQ answer with a stable id.
- Keep a tagged record in sync after a table update (same id, new text and metadata).