# Workflow template directory

Workflow templates provide a parameterized starting process. Each creates an independent workflow with its own definition and run history. Choose a recipe for its intended input and outcome, then inspect the generated jobs before starting execution.

| Template | Intended result |
| --- | --- |
| [Copy files between stores](/docs/workflow-templates/blob-copy) | Copy a scoped source file list into a destination store. |
| [Extract insights from files](/docs/workflow-templates/digest-insights) | Parse documents and retain model-generated insights. |
| [Document search index](/docs/workflow-templates/document-search) | Produce word postings, file summaries, and an index manifest. |
| [Export records to JSONL](/docs/workflow-templates/fs-export) | Append a bounded record selection to a sandbox file. |
| [HTTP webhook fan-out](/docs/workflow-templates/http-fanout) | POST records to a webhook and retain the HTTP results. |
| [LLM summarize records](/docs/workflow-templates/llm-summarize) | Retain one-sentence model summaries of source records. |
| [MCP tool notify](/docs/workflow-templates/mcp-notify) | Filter records and invoke an offered service tool for each match. |
| [SQL derived-record ETL](/docs/workflow-templates/sql-etl) | Page through a SQL result and retain its rows. |

## Use the recipe guides

Each guide explains required parameters, defaults, prepared job settings, a small first run, expected output, and repetition risks. A field with a default still needs review: the stored connection type or model may not be the one your workspace should use.

The prepared recipes use Manual triggers. Start with a small source scope and verify the destination before adding a schedule or event trigger. An enabled definition is not evidence that any run has completed successfully.

A limit on a nonbatched loader bounds its selected records. A source count larger than that limit requires a deliberate paging or batching strategy. Model and external-service operations can incur usage, and dry runs can validate a destination without executing it.

## Keep templates and instances separate

Changing a template affects future instantiation rather than automatically migrating existing workflows. Duplicating an existing workflow creates another independent instance. Use versioned reusable recipes when you need shared upgrade behavior.

For authoring reusable tenant templates, see [Manage workflow templates](/docs/workflow-templates/manage-templates). For the gallery procedure, see [Create from a template](/docs/workflows/templates).