> 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/omeda-connector/taxi-and-the-omeda-connector.md).
# Taxi and the Omeda connector
If you build your emails in Taxi for Email and send them via Omeda, our Omeda connector will save you time and reduce risk throughout the process. It does this by enabling you to automatically send your emails to any deployment within your Omeda account, either creating a new one or updating an existing one.
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 Omeda. The connector allows for a more seamless process from creating the email to exporting to Omeda.
[Personalisation](https://docs.messagebird.com/taxi/Dynamic%20content,%20segmentation%20and%20personalisation/Personalisation/what-is-personalisation) can be used with this connector.
You can set up as many Omeda connectors in your Taxi for Email account as you need. This can be useful if you have separate staging and production Omeda environments, or different accounts for brands or regions.
This connector also enables you to schedule when emails will be sent from Omeda as you export from Taxi. This makes sure that there will be even fewer steps needed after the email has left Taxi. You’ll have to jump between tools far less often which makes for a far smoother process.
\
On the export page select the ‘Schedule email send date’ and choose the send date, send time and the timezone you’re sending in.
Read Next:
[Setting up the Omeda connector](https://docs.messagebird.com/taxi/Connectors/Omeda%20Connector/setting-up-the-omeda-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, and the optional `goal` query parameter:
```
GET https://docs.bird.com/taxi/connectors/omeda-connector/taxi-and-the-omeda-connector.md?ask=&goal=
```
`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.