Skip to main content
Question

Email Alert Configuration in Google SecOps via SOAR (EmailV2)

  • January 30, 2026
  • 3 replies
  • 67 views

Forum|alt.badge.img+1

Hi Team, I am configuring email alerts in Google SecOps through SOAR using the EmailV2 integration and would like to confirm the recommended approach. Could you please share the correct steps to configure email alerts end-to-end (Google SecOps detection → SOAR playbook → EmailV2 → SMTP/IMAP)? Additionally, I need clarification on which details should be used for the EmailV2 integration, including the email address, username, password, SMTP server and port, and IMAP server and port. Specifically, should the email address and SMTP/IMAP server details be taken from the SOAR mailbox or from a client/user mailbox? Any guidance or documentation reference would be helpful. Thanks in advance for your support.

3 replies

hzmndt
Staff
Forum|alt.badge.img+10
  • Staff
  • January 30, 2026

@Jmevawala depends on your SMTP config, sample using gmail.com

 

  1. Deteciton Rule create alert 
  2. alert pulled by SOAR connector to SOAR, case created
  3. Playbook run and use EmailV2 integration to send email (action: Send Email)

https://docs.cloud.google.com/chronicle/docs/soar/marketplace-integrations/email-v2#send_email

 

 


Forum|alt.badge.img+1
  • Author
  • January 30, 2026

@hzmndt Could you please share the playbook configuration you have created for the EmailV2 integration to send alert emails?
 

 


cmorris
Staff
Forum|alt.badge.img+11
  • Staff
  • January 30, 2026

Likely depends on your use case - ex. notification for SOC, escalation, sending an approval link, etc. You can use the placeholders in the action itself to share information specific to the case: