# Email V1 (Deprecated) {% hint style="info" %} The **Email V1** is deprecated and no longer updated. Please refer to the document with the most recent version of the feature: [Email V2](/documentation/connectors-and-triggers/connectors/web-protocols/email-v2.md). {% endhint %} **Email V1** invokes the SMTP server in a pipeline. To use **Email V1**, you must create a SMTP-type account. Read the [tutorial](/documentation/connectors-and-triggers/connectors/web-protocols/email-v1/email-v1-usage-example.md) on how to use the ***Email V1*** component. ## Parameters Take a look at the configuration options for the component. Parameters supported by [Double Braces expressions](/documentation/connectors-and-triggers/double-braces/overview.md) are marked with (DB).

Parameter	Description	Default value	Data type
Account	account to be used by the component	None	Any
From	set the sender email to be sent by the component	None	String
Subject	sets the subject to be sent by the component	None	String
Content Type	sets the Content Type and encoding	None	String
Template	template body to be used to prepare email templates	None	String

### **Parameters examples** **From:** ``` example@examplo.com.br ``` **Subject:** ``` Example: ${subject} ``` **Content Type:** ``` text/html; charset=UTF-8 ``` **Template:** ``` ${firstname} ${lastname} ``` ## Messages flow ### Input The component waits for a message in the following format: ``` { to : ["abc1@gmail.com","abc2@gmail.com"] cc : ["abc1@gmail.com","abc2@gmail.com"], bcc : ["abc1@gmail.com","abc2@gmail.com"], params: { // Template body replacement parameters "paramA":"valueA", "paramB":"valueB", ... "paramN":"valueN" } } ``` ### Output When there's an error, this is the message shown in the component output: ``` { timestamp: 1503608693745, code: 999, message: "error message" } ``` \ Note that, for some errors, body and header are unavailable. --- # Agent Instructions: 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: ``` GET https://docs.digibee.com/documentation/connectors-and-triggers/connectors/web-protocols/email-v1.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.