> For the complete documentation index, see [llms.txt](https://craft-agent.gitbook.io/home/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://craft-agent.gitbook.io/home/tips-and-tricks/workflow-best-practices.md).

# Workflow Best Practices

Tips to design efficient, maintainable, and reliable workflows.

## Design Principles

### 1. Start Small, Iterate

Don't build a 20-node workflow immediately. Start with 2-3 nodes, test, then expand.

### 2. One Node, One Job

Each node should have a single, clear responsibility. This makes debugging easier.

### 3. Name Everything

Give meaningful names to your workflows and nodes. Future-you will thank you.

### 4. Test as You Build

Run your workflow after adding each node. Don't wait until the end to test.

### 5. Use Templates as Starting Points

Browse templates and community workflows to learn proven patterns.

## Performance Tips

* **Keep prompts concise** — Shorter prompts = faster execution
* **Avoid redundant nodes** — If two nodes do the same thing, merge them
* **Use scheduling wisely** — Each scheduled run costs 1 credit

## Debugging Tips

* **Check each node's output** — Click on a completed node to see its result
* **Verify connections** — Make sure data flows in the right direction
* **Simplify prompts** — If a node gives unexpected output, simplify the prompt first
* **Test with simple input** — Use short, known inputs when debugging

***

> **Tip:** The best workflows are simple, well-named, and thoroughly tested.
