Setup guide
1. Install the add-in
Sideload the manifest from this site, or install from AppSource once it is listed. Sign in with your work or school account.
2. Standard path — Power Automate + OneDrive
- Download the importable flow: legacy package (.zip) or Dataverse solution (.zip). SHA-256 checksums are published on this page after the templates are built.
- Import the package in Power Automate. The trigger is When a file is created (properties only) on the folder
/MailToAuto/jobsin your OneDrive. The properties-only trigger is required so large sidecars are not skipped. - The first time you run a button, the add-in creates
/MailToAuto/jobs,/MailToAuto/payload, and/MailToAuto/results. - Treat every field in the job file as untrusted plain text. Never pass subject, from, answers, or file names into expressions, HTML, or SQL. Deduplicate on
jobId(the OneDrive trigger can fire twice). After you finish, write/MailToAuto/results/{jobId}.ok.jsonor.err.json.
3. Premium path — a webhook you paste
You can paste a webhook URL from Power Automate, Zapier, Make, or n8n Cloud. Only those hosts are accepted. The add-in posts from Outlook with mode: 'no-cors' and shows Sent, delivery not confirmed. We cannot see whether the host accepted the body. Secrets belong in the URL the provider gave you, not in a custom header.
Cleanup
On open, the add-in deletes job and payload files older than 7 days (you can choose 1–30 days) and result files older than 7 days, matching only our file-name patterns under those three folders. Nothing else is deleted.
Template checksums
mailtoauto-flow.zipSHA-256f7ecddd046634dff2fe572585b5f9adbf07f6a5bf2486f849d3f76a5501ae871mailtoauto-solution.zipSHA-2569862c164e75fa57ac7ecf404f43985d130f75f8e10cb1ac57de48f752a953e4c