<h2>Create a flow with an inbound email trigger</h2><br/><div style="overflow-x:auto"> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"><head><meta content="text/html; charset=UTF-8" /><meta name="copyright" content="(C) Copyright 2025" /><meta name="DC.rights.owner" content="(C) Copyright 2025" /><meta name="generator" content="DITA-OT" /><meta name="DC.type" content="task" /><meta name="DC.title" content="Create a flow with an inbound email trigger" /><meta name="abstract" content="Start a flow when your instance receives an email." /><meta name="description" content="Start a flow when your instance receives an email." /><meta name="DC.relation" scheme="URI" content="../../../administer/flow-designer/task/create-flow.html" /><meta name="DC.relation" scheme="URI" content="../../../administer/build-workflows/concept/build-workflows.html" /><meta name="DC.relation" scheme="URI" content="../../../administer/flow-designer/concept/flow-designer.html" /><meta name="DC.relation" scheme="URI" content="../../../administer/flow-designer/concept/flows.html" /><meta name="DC.creator" content="ServiceNow" /><meta name="DC.date.created" content="2023-08-03" /><meta name="DC.date.modified" content="2023-08-03" /><meta name="page-type" content="automation-engine" /><meta name="page-type" content="platform" /><meta name="DC.format" content="XHTML" /><meta name="DC.identifier" content="create-inbound-email-flow" /><link rel="stylesheet" type="text/css" href="../../../CSS/commonltr.css" /><title>Create a flow with an inbound email trigger</title></head><body id="create-inbound-email-flow"> <div class="breadcrumb"><a class="link" href="../../../administer/build-workflows/concept/build-workflows.html" title="Transform manual tasks and mundane work into digital workflows. Modernize legacy processes with hyperautomation. Enable citizen automation from one platform.">Build workflows</a> > <a class="link" href="../../../administer/flow-designer/concept/flow-designer.html" title="Flow Designer is a Now Platform feature that enables process owners to automate work. Build multi-step flows from reusable components without having to code.">Flow Designer</a> > <a class="link" href="../../../administer/flow-designer/concept/flows.html" title="Flows automate a repeatable multi-step process. When the flow trigger conditions are met, the flow runs a sequence of reusable actions and flow logic to complete the process.">Building flows</a> > </div> <h1 class="title topictitle1" id="ariaid-title1">Create a flow with an inbound email trigger</h1> <div class="body taskbody"><p class="shortdesc"><span class="ph">Start a flow when your instance receives an email.</span></p> <div class="section prereq p">Role required: flow_designer or admin</div> <ol class="ol steps"><li class="li step stepexpand"> <span class="ph cmd">Navigate to <span class="ph menucascade"><span class="ph uicontrol">All</span> > <span class="ph uicontrol">Process Automation</span> > <span class="ph uicontrol">Flow Designer</span></span>.</span> </li><li class="li step stepexpand"> <span class="ph cmd">Select <span class="ph menucascade"><span class="ph uicontrol">+ New</span> > <span class="ph uicontrol">Flow</span></span>.</span> </li><li class="li step stepexpand"> <span class="ph cmd">In the flow properties, set <span class="ph uicontrol">Run as</span> to <span class="ph uicontrol">User who initiates session</span>.</span> <div class="itemgroup info"> <div class="note important"><span class="importanttitle">Important:</span> <span class="ph">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.</span></div> </div> </li><li class="li step stepexpand"> <span class="ph cmd">In the Trigger section, select the plus icon (<img class="image icon" id="create-inbound-email-flow__image_jlx_3bg_d3b" src="../../../build/app-engine-studio/image/plus-icon.png" alt="Plus icon" />) to add a trigger.</span> </li><li class="li step stepexpand"> <span class="ph cmd">Select <span class="ph uicontrol">Inbound Email</span>.</span> </li><li class="li step stepexpand"> <span class="ph cmd">On the form, fill in the fields.</span> <div class="itemgroup info"> <div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="create-inbound-email-flow__table_mmj_qtr_fdb" class="table" frame="border" border="1" rules="all"><colgroup><col style="width:18.484288354898336%" /><col style="width:81.51571164510166%" /></colgroup><thead class="thead" style="text-align:left;"><tr class="row"><th class="entry nocellnorowborder" style="vertical-align:top;" id="d199854e139">Field</th><th class="entry cell-norowborder" style="vertical-align:top;" id="d199854e142">Description</th></tr></thead><tbody class="tbody"><tr class="row"><td class="entry nocellnorowborder" style="vertical-align:top;" headers="d199854e139 ">Email conditions</td><td class="entry cell-norowborder" style="vertical-align:top;" headers="d199854e142 ">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 <span class="ph uicontrol">[Receive type] [is] [Reply]</span>.</td></tr><tr class="row"><td class="entry row-nocellborder" style="vertical-align:top;" headers="d199854e139 ">Reply Record Type</td><td class="entry cellrowborder" style="vertical-align:top;" headers="d199854e142 ">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 <span class="ph uicontrol">Incident [incident]</span>.</td></tr></tbody></table> </div> </div> </li><li class="li step stepexpand"> <span class="ph cmd">Select <span class="ph uicontrol">Done</span>.</span> </li><li class="li step stepexpand"> <span class="ph cmd">Add actions, subflows, and flow logic to the flow.</span> </li><li class="li step stepexpand"> <span class="ph cmd">Test the flow.</span> <div class="itemgroup info"><span class="ph">To test access controls for an inbound email flow, impersonate a typical inbound email user and manually trigger the flow.</span>. For more information, see <a class="xref" href="flow-test.html" title="Before activating a flow so other users can access it, test to make certain it works the way you expect.">Test a flow</a>.</div> </li><li class="li step stepexpand"> <span class="ph cmd">If the test is successful, activate the flow.</span> <div class="itemgroup info">For more information, see <a class="xref" href="flow-activate.html" title="Activate a flow to make it available to run.">Activate a flow</a>.</div> </li></ol> <div class="section result" id="create-inbound-email-flow__result_i5n_x5q_sgb">When an inbound email meets the conditions that you set, the associated flow triggers and runs the actions.</div> </div> <div class="related-links"> <div class="familylinks"> <div class="parentlink"><strong>Parent Topic:</strong> <a class="link" href="../../../administer/flow-designer/task/create-flow.html" title="Automate a process to run one or more actions when a trigger condition occurs.">Create a flow</a></div> </div> </div></body></html></div>