Enhancement: Workflows Email Action - CC/BCC

:sparkles: Description

Workflows is excited to announce the addition of CC and BCC fields to the Send Email action. Until now, recipient routing has been limited to Recipient Email Addresses with no CC or BCC, so reaching additional audiences with the same message often meant multiple Send Email steps or duplicate templates.

Send Email now supports To / CC / BCC in one action: primary recipients in Recipient Email Addresses, plus optional CC and BCC.

:information_source: What You Need to Know

  • Existing workflows keep working. Send Email steps you already configured are not modified automatically. They continue to send as they do today until you edit them.

  • CC and BCC are optional fields and each field allows up to 10 recipients.

:exclamation: Problem

Send Email lets you define who receives the message only through Recipient Email Addresses with no CC or BCC. When more people or mailboxes need the same email (same content), teams often use multiple Send Email steps or separate templates — for example copying a line manager while emailing an employee, or adding a shared mailbox without listing it as the primary recipient.

:bulb: Solution

Sending behaves like a standard email:

  • To — Recipient Email Addresses (required): primary recipients; same role as before.

  • CC — optional; recipients who receive the message and are visible to others on the mail (standard CC behavior).

  • BCC — optional; recipients who receive the message without being visible to To or CC recipients (standard BCC behavior).

:people_hugging: Who is affected?

Workflows Users.

Action Recommended: Review and adopt CC/BCC when it simplifies workflows that today use multiple Send Email actions for the same notification.


:calendar_spiral: Important dates

Sandbox availability: - Jun 8, 2026
Production: Jun 15, 2026 - Jul 6, 2026

14 Likes

Great addition! Thanks @Takato

Wonderful, go to see this enhancement

Great, I just had quick curious question many released updates are not have back ward compatibilty , is it difficult make backward compatibility in SaaS while in IIQ we are updating/ upgrading everything with one efix or patch file

Thanks

Avinash Mulpuru

Finally. Been working around this for years. Best I could do was stuff multiple addresses into a variable and pass it to the To field. Gets the job done but everyone shows up as a primary recipient. Good to see proper CC/BCC support added. Thanks @Takato

1 Like

@amulpuru are you asking about ISC in general or specific to workflows?

Simple, elegant and very useful! Thank you @Takato!

Wondering why a limit of 10 was chosen instead of 250 (a limit used a lot in ISC) . I think that would make it more difficult to send a CC/BCC mail to all members of a given governance group.

Im looking for ISC in general

Thanks for the addition, awaiting on this quite some time.

This is probably a better question in a separate thread or in Compass.

Thanks @angelo_mekenkamp . Governance group and increasing the limit are enhancements we’ll take on separately.

1 Like

Thank you @Takato for including CC and BCC functionality. This enhancement significantly improves our workflow by allowing us to efficiently email multiple users without duplication.