No I’m talking about the fields in the request.
But don’t you think this method will skep errors
First i connected the Sendgrid in Bubble API connecter successfully including your directions to remove ( : ) and set as empty.
Then i need to connect the key to place bubble email setting and this is what i am getting.
When you will enter the sendgrid api key, if I remember correctly, you will also need to enter Sender email address (this field should show after you entered your API key). I think Bubble will set it as default to admin@yourdomain.com but I’m not sure.
But why do you want to set your sendgrid key there is you use API Connector?
@Jici There is no another field to set the email, i configured it before successfully and it’s just by connecting the API
If both Postman and Bubble connector working, why it’s failing to connect in bubble email setting!
Regularly I use send email action of bubble and I need to change bubble email settings to replace their bubble.email.
It’s like a requirement.
Exactly, now the sender name is Optional to name it anything
I tried to type in the email verified in Sendgrid and still not woking.
what did you set in sender name?
Sender
Sender? what you should have is desk@for(… i don’t know the rest of your domain)
I tried to type in the email and it’s not working
The same response
And what did you set in the api key? Just the key or you added the Bearer (you shouldn’t have the bearer. Just the key).
If this continue to give you an error, you should contact Bubble support.
I think in the past I see an issue with sending the key if you don’t have an admin@domain.com set in your sendgrid account first (and after you can switch to another sender name). So maybe it’s related to this issue.
I set the API key without Bearer, in the past i used other email with Sendgrid without admin starting with Support@ and it worked without any issues.
I don’t think i have to connect bubble support
I am sure that there is something missing here
I cannot help you more on that. In most case I set the whole domain in sendgrid instead of one user. verified in Sendgrid. But actually, the issue doesn’t seem to be related to your API Key. Really just who is able to send the email. Maybe that if you don’t have any verified sender in Sendgrid, the validation in Bubble is easier. But now that you have it set, it may create issue.
Ok, you helped me out a lot
Thank you
I will try to solve the issue with Bubble support
1 Like
This topic was automatically closed after 70 days. New replies are no longer allowed.