---
sourceDocument: Xanadu Build workflows
sourceDocumentLink: https://www.servicenow.com/docs/r/xanadu/build-workflows

 Release :

    - xanadu

ft:locale :

    - en-US

ft:publication_title :

    - Xanadu Build workflows

ft:clusterId :

    - crworkflow

bundleId :

    - crworkflow

workflow :

    - Creator


---

# Create a flow with an inbound email trigger

# Create a flow with an inbound email trigger {#ariaid-title1}

* Release version: Xanadu
* 
* Updated August 1, 2024
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Start a flow when your instance receives an email.

## Before you begin

Role required: flow_designer or admin

## Procedure

1. Navigate to AllProcess AutomationFlow Designer.
2. Select + NewFlow.
3. In the flow properties, set Run as to User who initiates session.  
   Important:  
   Inbound email flows use the email sender as the user who initiates the session. If the system doesn't recognize the sender, the inbound email flow runs as the Guest user. Setting the inbound email flow to run as the user who initiates the session ensures that the flow actions are limited by user access controls. If the initiating user needs elevated privileges for some reason, have the inbound email flow call a subflow that runs with the required roles.
4. In the Trigger section, select the plus icon (![Plus icon]()) to add a trigger.
5. Select Inbound Email.
6. On the form, fill in the fields.  
   {#create-inbound-email-flow__table_mmj_qtr_fdb__entry__2}

   | Field | Description |
   |-|-|
   | Email conditions | Conditions to qualify which emails start your flow. The condition builder uses fields from the Email \[sys_email\] table. For example, to trigger a flow for an inbound email in which a user replies to a system notification, set the condition to \[Receive type\] \[is\] \[Reply\]. |
   | Reply Record Type | Table that is associated with the target email. For example, to trigger a flow from a reply email that a user sends from an incident record notification, select Incident \[incident\]. |
   [ ]

   {#create-inbound-email-flow__table_mmj_qtr_fdb}
7. Select Done.
8. Add actions, subflows, and flow logic to the flow.
9. **Optional:** Add stages to the flow to report progress to the requester.  
   See [Flow and subflow stages](https://www.servicenow.com/docs/208N2XI4EZHdrr7TQxKNjg "Communicate the current stage of a request, flow, or subflow with an end user.").
10. Test the flow.  
    To test access controls for an inbound email flow, impersonate a typical inbound email user and manually trigger the flow.. For more information, see [Test a flow](https://www.servicenow.com/docs/_78MAfbFTJcFiMImXMpSqQ "Before activating a flow so other users can access it, test to make certain it works the way you expect.").
11. If the test is successful, activate the flow.  
    For more information, see [Activate a flow](https://www.servicenow.com/docs/YDs8U80Le1qYH6kIiclRDA "Activate a flow to make it available to run.").

## Result

When an inbound email meets the conditions that you set, the associated flow triggers and runs the actions.

*[\>]: and then