From Field in Send an Email
It would be great to have a From field that supports dynamic references. Most business requirements want emails sent from a specific account, which is not supported in NW in O365!
Jason Blair
shared this idea
To support this requirement we’ve just release the following features
- Specify a customizable sender display name for both email and task actions, we understand one of the main requests was to be able to supply a custom from email address however due to many of the limitations in the cloud we are currently unable to deliver this request and so hopefully being able to add a From display name will get you one step closer..
- Add a customizable Reply To email address for the email action so you can control the email address when people hit reply.
Hope you enjoy these features and be great to hear any feedback once you try them out.
52 comments
-
Jesper Munk Nielsen
commented
Any news on this one? Our client insist on being able to change the "From" e-mail.
-
Sridhar Kandadai
commented
Do you have any update on when this feature will be included. We are starting with migration to Office 365 from Q3 and we would like to plan for this feature
-
Michael Campbell
commented
Can the FROM field be reinstated so we can set this for each email action
-
Paul Wright
commented
We are starting to use workflows to email external customers. They won't know the emails are from us if they don't come from our email address
-
Michael Campbell
commented
Most of my current On Prem Workflows, which I am migrating to Online, have a pre-determeine FROM. I believe this is an essential field as it make the workflows more personal if they can be sent FROM a person rather than a process.
-
Rob
commented
Can I also ask for this to be updated in O365 please? It is critical to the use of a workflow for access requests and is preventing our migration.
-
Wilfred
commented
Ditto, can this be set as a priority in Nintex O365?
-
Erik Rombouts
commented
I agree ... Any progress on this request please?
-
AC
commented
Yes, please.
-
Anita Lovasi
commented
This is a critical feature for our group. We use the FROM field in workflows as part of our contractual approval notification process.
-
Anonymous
commented
Please add this feature, it is critical to some of our workflows...
-
Tim Weston
commented
I encourage the Nintex team to consider adding this feature. As it is now, time-sensitive notification emails are flagged as spam or rejected altogether, causing significant customer service issues.
-
Jillian Love
commented
Please consider adding this feature so that important, time-sensitive emails are not flagged as spam at our organization!
-
Chris Kerry
commented
Please provide this feature. This is causing notification emails to go straight to spam. Oddly, it did not used to do that.
-
Matt Veatch
commented
The absence of this feature is creating customer service issues for our organization. We would strongly encourage the Nintex team to devote development resources to this feature.
-
Debosmita Chakraborty
commented
Any update when this feature will be available?
-
Anonymous
commented
I would like to see this feature added to Nintex. Any progress?
-
Anonymous
commented
Any progress on this topic please ??? It's for sure required !
-
Benjamin Robinson
commented
Allow a "From" Field on communications from Nintex.
-
Anonymous
commented
Hi Team,
Fairly large customer that is in the cloud & looking to use more of our products. One item they are concerned with is Change 'from' Address on O365 workflow:
We use a workflow for new employee onboarding. In that, we send an e-mail to our help desk system for each task that needs to happen to prepare for the employee. As we complete the tasks, our help desk system informs the requestor of completion (i.e. new computer, phone, system access, etc.) Without knowing who the request came from, we have to update each of the help desk tickets to change the “client” to the person initiating the request. Right now, the “from” occasionally picks an unrelated person which is easy to miss. The last few have come from a user in Texas who had nothing to do with the request.