My send email does not work today. Bubblebot says it could be that my free sendgrid account has expired but I don’t know how to tell if my send email uses that. How do I tell?
![]()
My send email does not work today. Bubblebot says it could be that my free sendgrid account has expired but I don’t know how to tell if my send email uses that. How do I tell?
![]()
If you’re using the native “Send Email” action in your workflows, that goes through Bubble’s own email service — not a separate SendGrid account you’d manage.
Check Settings > Languages tab — if you haven’t set up a custom email provider there, you’re on Bubble’s default. The issue might be related to the recent platform outage (Oct 26). Try testing again now — if it still fails, check your Server Logs for any error details on the email action.
That’s what I was wondering, if it’s the bubble fault or my own. I know my postmark email works.
I don’t see any email provider in my Language tab.
If Postmark is already working for you, I’d skip the native Send Email action entirely and route everything through Postmark. Use their plugin or set it up via the API Connector. The native action depends on Bubble’s built-in email service which can be unreliable. With Postmark you get better deliverability, delivery tracking, and you won’t run into these random outages.
Yeah the Postmark API needs file attachments as base64-encoded content, which the native Send Email action handles automatically but Postmark’s plugin doesn’t.
Easiest fix: instead of attaching the file directly, include a download link in your email body. Something like This User's File URL as a clickable link. The recipient clicks to download — works reliably and avoids the base64 hassle entirely.
If you absolutely need a true attachment, you’d have to set up Postmark via the API Connector using their /email endpoint and pass the file as base64 in the Attachments array. That’s doable but more involved.
That log showing “sent” but not arriving is likely the platform outage still causing issues — Bubble’s email service has been flaky since Oct 26.
For the Postmark attachment setup, it’s not as bad as it looks. You’d use the API Connector with their /email endpoint and pass the file content as base64 in the Attachments array. Happy to walk you through it if you get stuck — shoot me a message.
To quickly tell whose fault it is: open Logs > Server logs and filter by the Send Email action around the time it failed. If there’s no error there, the email left Bubble and the problem is delivery (check spam, and test to a Gmail and a non-Gmail address). Also note that native emails go from a shared sender, so setting your own Reply-To/sender name helps a bit. Since Postmark already works for you, the base64 Attachments array via the API Connector is a clean long-term fix.
Hi Spark,
Now that bubble is fully operational I verified the native send email function still does not work. It’s definitely not a delivery problem as this has worked fine up until now.
The question remaining is do I need to activate my sendgrid account? I’m waiting for bubble support to answer that question.
Thanks for your help!
Hi Douglas,
Now that bubble is fully operational I verified the native send email function still does not work. It’s definitely not a delivery problem as this has worked fine up until now.
The question remaining is do I need to activate my personal sendgrid account? I’m waiting for bubble support to answer that question.
So yes, it looks like I need to find a long-term solution. Is that something you can easily show me how to do easily?
Thanks!
Thanks for confirming and for checking again, 1theritzy. That rules out the outage as the cause, so the SendGrid-account question is the key one for Bubble support. If they need diagnostics, share the failing action’s server-log entry and timestamp (redacting recipient details) and ask which provider the native action is routed through. Once they confirm whether SendGrid must be active, you can choose between restoring the native attachment flow and finishing the Postmark API Connector attachment setup. Hope support clarifies it.