> For the complete documentation index, see [llms.txt](https://university.gonexa.fr/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://university.gonexa.fr/doc/en/advanced-features/doc-and-flows/email-generated-document.md).

# Email the generated document

Use a flow to send a document by email

## Action name: "Send e-mail with attachment"

Sometimes you need to send an email with an attachment.

**In a Salesforce flow:**

### Add the send email action

Fill in the expected parameters:

* **Contact or User ID**: Enter the ID of the contact or user you want to send an email to. You can retrieve this value with a Get Records element in the flow.
* **Email Template ID**: Enter the ID of the email template to use for sending. You can retrieve this value with a Get Records element in the flow, for example on the EmailTemplate object.
* **Content Document ID**: Enable this parameter to add a document as an attachment. You can retrieve this value with a Get Records element in the flow.
* **Related To ID**: Enable this parameter if you want to link the activity to a specific record in addition to the contact. Enter the ID of the desired record; you can retrieve it with a Get Records element in the flow.

You can add other parameters to the action, such as adding a recipient in copy, adding a custom sender address or displaying a sender name

{% hint style="warning" %}
**Tip**

An example flow is available in the pre-built Flow Org
{% endhint %}


---

# 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://university.gonexa.fr/doc/en/advanced-features/doc-and-flows/email-generated-document.md?ask=<question>&goal=<user_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.