> For the complete documentation index, see [llms.txt](https://software-help-docs.gitbook.io/knowledge-base/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://software-help-docs.gitbook.io/knowledge-base/software-guide/workflow-actions/workflow-action-send-email.md).

# Workflow Action: Send Email

In this article, you will learn more about the Send Email action.

This action will allow you to send followup emails with your leads.

**What you will need:**

* A workflow

**Part 1: Adding the Send Email action**

* Click on the “Add your first action” button and select the first action “Send Email”.
* The Send Email action settings will show up. Edit this as needed.

{% embed url="<https://lh4.googleusercontent.com/8bjUhfIQXwFAN_bsaWI24DNGo-NprsxH5iiyn8VZTOncYhv-DZbI9rBKq6S58KmrNPNI2j3OeVLkGI6Uj04XsS20KV1kTgTY_AnoZ0zq8LN5DDIR9qKjjY5_Is-_YaSE4-CP9De6OLSjlr8oZvS0yGc>" %}

***Note:*** if you need to add a trigger to this workflow, do that first. If you will be manually adding your leads to this workflow then a trigger will be unnecessary.

* Once you have all the fields filled out, click on Save Action.

***Note:*** If you want to send additional follow-up emails, it is suggested that you add a Wait step in between the Send Email action steps to give time between emails. You can add minutes, hours, or days.

{% embed url="<https://lh6.googleusercontent.com/bduxnIdABVVG3CCT9esBiZqwJk3JHg2fnj2eNUJmW75BlMjC8kZ5aVMHA6v43XS4Tqo2P3jgAoYooqZs0E8Z5vMqFkILOsNgNmrtUnyp70eof1QFposEl6mb90NsYIfFjDpWj9yq-yB0JEjvkLgnXto>" %}

* Once your workflow is ready, place it on Publish mode, and save.


---

# 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://software-help-docs.gitbook.io/knowledge-base/software-guide/workflow-actions/workflow-action-send-email.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.