# Create template

## What a template helps you do

A template turns one finished workflow into something others can reuse.

Use a template when the same process should work again for:

* Your team
* Another workspace member
* The Diaflow Community

### Before you create a template

You can create a template only after the workflow has been **published**.

If the workflow is still a draft, publish it first.

Then return to **Create template**.

Make sure the workflow is also ready for reuse.

Use this checklist:

* The workflow is **published**
* The workflow runs successfully
* The name is clear
* The inputs are easy to understand
* The output is useful without extra explanation
* Personal or private data has been removed
* API keys, secret keys, and credentials are not exposed

<figure><img src="/files/uco7yRApge9ho6HqnLyr" alt=""><figcaption></figcaption></figure>

### Create a template from Workflow Builder

1. Open the workflow you want to reuse.
2. Click the three-dot menu in the top right.
3. Select **Create template**.

If the workflow has already been published, the template form opens.

<figure><img src="/files/fkuSv3gY9tdPdnKQXWev" alt=""><figcaption></figcaption></figure>

### Add the template details

The form includes these main fields:

* **Name:** what the workflow does
* **Categories:** where people expect to find it
* **Description:** what problem it solves and when to use it

The description area also shows a live **Preview**.

This helps you review how the template content will look before you submit it.

### Review community requirements in the form

The template form also reminds you to follow these rules:

* Build practical and original workflows
* Write clear, well-structured descriptions
* Do not copy or repost existing templates

Use these rules as a final check before you submit.

### Remove secrets before you submit

This step is critical.

Before creating a template, remove any sensitive values from the workflow.

Do not leave:

* API keys
* Secret keys
* Access tokens
* Passwords
* Private webhook URLs
* Personal customer data

If a workflow depends on credentials, replace them with safe placeholders or setup instructions.

{% hint style="warning" %}
Never include real API keys or secret values in a community template.
{% endhint %}

### Write for reuse

A good template is easy for someone else to adopt.

Before you submit it, check that:

* The business outcome is obvious
* The steps follow a clear order
* A new user can tell what to change first

If a reviewer needs to guess what the workflow does, the template is not ready.

### When to create a template

Create a template when a workflow is:

* Used often
* Shared across teams
* Strong enough to become a standard process

Examples:

* Weekly reporting
* Customer intake
* Internal approvals

### Share it with the community

If you want to publish the template more broadly, continue with the full submission flow.

Use these guides:

* [How to Create and Publish a Template](/workspace/community/template/how-to-create-and-publish-a-template.md)
* [Community Template Submission Guidelines](/workspace/community/template/community-template-submission-guidelines.md)

## Best practices

Templates are most useful when they are practical.

Keep them:

* Specific enough to solve a real problem
* General enough to adapt to another team
* Free of temporary test data
* Free of credentials and private information

### Next steps

* Learn the full community flow in [How to Create and Publish a Template](/workspace/community/template/how-to-create-and-publish-a-template.md).
* Review quality expectations in [Community Template Submission Guidelines](/workspace/community/template/community-template-submission-guidelines.md).
* Publish your workflow first in [Publish a workflow](/workflow-builder/publish-a-workflow.md).
* Keep reusable workflows organized in [Tags](/workflow-builder/tags.md).


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.diaflow.io/workflow-builder/create-template.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.