Workflows

💡TL;DR

A workflow runs existing sidebar actions in order. It can prompt for a folder or require an active editor. It is not a text pipe: each action retains its own input, output and side effects. Start with a disposable note and a dedicated folder.

Overview

The shipped One-Click Extract definition is:

One-Click Extract::process-current-add-links>batch-generate-from-titles>batch-mermaid-fix

1. Add links to the active note; create concept notes when a concept folder is configured.
2. Generate content for eligible notes in the configured concept folder, or the folder selected for the batch step. This includes eligible notes already in that folder.
3. Repair Mermaid blocks in the batch generation's complete folder.

The default workflow does not perform web research. Generation can use research only when that separate generation setting is enabled. See batch processing for folder scope and output behavior.

How It Works

Workflow Execution Pipeline

Steps run sequentially. The sidebar reports the active step and any failure. Cancellation stops further steps and propagates to supported request paths. Already completed file writes remain; a workflow has no all-or-nothing rollback.

Folder context is explicit: the configured concept folder is the initial preference, batch generation records its source and complete folder, and the following Mermaid repair uses that complete folder. Other actions retain their own active-file, selection or interactive prerequisites.

DSL Format

Use one named button per line. :: separates the display name from the action list; > separates actions. Empty lines and lines beginning with # are ignored. Unknown action IDs are rejected.

Extract and diagram::extract-concepts-current>summarize-as-mermaid

Use the settings workflow builder to select available actions, or edit the DSL directly. Action IDs are stable identifiers; display labels follow the UI language. Folder variants have their own IDs rather than a general string-substitution rule.

Identifier	Action / prerequisite
process-current-add-links	Add links to the active note
process-folder-add-links	Add links within a selected folder
extract-concepts-current	Extract concepts from the active note
extract-concepts-folder	Extract concepts within a selected folder
generate-from-title	Generate content using the active note's title
batch-generate-from-titles	Generate content for eligible folder notes
research-and-summarize	Research a selection or title in an open Markdown editor
summarize-as-mermaid	Summarize the active supported input as Mermaid
generate-diagram	Select several chart types in one run and choose multiple output formats independently for each type. Unchecking a type retains its format preferences; leaving every type unchecked uses automatic analysis.
preview-diagram	Open the preview for a supported diagram source or artifact
translate-current-file	Translate the active supported file
batch-translate-folder	Translate a selected folder
extract-original-text	Extract specified original passages
batch-extract-original-text	Extract passages from eligible folder files
split-note-by-chapters	Split the active note by chapters
batch-mermaid-fix	Repair Mermaid code blocks in a selected folder
fix-formula-current	Normalize formula delimiters in the active note
batch-fix-formula	Normalize formula delimiters in a selected folder
check-duplicates-current	Check the active note for duplicates
check-remove-duplicate-concepts	Review and remove duplicate concepts interactively
test-llm-connection	Test the configured provider
probe-slide-export-env	Check the local slide export environment
export-slides	Export the active file as slides

Predefined vs. Custom Workflows

One-Click Extract is the shipped default. Additional buttons are your own definitions. Search Notemd settings for workflow configuration, give the button a name, select and order its actions, then inspect its sidebar tooltip before running it. A parser error should be corrected before relying on the intended chain.

Configuration

Setting	Default	Effect
customWorkflowErrorStrategy	stop_on_error	Stop the chain on the first reported step failure
useMultiModelSettings	false	Use the active provider until task-specific routing is enabled
enableResearchInGenerateContent	false	Keep web research out of title generation unless enabled

With continue_on_error, later steps may run even when an earlier step failed. Use it only when those steps can operate on the remaining inputs; continuing does not make a partially completed workflow successful.

Per-Task Models in Workflows

Provider and model selection stays with the task. When task-specific models are enabled, an empty model override uses the selected provider's configured model. Check each task's provider before running a chain that handles private material.

Example

To try the default workflow, configure an empty trial-concepts folder, process one disposable source note, then inspect the generated concept notes and the reported complete folder. Run each action separately first if you need to understand its output destination. Only expand the folder scope after reviewing the results.

Tips

• Keep workflows short enough that failure and output ownership remain clear.
• Avoid cleanup or deletion actions in unattended chains; they retain their interactive confirmation requirements.
• If you cancel or encounter a recovery conflict, inspect the progress log and files before retrying.
• Test the exact provider/model and folder selection used by the workflow. A passing connection test does not establish that a long batch will fit provider quotas.

Next Steps

• Concept notes: extraction prerequisites and templates.
• Batch processing: selection, concurrency and partial completion.
• Research: network requirements and source verification.