> For the complete documentation index, see [llms.txt](https://help.gleantap.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.gleantap.com/templates/creating-templates.md).

# Creating Templates

**Step 1:** Navigate to **Campaigns > Templates** 

**Step 2:** Click on the green '+' button on the top right of your screen to create a new template. 

**Step 3:** When the template editor loads, drag-and-drop the content blocks from the right side to the left to build your email template.

<figure><img src="https://312952119-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaFKpjLzPT7iDAWD0tQXo%2Fuploads%2FHlvsKL1L5Sjeeka7QEtj%2FScreenshot%202023-09-28%20at%203.51.14%20AM.png?alt=media&amp;token=d37f04ef-f8df-4981-80dd-975a1150e4c6" alt=""><figcaption></figcaption></figure>

* **Content tab:** In this tab, you'll find options to add headings, text, images and more. Simply drag-and-drop to build!
* **Rows tab:** In this tab, you'll find options to add rows with varying number of columns. If you're starting your template from scratch, you'll want to start off with this first.
* **Settings tab:** In this tab, you can adjust general details for your email template, such as background color or image, content width & alignment, and fonts.

**Step 4:** Click the blue 'Save' button at the top of the editor to save the email template to your template library.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.gleantap.com/templates/creating-templates.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.