Add an email automate action

Integrating with email or mailing lists allows Red Canary to send emails as part of an automation playbook.

1. Within any playbook, click Add Action.
2. Click Email, Send Email and then click Add to Playbook.
3. Specify email recipients in the To field by entering comma-separated email addresses. These can be determined dynamically using variables, such as using $Detection.marked_acknowledged_by_user.email to send an email to the user who acknowledged a detection.
4. Specify the Reply To address for the email. This address is used when a recipient clicks the reply button in their email client and is useful for routing responses back to your security or support team.
5. Select a Template and fill in any additional message fields supported by the template.
6. Click Save.

Email templates

You shouldn’t need to start from scratch every time you want to send an email, so we provide several pre-built templates.

Custom Freeform Email

This template is a completely freeform email. Enter text in the Message field and you will receive an email with exactly that.

Here’s an example:

Which produces this email:

Threat: All threat data as JSON

This template is designed for systems that read structured JSON data from emails; ServiceNow is a common recipient for these messages. The associated threat is sent in JSON format in the email body.

Note: This template is only valid for threat-based triggers.

Here’s an example:

Which produces this email:

Threat: Published notification in HTML

This template sends information about a threat to users in a condensed, summary format that includes a brief list of identified indicators of compromise.

Note: This template is only valid for threat-based triggers.

Here’s an example:

Which produces this email:

Threat: Human-readable HTML with full timeline

This template sends information about a threat to users in a condensed, summary format with the complete timeline of the threat, including all relevant activity and identified indicators of compromise.

Note: This template is only valid for threat-based triggers.

Here’s an example:

Which produces this email: