---
sourceDocument: Yokohama ServiceNow AI Platform Administration
sourceDocumentLink: https://www.servicenow.com/docs/r/yokohama/platform-administration

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama ServiceNow AI Platform Administration

ft:clusterId :

    - platadm

bundleId :

    - platadm

workflow :

    - Platform


---

# Accessing email object variables

# Accessing email object variables {#ariaid-title1}

* Release version: Yokohama
* 
* Updated January 30, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read

Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of Accessing email object variables

In ServiceNow Yokohama release, inbound email action scripts utilize theemailobject and the global variablesysemailto access and manipulate various components of an inbound email.
This capability enables customized processing of incoming emails by extracting key details such as sender, recipients, subject, body content, and headers.
Show full answer Show less  

## Key Features

* **email object variables:** Provide direct access to specific parts of an inbound email:
  * **email.to** , **email.direct** , and **email.copied**: Comma-separated recipient lists in To: and Cc: fields.
  * **email.bodytext** and **email.bodyhtml**: Email body in plain text or HTML format.
  * **email.from**: Sender's email address, resolved either to a user's email or the header's address.
  * **email.fromsysid**: Sys ID of the user who sent the email.
  * **email.origemail** and **email.fromAddress** : Original sender address, configurable via system property `glide.email.inboundaction.extractfromheader`.
  * **email.subject**: Email subject as plain text.
  * **email.recipients** and **email.recipientsarray**: Recipients in string and array formats for flexible scripting.
  * **email.contenttype**: MIME type of the email content.
  * **email.headers**: Raw email header details as plain text.
  * **email.importance**: Sender-indicated message importance (High, Low, or empty).
* **RFC 2822 compliance:** Email address groups must be comma-separated for correct parsing by the instance.
* **Inbound email recipient processing:** Use `email.recipientsarray` to iterate over recipients and customize email handling logic.
* **sysemail variable:** Provides access to the underlying `sysemail` record that triggered the inbound email action, allowing reference to email record fields such as uid, sysid, and contenttype.

## Practical Application for ServiceNow Customers

By leveraging these email object variables and the **sysemail** record in inbound email action scripts, ServiceNow customers can create tailored automation and workflows based on email content and recipients. This is crucial for scenarios such as:

* Routing or assigning incidents based on sender or recipients.
* Parsing email body content for automated ticket creation or updates.
* Filtering or prioritizing emails by importance or sender identity.
* Processing emails sent to multiple recipients using array iteration.

Understanding and using these variables ensures precise control over inbound email processing, improving workflow efficiency and user experience within the ServiceNow platform.  
An inbound email action script contains the email object to access various pieces of an
inbound email through variables. You can use the global variable <var class="keyword varname">sys_email</var>
with inbound email actions.
{#r_AccessingEmailObjsWithVars__table_sbj_31q_n4__entry__2}

| Variable | Contents |
|-|-|
| <var class="keyword varname">email.to</var> | Contains a comma-separated list of email addresses in the To: and Cc: boxes. |
| <var class="keyword varname">email.direct</var> | Contains a comma-separated list of email addresses in the To: box. |
| <var class="keyword varname">email.copied</var> | Contains a comma-separated list of email addresses in the Cc: box. |
| <var class="keyword varname">email.body_text</var> | Contains the body of the email as a plain text string. |
| <var class="keyword varname">email.body_html</var> | Contains the body of the email as an HTML string. |
| <var class="keyword varname">email.from</var> | Contains an email address that depends on the following conditions: * If the address listed in the email Headers field matches an existing user's Email address, this variable contains the user's email address. * If the address listed in the email Headers field does not match an existing user's Email address, this variable contains the address listed in the email Headers field. {#r_AccessingEmailObjsWithVars__ul_erp_ywk_br} |
| <var class="keyword varname">email.from_sys_id</var> | Contains the Sys ID of the user who sent the email to the instance. |
| <var class="keyword varname">email.fromAddress</var> | If system property glide.email.inbound_action.extract_from_header property is set to true, origemail is computed from the headers. The default value is false if the property does not exist. |
| <var class="keyword varname">email.origemail</var> | Contains the address of the email sender as listed in the email Headers field. |
| <var class="keyword varname">email.subject</var> | Contains the subject of the email as a plain text string. |
| <var class="keyword varname">email.recipients</var> | Contains a comma-separated list of recipient addresses as a plain text string, in the To: box. |
| <var class="keyword varname">email.recipients_array</var> | Contains the recipient addresses as an array. |
| <var class="keyword varname">email.content_type</var> | Contains the MIME content type of the email (for example,<var class="keyword varname">text/plain; charset="us-ascii"</var> or <var class="keyword varname">text/html; charset="us-ascii"</var>). |
| <var class="keyword varname">email.headers</var> | Contains details about the sender, route, and receiver as a plain text string in the format of the sending email client. |
| <var class="keyword varname">email.importance</var> | Contains an indication from the sender about how important a message is. The value can be High, Low, or empty. |
[Table 1. Accessing email objects with variables]

{#r_AccessingEmailObjsWithVars__table_sbj_31q_n4}  
Note:  
The instance follows [RFC 2822](http://www.rfc-editor.org/info/rfc2822) (Internet Message Format), which requires multiple email addresses in a group to be separated by commas, not semicolons. The instance can set the values of the <var class="keyword varname">email.to</var>, <var class="keyword varname">email.direct</var>, and <var class="keyword varname">email.copied</var> variables only if emails addressed to groups follow the expected RFC format.

## Inbound email.recipient variables {#r_AccessingEmailObjsWithVars__section_m3y_2c3_2db}

The recipients variables (<var class="keyword varname">email.recipients</var>, <var class="keyword varname">email.recipients-array</var>) allow processing of inbound email based on the email recipients. For example, you can create a script to process email based on the array values:

    var rarray  = email.recipients_array ; for ( var i  = 0 ; i  < rarray.length ; i ++ ) { var recipient  = rarray [i ] ; // do something with it } 

## The sys_email variable {#r_AccessingEmailObjsWithVars__section_xxr_3f3_2db}

This variable lets you access the received sys_email record that triggered the inbound
email action. It can be used to reference fields on the email record, such as
uid, sys_id,
content_type, and so on.