> 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/sailthru-connector/taxi-and-the-sailthru-connector.md).

# Taxi and the Sailthru Connector

If you build your emails in Taxi for Email and send them via Sailthru, our Sailthru connector will save you time and reduce risk throughout the process. It does this by allowing you to automatically send your mailings to any folder within your Sailthru instance or update existing emails that have already been exported.

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 Sailthru. The connector allows for a more seamless process from creating the email to exporting to Sailthru.

The Sailthru connector 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.

\
There are two Sailthru connectors, one that [exports HTML as campaigns](https://docs.messagebird.com/taxi/Connectors/Sailthru%20Connector/setting-up-the-sailthru-connector) and one that [exports HTML as templates](https://docs.messagebird.com/taxi/Connectors/Sailthru%20Connector/setting-up-the-sailthru-template-connector). Campaigns are individual emails that can be used for marketing campaigns. Templates are more of an email design that can then be used for campaigns and also triggered emails. Taxi allows you to export to both of these in Sailthru.


---

# 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.bird.com/taxi/connectors/sailthru-connector/taxi-and-the-sailthru-connector.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.