E-mail services

<< Click to Display Table of Contents >>

Navigation:  Low-code Process Automation > Automation - Test and Production environments > Enterprise Subscription >

E-mail services

Overview

With Bizagi you may configure your processes to rely on email services so that your processes can:

Send customized notifications to your users or customers, regarding the business.

Have Bizagi send out automatic notifications regarding a task being ready to be worked on (as soon as it is allocated).

Rely on alarms set off as reminders for tasks which are overdue.

Integrate the processes' workflow so that tasks can be completed via email replies.

Achieve Multi-factor authentication to enhance security by requesting two or more pieces of evidence from the user that is attempting to log in

 

A cloud emailing service is included along with the subscription. This module is configured for all the environments of your subscription.

When using this service, your process applications will send out email notifications from a SendGrid cloud service.

Bizagi is in charge of the service configuration as well as the managing and monitoring.

 

Technical specification

Communication is done using the SMTP protocol, through port 587 using TLS.

SendGrid is the emailing solution recommended by Azure to work best with Azure's cloud services. Click here to read about SendGrid securicy policies.

The total message size of emails sent is limited to 20,480,000 bytes, or approximately 19.5MB. SendGrid recommends that attachments do not exceed 7MB. If these values ​​are exceeded, the email will not be sent. As an alternative, we strongly suggest to use links when sending files via email.

 

Important considerations

You are entitled to use Bizagi's emailing service. This module is configured for all the environments of your subscription. When using this service, your process applications will send out email notifications from a SendGrid cloud service.

 

If you do not plan to use Bizagi's emailing service and wish to use your own email service, submit a support ticket stating so. You can directly integrate your corporate SMTP email service if it is cloud-ready, or by using a VPN.

When choosing this option, you will not be able to use Multiple senders (From option) when configuring notifications.

Make sure you read and understand the specifications below, and visit Considerations for your own SMTP.

 

If you choose to use your own SMTP, consider the following:

If the SMTP is accessible from the VPN configured by Bizagi, you must inform this to our Bizagi Support team. This does not apply for Office 365.

You can use port 587 or 465 using TLS. Port 25 is not supported (port 25 is supported only when using VPN; the VPN encrypts the information).

SMTP must support HTTPS authentication. Other authentication protocols are not supported.

The SMTP must be configured with an existing service account (e.g., no-reply@mycompany.com). This service account is going to be used to send emails from Bizagi, and must be dedicated for that purpose.

The SMTP service account cannot have multi-factor authentication.

We recommend you choose a non-expiring password. Otherwise, you must inform Bizagi through a support ticket when the password changes.

You are in charge of configuring and managing the SMTP.

Bizagi is not responsible of issues related to the SMTP that can affect the execution of processes.

The same SMTP can be use for both Test and Production environments. However, you can define an SMTP per environment. If you do so, you need to inform our Bizagi Support team, and deliver the information for each SMTP service account (one for each environment).

 

When you have configured the SMTP, you must request a support ticket and provide the following information:

SMTP URL: URL of your SMTP server or relay.

Port: Port number to access the SMTP URL.

User Name: User name to access the SMTP server.

Password: Password to access the SMTP server.

From email: Emails that send email notifications in processes will have this sender. The SMTP must admit the domain that the "From Email" has.

CC: If you need to send a copy for every email notification sent by Bizagi, send this parameter. This must be one email only.

BCC:  If you need to send a behind copy for every email notification sent by Bizagi, send this parameter. This must be one email only.

Regarding completing tasks via email, you are entitled to use Bizagi's email integration service. This module is configured for all the environments of your subscription.

When using this service, your process applications will send a response to a specific mailbox service in which Bizagi uses a dedicated account.

 

What should I do as a customer?

By default the emailing service has the following domain:

bizagimailer.com

Thus, by default, your emails will be sent from: noreply-environment-project@companyname.bizagimailer.com

 

When you purchase Bizagi Automation Services, you can define the domain that is going to be used by the service to send emails. For example @mycompany.com.

Thus, you can define the desired domain and authorize Bizagi to send emails on your behalf. This is done through a concept called Automated Security, in which SendGrid handles the signing of your DKIM and authentication of your SPF, for your outbound email. You need to add CNAME records (that will be sent to you), in your DNS.

If you have DMARC configured in your domain, Bizagi can support it.

For more information, refer to Define email sender configuration.


Last Updated 9/1/2023 9:12:08 AM