--- 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 step # Send Email step {#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 step The Send Email step allows you to send emails to specified users or groups as an action within a flow in Workflow Studio. This step is designed for users with theactiondesignerrole who create custom actions incorporating one or more action steps. It supports dynamic input values using data pills from the Data panel, enabling personalized and record-linked email communications. Show full answer Show less ## Inputs * **Target Record (Document ID):** The record the email is associated with; replies update this record with the email content. * **Table (Table Name):** Specifies the table containing the target record. * **To (String):** Primary recipients' email addresses. Accepts comma or whitespace-separated emails or data pills (e.g., User or Group records). To email groups, provide a Group email address or enable "Include members" to email group members. * **CC (String):** Additional recipients copied on the email, entered similarly to the To field. * **BCC (String):** Recipients blind copied, visible only to the sender. * **Subject (String):** Email subject, supporting static text or data pills. * **Body:** Email message content with inline styling options. Content can include static text or data pills. Note that email template variables (e.g., ${number}) must be replaced by data pill references, as the Send Email action does not process template variables directly. * **Action error evaluation:** Defines behavior if the step fails, with options to continue or trigger error evaluation. ## Outputs The step outputs an **Email record** that appears in the Data panel, allowing further use within actions or flows. ## Testing and Considerations * Verify email generation by reviewing the email record in the **Email \[sysemail\]** table; the Headers field confirms successful creation. * Access control restrictions apply: ensure the user context running the flow has permission to send emails. * When testing, impersonate typical email senders and manually trigger the flow to confirm email permissions and behavior. * The maximum number of recipients is limited by the **glide.email.smtp.maxrecipients** system property; plan recipient lists accordingly. This action step empowers ServiceNow users to automate email notifications linked to records and workflows, enhancing communication efficiency while maintaining control over recipients and content. 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=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. ## 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://www.servicenow.com/docs/DYUWPGHPp4xlTo_Ny0q7aQ "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.