db-upsert

You can upsert documents by providing topic content to a workflow that verifies the database, checks for existing entries, writes or merges the content, and updates a central index.md file to stay synchronized.

Merging notes under a topic is handled by a task-driven workflow that determines the topic, checks if the document exists, merges the new content with existing records, and updates the central index.

A deterministic workflow helps database document creation by executing strict sequential tasks: verifying the database, determining the topic, checking existence, writing or merging data, and verifying the index update.

Yes, you can use TaskCreate and TaskUpdate to guide the workflow for storing topic-based records, ensuring new documents are created, existing entries are merged, and the central index remains synchronized.

You do not need an existing index.md file before upserting topic documents; the workflow verifies the database state and will update or create the central index as part of its task-driven process.

If you upsert a document for a topic that already exists, the workflow checks its existence and merges the new content with the current records, then updates the index to maintain synchronization.