> For the complete documentation index, see [llms.txt](https://docs.digibee.com/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digibee.com/documentation/connectors-and-triggers/connectors/web-protocols/email-v1/email-v1-usage-example.md).

# Email V1: Usage example (Deprecated)

Component usage example.

Let's say you can't seem to add values to the email template when using the ***Email V1*** component.

First of all, it's necessary to understand that the email template accepts the use of the input JSON attributes in the **${atrribute}** format. Therefore, the "attribute" must be inside "params", resulting in the following input JSON:

```
{
    "attribute": "valueOfAttribute"
}
```

Afterwards, this is the transformation that must occur:

```
{
    "params": {
        "attribute": "valueOfAttribute"
    }
}
```

This would be the email template preview:

***Hello ${attribute}!***

It's also possible to add HTML tag to the template:

```
<div>Hello ${atrribute}!</div>
```

That way, the variable replaced in the sent email would be seen like this:\
***Hello valueOfAttribute!***<br>

Click [here](/documentation/connectors-and-triggers/connectors/web-protocols/email-v1.md) to read the full article about the ***Email V1*** component.


---

# 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.digibee.com/documentation/connectors-and-triggers/connectors/web-protocols/email-v1/email-v1-usage-example.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.