> For the complete documentation index, see [llms.txt](https://docs.bird.com/taxi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bird.com/taxi/connectors/episerver/taxi-and-the-episerver-connector.md).
# Taxi and the Episerver connector
If you build your emails in Taxi for Email and send them via Episerver, our Episerver connector will save you time and reduce risk throughout the process. It does this by allowing you to automatically send your mailings to any email within your Episerver instance or update existing emails that have already been set up.
Without the connector, you will need to download the HTML from Taxi and then either upload the HTML file or copy and paste it into Episerver. The connector allows for a more seamless process from creating the email to exporting to Episerver.
The Episerver connector also makes it much easier to create and export targeted emails. [Personalisation](https://docs.messagebird.com/taxi/Dynamic%20content,%20segmentation%20and%20personalisation/Personalisation/what-is-personalisation) and [segmentation](https://docs.messagebird.com/taxi/Dynamic%20content,%20segmentation%20and%20personalisation/Segmentation/what-is-segmentation) can be used with this connector.
When you export, using the different connectors the emails will land in different places in Episerver. The Smart Campaign connector will export to the Smart Campaigns in your Episerver account, and the transactional connector will export to Transactional mails in your Episerver account.
[Setting up the Episerver Transactional connector](https://docs.messagebird.com/taxi/Connectors/Episerver/setting-up-the-episerver-transactional-connector) | [Setting up the Episerver Smart Campaign connector](https://docs.messagebird.com/taxi/Connectors/Episerver/setting-up-the-episerver-smart-campaign-connector)
---
# 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:
```
GET https://docs.bird.com/taxi/connectors/episerver/taxi-and-the-episerver-connector.md?ask=
```
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.