Why Domain/email Tab Does NOT SUPPORT SendGrid API Key when I authorized by SUBdomain?

hobum91 · 2025-03-06T13:30:47.675Z

Problem :
I Authenticated my subdomain on SendGrid & my bubble app has the subdomain.
BUT
When I want to verify SendGrid Key at the Domain/email tab,
I see the weired error. Bubble do not recognize my subdomain. just recognizing maindomain (which I never asked)

hobum91 · 2025-03-06T13:51:09.272Z

AND WHAT MAKES ME ANGRY is,
When I send email by BUBBLE API CONNECTOR + Sendgrid cURL API,

IT WORKS PERFECTLY.

johnny · 2025-03-06T16:44:13.758Z

That’s because in Sendgrid, you probably inputted your root domain, instead of subdomain. I think if you verify your whole domain in Sendgrid, then you’ll lose that error

hobum91 · 2025-03-14T21:33:43.607Z

I understand.
But I’m using my root domain as gmail so that I can not use it in Sendgrid. Because If I verify sendgrid with root domain, I think my gmail would not work.
That’s why this subdomain issue make me angry T_T

johnny · 2025-03-15T00:48:35.189Z

You don’t use your gmail, yahoo or any of those shared domains in Sendgrid. You should be using your own custom domain.

hobum91 · 2025-03-15T06:10:37.611Z

No, what I NEED is using that subdomain.

Main domain is using already, And I am developing additional service using subdomain.

So the problem is issue of subdomain authorization, especially in the page of bubble UI. Not using subdomain.

akamarski · 2025-03-15T11:53:32.840Z

You just allow sendgrid to send emails on behalf of the domain, it has nothing to do with receiving emails in Gmail. The two can work together

hobum91 · 2025-03-15T15:17:04.308Z

No, It’s not.

When you do ‘Sender Authentication’ in the SendGrid Console, SendGrid ask you to add MX RECORD in DNS section of you domain.

This means you change your mail service.
Because, as far as I know, MX record is required only one for one domain. Otherwise, email does not know where it to be sent.

And If you change MX record without thinking, especially you’re using Gmail several years & that mail address is still officially used, your boss would call you in several hours…!

So It is much more reasonable using subdomain when you develop services without trouble.

Again, Trouble is ‘bubble doesn’t support subdomain validation of SendGrid key in the editor’. Even though It works perfectly when you use bubble API plugin. It should be fixed if bubble wants every no-coders can do SendGrid validation easily.

(SendGrid Page below)

sendgridMX1223×2562 434 KB

akamarski · 2025-03-15T18:42:06.253Z

Not all MX records are equal

To receive emails on a given domain, you need MX records that use @ as the host.

SendGrid is asking to ad an MX record for a subdomain for their own verification purposes. Probably if there’s some way to receive emails in SendGrid itself or some system email.

Your original MX records won’t stop working because they apply to a different host.

The point is: just go with the default sendgrid flow for the main domain. They know how to NOT fuck up

hobum91 · 2025-03-16T16:40:29.870Z

oh, what I meant was I has own custom domain and using google workspace with my custom domain.

so I can login gmail with my domain, not @gmail.com

hobum91 · 2025-03-16T16:48:27.299Z

Yeah, I think you’re misunderstanding my situation.

As I wrote, I’ve already got finished Sender Authentication of Sendgrid with my SUBdomain. I registered MXrecord of SUBdomain also. And it fully works when using bubble API plugin until now.

The problem is, Bubble does not verify my sendgrid key because I used subdomain to be authenticated in Sendgrid.

My root domain doesn’t need sendgrid and I don’t want to send email with my root domain. But bubble requires to authenticate root domain in sendgrid EVEN THOUGH I use subdomain.