Get Email Header action
Access an email header value as a data pill in a flow.
Roles and availability
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
|
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.
|
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.
[Omitted image "get-email-header-example-configuration.png"] Alt text: Get Email Header action example
Testing the flow with a sample email record produces the header value as a data pill.
[Omitted image "get-email-header-example-execution-details.png"] Alt text: Sample header value with a unique notification ID.
Parent Topic:Workflow Studio actions
--- title: Get Email Header action description: Access an email header value as a data pill in a flow. locale: en-US canonical_url: https://www.servicenow.com/docs/r/australia/build-workflows/workflow-studio/get-header-action.html release: australia product: Workflow Studio classification: workflow-studio topic_type: reference last_updated: "2026-09-10" reading_time_minutes: 1 breadcrumb: [Actions, Flows, subflows, and actions reference, Flows, subflows, and actions, Workflow Studio, Build workflows] --- # Get Email Header action Access an email header value as a data pill in a flow. ## Roles and availability 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 <table id="table_fdl_yhf_kcb"><thead><tr><th> Field </th><th> Description </th></tr></thead><tbody><tr><td> Email Record </td><td> Record from the Email \[sys\_email\] table. </td></tr><tr><td> Target Header </td><td> 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 </td></tr></tbody> </table>## Example 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. \[Omitted image "get-email-header-example-configuration.png"\] Alt text: Get Email Header action example Testing the flow with a sample email record produces the header value as a data pill. \[Omitted image "get-email-header-example-execution-details.png"\] Alt text: Sample header value with a unique notification ID. **Parent Topic:**[Workflow Studio actions](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/build-workflows/workflow-studio/flow-actions.md)
| title | Get Email Header action |
| description | Access an email header value as a data pill in a flow. |
| locale | en-US |
| canonical_url | https://www.servicenow.com/docs/r/australia/build-workflows/workflow-studio/get-header-action.html |
| release | australia |
| product | Workflow Studio |
| classification | workflow-studio |
| topic_type | reference |
| last_updated | 2026-09-10 |
| reading_time_minutes | 1 |
| breadcrumb | ActionsFlowssubflowsand actions referenceFlowssubflowsand actionsWorkflow StudioBuild workflows |