Power Apps and Automate allow you to send emails not from the one who pressed the button, but from an alternative source. This is achieved through SharePoint, providing more control over email titles and replies. Using the SharePoint Rest API, you can easily make this transition.
Some limitations exist such as inability to send emails to external users or attach files. Moreover, this method only works when sending to users familiar with SharePoint site, i.e., people within the user table or users who have interacted with the SharePoint site.
The SharePoint Site Title can be altered to control what is displayed in the 'From' Field of the email when sending a no-reply message. Making this adjustment ensures that the receiver sees a specific title when they receive a no-reply email. You can also integrate this flow within a Power Apps App for dynamic content. Moreover, using Combobox and Concat allows you to manipulate and create the email string you need. Notably, the demonstration showcases sending a no-reply email from a 'PowerApps911' employee email to two recipient emails, illustrating the functionality of the feature.
This text has introduced the ability to send emails on behalf of others using Power Apps and Automate by using SharePoint. This method provides better control over setting the email's title and routing any replies to the chosen 'sender'. This is achieved through a small call to the SharePoint Rest API. Furthermore, the text has highlighted some functions and features including: Sending a no-reply email from SharePoint, demonstrating the functionality, building a Power Automate flow, and the integration with Power Apps for dynamic content. The goal is to create a system where the emails do not technically originate from a specific user, but replies can be routed back to the user performing the task.
Microsoft SharePoint emailing, Power Apps automation tutorial, Power Automate Flow guide, Emails control via SharePoint, SharePoint Rest API for emailing