|
This page applies to Appian Cloud only. It may not reflect the differences with Appian Government Cloud. |
Customers of Appian Cloud can use email to enable communication between their Appian Cloud environments and users. This page explains the email features that are available to Appian Cloud customers and how they can be used.
Tip: If your Appian Cloud site is configured for private access (i.e. inbound access enabled only through VPN or PrivateLink) then you will have fewer email options than those outlined below. See the Email Capabilities for Private Access sites section below for more details.
Appian Cloud provides email-as-a-service for all Appian Cloud environments by default. An Appian Cloud environment will send an email for system notifications or when a designer configures a process model to send an email.
Appian supports sending emails with a custom address in the From: header. See Configuring Custom Email Senders page for more information.
Appian Cloud email-as-a-service IP addresses are published in up-to-date Sender Policy Framework (SPF) records. These IP addresses are subject to change.
If Appian detects that an a environment is sending mail that affects the deliverability of Appian Cloud emails, such as spam or a large volume of messages to undeliverable addresses, a limit may be applied to that environment. If this happens to your environment, you will be notified via a support case.
As of release 22.3, it is possible to setup DKIM signing for custom, non-Appian domains.
If you have a custom domain, you can use these instructions to configure DKIM signing in Appian Cloud.
Note that it is not yet possible to configure DKIM signing for Appian-owned domains, i.e. appian-customer.com or appiancloud.com. That functionality will not require customer configuration and will be delivered at a later date.
Appian Cloud email-as-a-service also provides a capability to receive mail. This supports sending an email message to a process.
In Appian Cloud it is possible to start new process instances using an email trigger sent to a specific process model. Appian Cloud environments have been configured to accept incoming email for running processes as well as for specific events.
When an email message is sent to a process model, the message is also received by all running instances of that process model for which there's an active receive message event configured to listen for email messages.
Tip: Appian Cloud email servers are configured with a 70 MB limit for the total size of the email. This includes the email message and all attachments. The 70 MB limit applies to both inbound and outbound emails.
Email messages sent to Appian Cloud processes must use one of the following formats:
1
process<id>@subdomain.appiancloud.com
1
event<eventId>@subdomain.appiancloud.com
1
2
processmodel<id>@subdomain.appiancloud.com
processmodeluuid<model_uuid>@subdomain.appiancloud.com
Due to email's unique reliance on DNS records associated with a site, private access sites (i.e. inbound access enabled only through VPN or PrivateLink) have fewer email capabilities than publicly available sites. Email on private access sites can be enabled using the following options:
With either of the above options you'll be able to utilize custom email senders on your private access cloud site.
If the Appian Cloud email-as-a-service does not meet your requirements, you may use your own custom email service for outbound email, inbound email, or both. A secure, network connection to your email service is required. This may require creating a VPN integration. Information on the requirements for configuring a VPN integration tunnel can be found on the Self Service VPN page.
Once a secure, network connection is available, create a support case on Appian Community to have your environment configured to use your custom email service.
