--- sourceDocument: Brazil Build workflows sourceDocumentLink: https://www.servicenow.com/docs/r/build-workflows Release : - brazil ft:locale : - en-US ft:publication_title : - Brazil Build workflows ft:clusterId : - crworkflow bundleId : - crworkflow workflow : - Creator --- # Send Email action # Send Email action {#ariaid-title1} Release version: Brazil Updated September 10, 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 action The Send Email action in ServiceNow allows you to send emails to specified users or groups as part of a flow within Workflow Studio. This action is available to users with theflowdesigneroradminroles, enabling them to add and configure email sending capabilities in automated workflows. The email can be associated with a specific record, allowing replies to update that record. Show full answer Show less ## Configuration Inputs * **Target Record:** The record (Document ID) linked to the email. Replies update this record. * **Table:** The table containing the target record. * **To:** Primary email recipients. Accepts comma or whitespace-separated email addresses or data pills containing emails (e.g., user or group emails). To email a group, use the group's email address and ensure group members are included if needed. * **CC and BCC:** Additional recipients copied or blind copied, supporting multiple addresses or data pills. * **Subject:** Email subject line, supports static text or dynamic data pills. * **Body:** Email content supporting text and data pills with inline styling. Note that Email Template variables are not supported and must be replaced with data pill references. ## Key Considerations * The number of recipients must not exceed the limit defined by the system property `glide.email.smtp.maxrecipients`. * Replies to the email update the associated target record. * Access Control Lists (ACLs) apply; ensure the user running the flow has permissions to send email. * Testing involves checking the generated email record in the **Email \[sysemail\]** table, specifically the Headers field to confirm success. * When sending email to groups, verify the group's "Include members" option is enabled to target individual members rather than just the group's email address. ## Outputs The action outputs an **Email** record representing the created email, which can be used as input for subsequent steps in the flow. ## Practical Use Case Example An example use case is sending an email automatically when an incident record is created, provided the assigned user is specified and the incident category matches certain criteria (e.g., inquiry/help). The email is dynamically addressed to the assigned user and references the incident number in the subject and body, illustrating how flow data integrates into email content. ## Additional Configuration To enable full email capabilities, configure your ServiceNow instance's email administration settings to send and receive emails correctly. Send an email to specified users or groups as an action in a flow. ## Roles and availability {#send-email-flow-designer__section_pwq_rb5_kcb} Available as a Workflow Studio ServiceNow core action. Users with the flow_designer or admin role can add an action to a flow and define configuration details. ## Inputs {#send-email-flow-designer__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=brazil&pubname=brazil-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. ## Outputs {#send-email-flow-designer__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. ## Configuring instance Email {#send-email-flow-designer__section_qst_ydb_hbc} For information about configuring your instance to send and receive email messages, see [Configure email administration](https://www.servicenow.com/docs/access?context=configuring-email-admin&version=brazil&pubname=brazil-platform-administration&ft:locale=en-US). ## Testing the email action {#send-email-flow-designer__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. ## Send email when incident created {#send-email-flow-designer__example_hqt_23c_hbc} In this example, the system sends an email whenever an incident record is created where the Assigned to filed is not empty and when the incident category is inquiry/help. The incident trigger record provides the values used by the send email action. For example, the email is sent to the email address of the assigned to user, and the email subject and email body both refer to the incident number.