Skip to Main Content
Nintex Ideas

đź‘‹ Use this site to provide feedback and ideas for all Nintex Products. See our post on Nintex Community "Welcome to Nintex Ideas" for more details on Nintex Ideas, how an idea is handled by our product teams and more!

If you are looking for the Nintex roadmap, you can find that on Nintex Community

If you have questions about Nintex Ideas, please contact

If you require support, please visit Nintex Customer Central

If you have a sales inquiry, please contact

Status Open for voting
Categories Workflow Designer
Created by Gavin Adams
Created on Oct 18, 2022

Task Responder name in Assign a task to multiple user first response outcome

In the current object output for the Assign a task to multiple users both in the task responses collection and in the first response object there is the 'Task Responder' text variable. This is the email of the user that completed the task.

Frequently we would have a send email action in the outcome branch of the task action where we would want to include the name rather than email of the person who completed the task. To do this we have to use an azure active directory get user details actions to find the name based on the 'Task Responder' variable.

Additionally If we look at the My Nintex / Workflow tracking page for a workflow instance we can see the email and name of the person who completed a task.

It would be very helpful and reduce the number of Azure AD lookups to have 'Task Responder Name' in the Task output object especially in the 'First Response' Object.

  • Attach files
  • Brandi Woodson
    Jan 16, 2023
    Workaround at the moment we found after replying to this is using variables on each form to build full name using context info. This would still be helpful but not priority for us anymore.
  • Brandi Woodson
    Nov 4, 2022

    Is this feature going to be added soon? We definitely need more details regarding the 1st user who responds to a multiple assign task action. We send email notifications to the initiator/created by user following something being approved. We have to use azure directory every time as well and it slows the processing down when they are every where, we have to do it for each branch and have one object per branch - it's annoying! This is another prime example while some objects should be re-useable. We shouldn't have to have a new object in these instances considering we are setting the object only once subject to the route it takes.

    The task form won't allow hidden controls to pass through with information to be used for the rest of the workflow. I have failed in making this work. I can get the full name using context in the task form but I have to have a visible text control where the value is stored for the value to stay with the form after actioning. I don't want to show these fields on the task form. It's tacky. I have seen other ideas that are similar in nature - details regarding the 1st person to respond to a task outcome.