Builder View 

• Drag and drop the Email state from the Notifications section in the left pane of Builder View.
• Select the state and open the Configuration pane. Update the common state field attributes.
• From the Email Templates dropdown, select a template associated with the circuit.
  

1. To / To Recipients Path  
   
• To: Manually enter one or more recipient email addresses, separated by commas.
• To Recipients Path: If recipients need to be set dynamically, specify their email addresses using a JSON path (e.g., $.email).
  
2. CC / CC Recipients Path  
• CC: Manually enter the CC email addresses, separated by commas.
• CC Recipients Path: Use a JSON path to assign CC recipients dynamically.
  
3. BCC / BCC Recipients Path  
• BCC: Manually enter the BCC email addresses, separated by commas.
• BCC Recipients Path: Provide a JSON path to dynamically specify BCC recipients.
  
4. Files / Files Path  
• Files: Select files from the dropdown list, which shows files from the Qntrl Files module.
• Files Path: Enter a file path manually if you're passing files through input JSON.
  
5. On Failure  : Choose how the Circuit should behave if TransMail fails(e.g., delay or delivery issue). This setting does not handle validation failures like invalid email and will cause the state and circuit to fail
• Continue: Proceed to the next state even if the email fails.
• Stop: Stop circuit execution if email delivery fails.
  
6. Custom Data  : Custom placeholders from the email template appear here for mapping dynamic values from the circuit input(e.g., dynamic placeholders like due dates, usernames, etc.).
   

• The combined size of all files (from both templates and configuration) must not exceed 14 MB.
  

• If one of the recipient emails is incorrect, the entire email will fail to send.

• To, CC, and BCC: Max 10 recipients each.
• Files: Max 3 files.

Code View 

In Code View, the JSON to execute a Task Engine state is given below.

{
	"Licence Key Activation Notification": {
		"type": "email",
		"next": "End",
		"email_template_id": "notification_email_12",
		"payload": {
			"on_failure": "continue",
			"to": [
				"jennifer.dsousa@sweriocorp.com"
			],
			"files": [
				"employee logs.xml",
				"license_key_config.json"
			],
			"bcc": [
				"monica.thomas@sweriocorp.com"
			],
			"cc_recipients_path": "$.cc_mails"
		},
		"start": true,
		"parameters": {
			"Date": "07.07.2025"
		}
	}
}

Troubleshooting   

1. Can I use an email template created for Boards in a Circuit?

2. Why did my email notification fail even though the configuration seems correct?

3. Why did the circuit continue after the email state failed?

4. Why are my attached files not being delivered in the email?

5. Why can't I find the email template I created in the dropdown?

6. Can I attach files from both the Email Templates attachments and the Email state file configuration?