--- 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 --- # Automated Send Email activity # Automated Send Email activity {#ariaid-title1} * Release version: Australia * * Updated March 12, 2026 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 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 Automated Send Email activity The Automated Send Email activity enables you to create and send emails automatically within a playbook without requiring user input or pausing the workflow. Once triggered, it immediately sends the email and advances to the next activity. This streamlines communication processes by automating email notifications based on data collected or generated earlier in the playbook. Show full answer Show less ## Roles and Availability This activity is available as a common activity and can be added to playbooks by users with the **admin** , **playbook.admin** , or **pdauthor** roles. ## Configuring Inputs Inputs for the activity are configured via the activity properties panel. Key inputs include: * **Label**: Title displayed on the activity and playbook card. * **Description**: Information about the activity's usage or outcome. * **Run condition**: Conditions under which the activity runs, based on prior data. * **Start Rule**: Defines when the activity or stage begins (e.g., at playbook start, after specific stages or activities). * **Start with delay**: Optional delay before execution. * **To**: Recipient list for the email, configurable either as fixed email addresses or dynamically using pill-picker to reference data from records (e.g., customer email from an application record). * **Cc**: Carbon copy recipient list, similarly configurable. * **Subject**: Email subject line. * **Body HTML**: Email body supporting rich text, HTML, and dynamic content through pills. The pill-picker is essential for dynamically populating fields with data from records, enabling personalized and context-specific emails. ## Advanced Inputs Additional optional inputs allow further customization, including: * Comma-separated email address strings for To, Cc, and Bcc fields. * Bcc recipient lists for blind copying. * **Target Record**: Reference to the record to which the email is attached. * **Table Name**: Specifies the table containing playbook or activity data. ## Outputs The activity produces outputs that can be utilized by subsequent playbook activities, such as: * **Record**: Reference to the task record created. * **Email**: Reference to the created email notification record. ## Practical Benefits for ServiceNow Customers By leveraging the Automated Send Email activity, customers can: * Automatically notify users or stakeholders without manual intervention. * Ensure timely communication by embedding email sends within automated playbook workflows. * Personalize emails dynamically based on playbook data. * Maintain audit trails by linking emails to relevant task records. This activity enhances operational efficiency and consistency in communication within ServiceNow playbooks. Create an email from previously gathered or generated data without pausing the playbook to ask for user input. When the activity runs, it immediately sends the email and continues to the next activity in the playbook. ## Roles and availability {#automated-send-email-activity__section_pwq_rb5_kcb} This activity is available as a common activity. Users with the admin, playbook.admin, or pd_author can add this activity to a playbook. ## Inputs {#automated-send-email-activity__section_yb4_zq3_plb} Open the activity properties panel and configure your activity to add values for the following inputs. If the input value varies, use the pill-picker to show where to get the value. To learn more about the pill-picker, see [Dot-walking examples](https://www.servicenow.com/docs/access?context=dot-walking-examples&version=australia&pubname=australia-platform-user-interface&ft:locale=en-US). {#automated-send-email-activity__table_ajt_sr3_plb__entry__3} | Input | Type | Description | |-|-|-| | Label | String | Title to display as activity and playbook card. | | Description | String | Information to display about activity usage or outcome. | | Run condition | Condition Builder | Conditions that must be met to run an activity or stage. You can use data from prior activities to build conditions. Note: Select Show additional options to see this field. | | Start Rule | Choice | Under ScheduleStart Rule, select a start rule for when your stage should start running: * When process starts: Your stage starts running as soon as the playbook starts. * After specific stages: Your stage starts running after specified stage(s) have finished running. {#automated-send-email-activity__ul_f4z_nq1_ppb}Under Schedule \> Start Rule, select a start rule for when your activity should start running: * When stage starts: Your activity starts running as soon as its stage starts running. Your stage starts running when your playbook is triggered. * After specific activities: Your activity starts running after specified activities have finished running. {#automated-send-email-activity__ul_zzc_3ls_m1c} | | Start with delay | True/False | Option to wait for a duration of time before running an activity or stage. When enabled, this input displays the [Start with delay input properties](https://servicenow-prod.fluidtopics.net/EdInaaLAHZCnrBcJbs96Lw "Specify a duration of time to wait before running an activity or a stage whose start rule and conditions have been met. Give users time to act during automated playbooks. Give users time to wait for a specific date and time to complete actions."). Note: Select Show additional options to see this field. | | To | List of Users | Recipient list for the email. There are 2 ways to configure this field: * Enter email addresses as strings if you want the emails to go to the same addresses every time. * When the email address value varies, use the pill picker to indicate where to find the recipient email address. For example, you would use the pill picker if you wanted to automatically notify credit card applicants of a rejection, because each applicant has a different email. You would select the customer record from the trigger (when the application was submitted), because that is where the applicant's email address is found.
{#automated-send-email-activity__ul_zzl_x1h_lwb} | | Cc | List of Users | Cc recipient list for the email. | | Subject | String | Subject of the email. | | Body | HTML | Body of the email. Tip: You can use both text and multiple pills in your message, and any other rich text or HTML field. | [ ] {#automated-send-email-activity__table_ajt_sr3_plb} ## Advanced inputs {#automated-send-email-activity__section_bgh_1r3_plb} After configuring the required inputs for your activity, you can also choose to configure additional inputs. In the side panel, select Show additional options to display these advanced inputs. For more information, see [Activity experience](https://servicenow-prod.fluidtopics.net/aEvbv54ObgcCjjhXabvx8w#activity-definitions__activity-experience). {#automated-send-email-activity__table_cjj_sr3_plb__entry__3} | Input | Type | Description | |-|-|-| | To Email Address | String | Comma-separated list of email addresses. | | Cc Email Address | String | Comma-separated list of copied email addresses. | | Bcc | List of Users | Bcc blind copy recipient list for the email. | | Bcc Email Address | String | Comma-separated list of blind copied email addresses. | | Target Record | Reference.Task \[task\] | Reference to the record that the system attaches the email to. | | Table | Table Name | Table containing activity or playbook data. | [ ] {#automated-send-email-activity__table_cjj_sr3_plb} ## Outputs {#automated-send-email-activity__section_unx_fr3_plb} These outputs can provide data to other activities in your playbook. You can access this data as activity inputs when you configure your activity: {#automated-send-email-activity__table_mv2_rr3_plb__entry__3} | Output | Type | Description | |-|-|-| | Record | Reference.Task\[task\] | Reference to record created. | | Email | Reference.Notification\[sysevent_email_action\] | Reference to the newly created email notification record | [ ] {#automated-send-email-activity__table_mv2_rr3_plb} *[\>]: and then