Action By Email Upgrade

The Action by Email functionality in Archer SaaS enables users to take specific workflow actions directly from their email without needing to log into the platform. This feature enhances efficiency by allowing users to respond to approval requests, update records, or trigger automated workflows with a simple email reply. By streamlining decision-making processes, it helps organizations improve responsiveness and operational agility. For more details on configuring ABE, you can refer this blog:

https://www.archerirm.community/s/article/Advanced-Workflow-Actions-By-Email-Configuration-Checklist-in-Archer

For the Archer SaaS Workflow Action by Email functionality to work properly, specific network configurations must be in place. Currently, this requires either disabling the IP trust list on the instance or, if the IP trust list is enabled, ensuring that the entire AWS IP range is whitelisted at the instance level. Both of which are not the ideal scenarios. The underlying issue arises from the dynamic IP assigned to the Lambda function deployed in the default VPC, which is not whitelisted on instances where the IP trust list is enabled. As a result, the function is unable to establish a connection with the platform endpoints for further processing. Both of which are not the ideal scenarios.

The upgraded ABE service will addresses these challenges by hosting the Action by Email (ABE) Lambda function in a private subnet within a dedicated VPC. All traffic to Archer Platform (AP) is redirected via a NAT Gateway in the public subnet. The NAT Gateway’s Elastic IP will be whitelisted in AP to allow incoming traffic. This approach provides a more secure and controlled way to enable the Action by Email functionality without compromising security or requiring excessive IP whitelisting.

Note: This solution specifically addresses the whitelisting of AWS IPs that had to be whitelisted for ABE functionality to work. If any additional IP addresses have been whitelisted at the instance level for other operational requirements, they should continue to be maintained as per the existing configurations.

This functionality has been made available in AU, Canada and India