> ## Documentation Index
> Fetch the complete documentation index at: https://docs.workflowmachine.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Start from a template

> Use templates to launch a workflow faster and learn the product from working examples.

## Why start from a template

Templates are one of the fastest ways to get value from Workflow Machine. Browse [Templates](https://app.workflowmachine.com/templates) to explore available starting points.

Instead of building every workflow from scratch, you can start from a working pattern and adapt it to your own tools, data, and goals.

Templates are especially useful when:

* you already know the business outcome you want
* you want to learn by inspecting a real workflow
* you need a faster path to a first published workflow

## What a template gives you

A template usually provides a starting structure such as:

* one or more triggers
* a sequence of steps
* a suggested workflow use case

You still need to review and customize the details, especially connections, field mappings, and any app-specific configuration.

## How to choose a good template

Pick a template based on the outcome you want, not just the apps it mentions.

Good examples:

* lead capture and routing
* inbox triage
* scheduled digests
* content summarization
* spreadsheet or database logging

If multiple templates look similar, choose the one with the simplest shape first. It is easier to extend a simple workflow than to debug a complex one you do not fully understand yet.

## Before you publish a template

Treat every template like a draft.

Before going live:

* check the trigger configuration
* connect the right app accounts
* verify all required fields
* review the data flow between steps
* run a test

Templates can save time, but they still need your context.

## What to customize first

The most important template edits are usually:

* the workflow name
* the selected connections
* destination channels, documents, or databases
* AI prompt wording
* conditions and output formatting

You do not need to change everything at once. Make the minimum edits needed to fit your process, then test.

## A good way to learn the product

Templates are also a teaching tool.

If you are still getting familiar with triggers, steps, and field mappings, open a template and inspect:

* how the workflow was created in chat, so you can learn how to prompt more effectively
* what starts the workflow
* how the steps are sequenced
* which parts use connections
* how the final result is produced

That makes it easier to understand how to build your own workflows from scratch later.

## When to choose a blank workflow instead

Start from scratch instead of using a template when:

* your process is very specific
* you want to learn the editor directly
* the available templates are more complex than your use case

Both approaches are valid. Templates are about speed, not obligation.