We’re happy to announce the public preview of (phase 1) the Bring Your Own Email (BYOE) feature in AppSheet!
With this launch, Workspace users will be able to send Automation Emails from their own email addresses, instead of the default ‘noreply@appsheet.com’.
Important Note: This public preview of phase 1 of BYOE only supports Workspace customers. We are planning non-Workspace support in the coming quarters.
Benefits
Using BYOE to customize your automation From emails will:
Improve overall automation email usage as enterprise spam filters won’t potentially block emails from ‘noreply@appsheet.com’.
Reduces the risk of spam proliferation within an enterprise.
Things to note:
The public preview is an initial offering of this feature which includes the ability to select an account to send automation emails from accounts that match your org’s owned domains.
We plan to roll out successive enhancements along the way towards GA.
These include:
Support for Gmail aliases and Display names.
And more…
Support for non-Workspace support will come in phase 2, which is expected H1 2027.
For more information on how to use BYOE please see the documentation.
Thanks for your interest in this important feature as we continue to enhance it further!
@cschalk_ws Huge thanks to the product team for the new BYOE feature for Workspace users! I do believe this will go a long way toward stabilizing our apps. Being able to ensure that automated AppSheet emails are reliably received and not blocked on the recipient’s end is a massive improvement.
I’m excited and look forward too allowing non-workspace domains. This helps a lot for clients that we build apps for, they love appsheet, however already have their own business domains set up outside of Google.
Thanks AppSheet product teams for finally making this feature possible. This will surely improve our overall app experience. Looking forward to BYOE roll out.
Thank you for bringing us a new feature. I quickly tested and identified the critical issue with us. For the email body, we placed the Japanese characters, but all of those texts were garbled when we received the actual email. Could you please add the function to cope with the other languages? I presume currently only English font is supported. Thank you.
When sending with this BYOE solution, text with ANSI Alt code like ALT+0149 (Bullet Point Symbol), it seems to have stripped it out and replaced it with •
Standard UTF-8 characters (like the • bullet point) are rendering as Mojibake (e.g., •) in receiving email clients. This issue does not occur when sending the exact same template through AppSheet’s default mail servers.
This will affect multi-byte languages like Japanese, Chinese or Arabic and the same fix below should solve it.. @Koichi_Tsuji
The raw message payload being handed off to the Gmail API appears to be missing the explicit UTF-8 character set declaration, causing receiving email clients to fallback to Windows-1252/ISO-8859-1.
Try update the BYOE Gmail API constructor to ensure the MIME headers explicitly declare the character set (e.g., Content-Type: text/html; charset=UTF-8) or ensure the payload is properly Base64 encoded prior to the users.messages.send API handoff.
Die Nachricht wurde nicht zugestellt
Bei der Zustellung Ihrer Nachricht an […] ist ein Problem aufgetreten. Bitte lesen Sie die technischen Details weiter unten.
Die Antwort vom Remoteserver ist:
550 5.7.23 spf check failed
@Fabian_Weller, this is likely something you’ll need to address yourself. SPF is the Sender Policy Framework, an internet anti-spam measure. It works with DNS to identify who may legitimately send email from your domain. SPF must identify whomever is sending the email as a legitimate sender for your domain.
Thank you @Steve . So this is about an E-Mail we sent to a customer on a regular basis. With noreply@appsheet.com it always worked. When I enter our own Mail Address I get this error message.
When your domain’s DNS publishes an SPF record, it’s telling the world who may legitimately claim to be sending email for your domain.
When AppSheet was sending the email, the email appeared to be coming from appsheet.com, so your own domain’s SPF record wasn’t consulted.
But, with BYOE, the email appears to be coming from your domain, so the SPF record matters.
When recipients see the email is from your domain, they consult your domain’s SPF record.
If the email doesn’t match what SPF says, the recipient rejects the email.
I don’t know how AppSheet’s BOYE setup works. I would imagine AppSheet provides the message to a server you’ve identified, and your server is then responsible for sending the message to the recipients. It’s that server, not AppSheet’s or Google’s, that must be whitelisted in your domain’s SPF record.
Based on @cschalk_ws’ reply, the short answer seems to be: yes, quotas and limits still apply, but Google may change them in the future. But that response probably doesn’t actually paint a complete picture.
I don’t know the specifics of how BYOE works, but if AppSheet/Google is effectively giving your mail server the message, as I suspect [EDIT: my assumption appears to be wrong, so is what follows], and your mail server then sends it to the intended recipients, AppSheet/Google cannot apply quotas or limits to the messages your own mail server sends. This is one of the major value propositions of BYOE: freedom from AppSheet/Google email quotas and limits. AppSheet/Google quotas and limits remain in effect for the process strictly before the message is passed to your BYOE mail server, as best as I can tell.
(and @Steve ) We have quotas (checked during automation execution) on email sends that currently apply to BYOE as well as noreply@appsheet.com. We believe we can relax or remove them for BYOE in the near future - they were in place to protect our noreply@appsheet.com integration - but we wanted to be cautious in case there are any unexpected consequences for our service from adding large amounts of calls to the Gmail API.
@Trevor_Ryland, could you provide an overview of how BYOE is implemented, so I can address is accurately in the community?
What does the app creator “bring” for BYOE? Does Google convey the automation-generated email to the customer’s server for distribution, or does Google adopt the identity of the customer and distribute the message directly?
I have an ISP and SaaS-hosting background, as well as being a long-time AppSheet enthusiast.
