> For the complete documentation index, see [llms.txt](https://docs.cipp.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cipp.app/user-documentation/email/transport/list-connector-templates.md).

# Connector Templates

This page lists the Exchange connector templates saved in CIPP. Templates are stored in CIPP rather than in a tenant, and they are what the **Deploy Connector** drawer offers you when it asks for a template. New templates are added with the **Create template based on connector** action on the [Connectors](/user-documentation/email/transport/list-connectors.md) page.

## Action Buttons

<details>

<summary>Deploy Connector</summary>

Opens a drawer that creates a connector in one or more tenants. Select the target tenants, then either pick a template from this list to fill in the **Parameters (JSON)** box or type the JSON in yourself, and click **Deploy Connector**. The result for each tenant is shown in the drawer, and your tenant selection is kept so you can deploy another.

</details>

## Table Details

| Column            | Description                                                                                                            |
| ----------------- | ---------------------------------------------------------------------------------------------------------------------- |
| Name              | The template name, which is also the name given to the connector it creates.                                           |
| Cippconnectortype | Whether the template creates a connector for mail arriving at the organisation (`Inbound`) or leaving it (`Outbound`). |
| GUID              | The template's unique identifier, useful for telling apart two templates that share a name.                            |

The Extended Info flyout on this page is a **Connector Template Details** card showing every setting the template holds, rather than only the three columns above. Which settings appear depends on the direction: outbound templates cover options such as smart hosts, TLS settings, and recipient domains, while inbound templates cover options such as sender domains, sender IP addresses, and the required sender certificate name.

## Table Actions

<table><thead><tr><th>Action</th><th>Description</th><th data-type="checkbox">Bulk Action Available</th></tr></thead><tbody><tr><td>Save to GitHub</td><td>Commits the selected template to a GitHub repository you choose, using a commit message you supply. Greyed out unless the GitHub integration is set up and you have write access to at least one repository.</td><td>true</td></tr><tr><td>Delete Template</td><td>Removes the selected template from CIPP. Connectors already deployed from the template keep working and are not changed.</td><td>true</td></tr><tr><td>More Info</td><td>Opens the Extended Info flyout with the full details for the selected row.</td><td>false</td></tr></tbody></table>

***

## Feature Requests / Ideas

We value your feedback and ideas. Please raise any [feature requests](https://github.com/CyberDrain/CIPP/issues/new?template=feature.yml) on GitHub.


---

# 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://docs.cipp.app/user-documentation/email/transport/list-connector-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.