# Epicor BPM Send Email: Widget, Function and SMTP Setup > Source: https://netray.co/erp-help/epicor-bpm-send-email-widget-function-smtp > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Help ## Short answer To send email from an Epicor Kinetic BPM or Epicor Function, make sure the server SMTP settings work, then add a Send Email widget to the directive or function and fill the To, Subject, Body and optional attachment. Test the SMTP path first with a standard email-producing action, because most failures are server mail settings, not the widget. ## Kind how-to ## System epicor ## Erp Epicor Kinetic ## Module BPM / Epicor Functions / Email ## Query epicor bpm send email ## Alternate Queries - epicor function send email - epicor bpm email attachment - epicor bpm smtp not sending ## Applies To Epicor Kinetic 2021 and later, Method and Data Directives, Epicor Functions; SMTP as configured by the server administrator ## Steps ### How to send an email from a BPM or function **Items:** - Confirm the Epicor server can send mail: the SMTP host, port, authentication and from-address are set in the server's email configuration, and the mail server allows relaying from the Epicor application server. - Prove it before building: trigger any standard Epicor action that emails (an order acknowledgement or a report set to email) and confirm it arrives. - Open the directive (BPM Method Directive Maintenance) or the function (Epicor Functions Maintenance) and add a Condition widget so the email only fires on the case you want. - Add a Send Email widget on the true branch. Set From, To, Cc, Subject and Body. Use variables or fields to fill the recipient and text. - If you need an attachment, generate or locate the file first and reference it in the widget's attachment setting. Keep the file reachable from the application server. - For HTML bodies, build the string in a variable first and pass it in, so you can test the text in isolation. - Enable the directive, save the function, then test with a recipient list that contains only you. - Check the server trace log for the SMTP exception text if nothing arrives, and the recipient spam or quarantine folder. ## Sections ### Where email actually fails **Body:** The widget is a thin layer over the server's mail client. When nothing arrives, the cause is usually outside the BPM: wrong SMTP host or port, TLS mismatch, an authentication account without permission to send as the from-address, or a firewall rule between the Epicor server and the mail relay. Microsoft 365 tenants that disabled basic authentication frequently break older SMTP setups. Use a from-address your mail system accepts. Many relays reject mail whose sender domain does not match the authenticated account or is not allowed to relay. Fixing that on the mail side is faster than any workaround in the BPM. ### BPM versus function: which should send **Body:** If the email is a side effect of a transaction (a job released, an order held, a receipt posted), a Method Directive in Post-Processing is the natural place. If many directives need the same email format, put the Send Email widget in an Epicor Function that takes the recipient, subject and data as parameters and call it from each directive. Functions keep the formatting and recipient rules in one maintained place, which matters when someone changes the template a year later. The trade-off is one more object to secure and version, so for a single one-off alert the widget in the directive is enough. ### Testing safely **Body:** Never test an outbound email BPM against live distribution lists. Add a condition that sends to a single test address when the company or site is a test one, or route all recipients through a variable you can override. Throttle in the design. A Data Directive on a high-volume table that emails on every row will flood a mailbox during a DMT load or mass update. Add a condition on a status transition and guard against firing in bulk imports. ## Pitfalls - Building the widget before confirming the server SMTP configuration works. - Emailing from a Data Directive that fires on every row during imports and floods recipients. - Using a from-address the mail relay does not permit, causing silent rejection. - Pointing an attachment at a path only your workstation can see, not the application server. - Leaving real customer addresses in a BPM that runs in a test company. ## Ai Angle An assistant that reads your Epicor configuration can show which directives send mail and to whom, which helps when someone asks why a customer received a message. ERPray can answer questions such as which orders triggered a notification, with the underlying query visible. Changing a directive stays a reviewed change. ## Faq ### Why does my Epicor BPM send email widget do nothing? **Answer:** The directive may be disabled, the condition may never be true, or the server SMTP settings may be wrong. Test a standard Epicor email first, then check the server trace log for the SMTP exception. The widget itself rarely fails on its own. ### Can an Epicor Function send an email? **Answer:** Yes. Epicor Functions support a Send Email widget in the designer, so you can wrap the email in a reusable function and call it from BPMs, other functions or an external REST call. ### How do I attach a file in an Epicor BPM email? **Answer:** Generate or locate the file on a path the application server can read, then reference it in the attachment setting of the Send Email widget. Verify permissions on the folder for the account the server runs as. ### Does Microsoft 365 work with Epicor BPM email? **Answer:** It can, but tenants that disabled basic SMTP authentication need a supported relay or connector configuration. Ask your mail administrator how the Epicor server should authenticate before you debug the BPM. ## Search terms epicor bpm send email, epicor function send email, epicor send email widget, epicor bpm email attachment, epicor smtp settings, epicor kinetic email notification, epicor bpm notification, epicor bpm email not sending --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json