> 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**&#x20;

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

**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="/files/S90wQbBIo2JTHdVknbio" 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 dynamically by asking a question.

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

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
