> For the complete documentation index, see [llms.txt](https://docs.getmesa.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.getmesa.com/connect/gmail/send-email.md).
# Send Email
## Attachments
You can attach attachments to your email by inputting the URL of the attachment.
We use the file's type extension to determine the mime type of the file. For instance, if a file ends with .pdf, we will assume the mime type is application/pdf because of the extension. Similarly, if the file ends with .png, we will assume its mime type is image/png. Therefore, it is highly recommended that the attachment URLs end with the file extension.
***
## Limitations
* The **Send Email** action cannot reply to email threads at this time.
* Please note that the email message, including attachments, cannot exceed the per-message size limit of 25MB or it may be permanently lost.
* We do not support sharing URLs from Google Drive or Dropbox at this time or the ability to upload a file directly in MESA. For example, the attachment URL should be publicly available and MESA should be able to directly access the file without downloading it. We recommend uploading the files to a third-party service like [Shopify Files](https://help.shopify.com/en/manual/shopify-admin/productivity-tools/file-uploads) and then copying the URL from there.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.getmesa.com/connect/gmail/send-email.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
