--- 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 --- # Send Email step # Send Email step {#ariaid-title1} * Release version: Australia * * Updated March 12, 2026 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 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 Send Email step The Send Email step in Workflow Studio allows you to send emails to specified users or groups as part of an automated flow. It is designed for users with theactiondesignerrole who need to create custom actions involving one or more steps. Show full answer Show less ## Inputs This step requires several inputs to customize the email: * **Target Record:** The record the email is associated with; replies update this record. * **Table:** The table containing the target record. * **To:** Main recipients' email addresses or data pills, supporting individual users or group email addresses. For groups, the "Include members" option must be enabled to email group members. * **CC:** Additional recipients copied on the email. * **BCC:** Recipients blind copied and invisible to others. * **Subject:** Email subject text or dynamic data pills. * **Body:** Email message content supporting inline styles and data pills. Note that Email Template variables cannot be processed and must be replaced with data pill references manually. * **Action error evaluation:** Option to continue or stop the flow if the email step fails, enabling custom error handling. **Important:** The maximum number of recipients is capped by the `glide.email.smtp.maxrecipients` system property to optimize SMTP processing. ## Outputs The action outputs the created email record, which can be utilized in downstream flow steps. ## Testing and Permissions * Test email generation by reviewing the email record in the **Email \[sysemail\]** table; the Headers field shows success status. * Access controls apply; ensure the executing user has permission to send emails, especially when running flows under the user session context. * For access testing, impersonate the typical sender and manually trigger the flow. Send an email to specified users or groups as an action in a flow. ## Roles and availability {#send-email-action__section_pwq_rb5_kcb} Available as an Workflow Studio action step. Users with the action_designer role can create a custom action with one or more action steps. ## Inputs {#send-email-action__action-inputs} Provide a value for each input that your flow needs. To add dynamic values, you can also drag and drop pills from the Data panel or select them from the pill picker. Target Record : Data type: Document ID Record that the email is associated to. When a user sends a reply to your email, the target record is updated with the reply email content. Table : Data type: Table Name Table containing the target record. To : Data type: String The main recipients of the email. Enter a list of user email addresses separated by commas or white spaces. You can also drag data pills that contain email addresses into the field, such as a User or Group record. For example, if you want to send an email to the group assigned to the incident, drag the \[Assignment group\] data pill from the data panel. To send email to a group, you must provide a Group email address. To send email to group members, the group must have the Include members option enabled. Note: The number of email recipients must be equal to or less than the maximum number set by the glide.email.smtp.max_recipients system property. See [Minimize SMTP Recipient Quantity](https://www.servicenow.com/docs/access?context=sc-max-smtp-recipients&version=australia&pubname=australia-platform-security&ft:locale=en-US) for information about setting this value. CC : Data type: String Additional recipients copied on this email. Enter a list of user email addresses separated by commas or white spaces. You can also drag data pills that contain email addresses into the field. BCC : Data type: String Additional recipients of this email, who are visible only to the sender (blind copied). Enter a list of user email addresses separated by commas or white spaces. You can also drag data pills that contain email addresses into the field. Subject : Data type: String Subject of the email. You can enter text or drag data pills into the field. Body : The content of the message body. You can enter text or drag data pills into the field. The editor formatting options add inline styles. There is no style sheet associated with an email body. You can add your own inline style sheet to this HTML input. Note: You can partially reuse content from the Email Template \[sysevent_email_template\] table with some manual editing. The Send Email action can't process Email template variables, which are strings that start with the dollar sign character and include content in curly braces. You must replace email variables with references to data pills. For example, replace the string ${number} with a data pill reference to an incident record number. ## Action error evaluation {#send-email-action__id_lg2_4s3_15b} If this step fails : Data type: Choice Option to continue running the next step or go to error evaluation. To use the step status code or message for a custom action error condition, see [Action error evaluation](https://servicenow-prod.fluidtopics.net/TJkLnvv_cE34AFa4p0LuVQ "Enable actions to catch step failures and continue running. Identify when specific error conditions occur and return your own action status code, status message, and error state."). ## Outputs {#send-email-action__action-outputs} These outputs appear in the Data panel. You can use them as inputs elsewhere in your action or flow. Email : Data type: Record Email record created. ## Testing the email step {#send-email-action__section_r3v_r4s_kcb} To verify that the email was generated when testing the action, review the email record in the Email \[sys_email\] table. The Headers field indicates whether the email was successfully generated. For example: ACL restrictions apply to the Send Email action. If you configured your flow to run as the user who initiates the session, ensure that the user can access email. To test access controls for a Send Email action, impersonate a typical email sender and manually trigger the flow.