Skip to Main Content

Add a CC email to the Assign a Task action

In the 'Assign a task' action in Nintex for Office 365 and Flexi task for Nintex for SharePoint there is an option to CC or BCC the task notification email.
Please add CC and BCC to the NWC 'Assign a task' action.

This is important as we migrate from the feature rich Nintex for SharePoint or Office 365 to NWC.
  • Attach files
      Drop here to upload
    • Guest
      Reply
      |
      Apr 24, 2025

      Similar requests to this one in case anyone here would like to cast votes on them:
      https://ideas.nintex.com/ideas/CNV-I-409 - "Add CC/BCC on task assignment notifications or provide log in the workflow instance showing output and metadata"
      https://ideas.nintex.com/ideas/CNV-I-173 - "Allow access to emails that are sent by Nintex per workflow instance"
      https://ideas.nintex.com/ideas/CNV-I-330 - "Add ability to CC users in tasks and task reminders"

    • Guest
      Reply
      |
      Nov 6, 2024

      I have many users in my company requesting this functionality, can you please prioritize for your next quarterly review?

    • Admin
      Kate Huynh
      Reply
      |
      Oct 5, 2023

      Thank you all very much for posting your feedback on Assign a Task to Multiple Users. At this time, we will not be moving this request to the near-term backlog, as we are focused on other critical initiatives. However, we reevaluate requests every quarter, so please keep the feedback coming as it is critical for our longer-term planning.

    • Guest
      Reply
      |
      Mar 6, 2023

      Is there an ETA for this one? Last update I received was the end of Feb by our success team. I don't see this available yet. Please advise.

    • Guest
      Reply
      |
      Jan 10, 2023

      Thanks for the prompt feedback and clarification on this one. Greatly appreciated. :)

    • Admin
      Neeti Kulhar
      Reply
      |
      Jan 10, 2023

      Yes, that's correct - Assign a Task action is being removed this week. This functionality would be added to the Assign a Task to Multiple Users action in Nintex Automation Cloud.

    • Guest
      Reply
      |
      Jan 10, 2023
      I thought assign a task action was removed as of 1/1? Will this apply to multi assign task action in cloud as well?
    • Admin
      Neeti Kulhar
      Reply
      |
      Jan 10, 2023

      Thank you for your feedback. The Cc/Bcc functionality for task notification is being targeted to be included in the next 3-6 months.

    • Guest
      Reply
      |
      Jan 10, 2023

      +1 to this although ideally there would be an option to assign a task as a "CC" in addition to the email aspect. Further, a task level configuration should be available to determine who can complete the task be this: the primary recipient(s), the CC recipients or both.

    • Guest
      Reply
      |
      Nov 9, 2022

      So, is this being added? We really need this functionality soon. Most of our users use the task email to follow-up with approvers of a task. They also don't know if the email for the task went through to specific task owners and they get a bit nervous too.

    • Guest
      Reply
      |
      Sep 7, 2022
      Thank you for sharing your feedback, Gavin! I've heard from our sales team similar needs from other organisations, so I have encouraged them to send this request to anyone who needs it. I've spoken to you about a workaround 1:1, but I thought I'd share it here, too. So anyone who has a similar use case has an option to work with, in the absence of a native CC/BCC capability.

      My recommendation is to use a "Run parallel paths" action, with an "Assign a task" action in one branch, and "Send an email" in the other. The email is used as the notification that a task has been assigned, and while it's not a CC or BCC, at least you have communication around the task assignment.

      If you have any feedback about this workaround, let me know. While I understand this could work for some processes, everyone's needs are different. If it doesn't work for you, please expand on why, so our product team has more context about how to integrate this capability natively.