---
sourceDocument: Australia Build workflows
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/build-workflows

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Build workflows

ft:clusterId :

    - crworkflow

bundleId :

    - crworkflow

workflow :

    - Creator


---

# Get Email Header action

# Get Email Header action {#ariaid-title1}

* Release version: Australia
* 
* Updated March 12, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Access an email header value as a data pill in a flow.

## Roles and availability {#get-header-action__section_oyw_xj5_tgb}

Available as a Workflow Studio core action. Process analysts use the flow_designer role to add an action to a flow and define configuration details.

## Fields {#get-header-action__section_hyb_tj5_tgb}

{#get-header-action__table_fdl_yhf_kcb__entry__2}

| Field | Description |
|-|-|
| Email Record | Record from the Email \[sys_email\] table. |
| Target Header | Header from the email record. Upon completion of the action, the header value is added as a data pill in the flow. Note: If multiple headers have the same name, the action gets the value of the first header that appears. This input requires a string value matching an email header name. ServiceNow provides several dedicated email headers. * X-ServiceNow-Source * X-ServiceNow-SysEmail-Version {#get-header-action__ul_w1l_fts_nwb} |
[ ]

{#get-header-action__table_fdl_yhf_kcb}

## Example {#get-header-action__section_nyj_xj5_tgb}

In the following example, a process owner adds the Get Email Header action under an inbound email trigger. In the Email Record field, the user selects to get
an email header from the email that triggered the flow. In the Target Header field, the user selects to get the X-ServiceNow-Source header from the email.

Testing the flow with a sample email record produces the header value as a data pill.