I see, some " were missing 
1 Like
Hello,
I have the same problem. Have you found a solution @fcastillosa.apps ? @ZeroqodeSupport any idea to personalize the senderās name. Even when I configure Sendinblue, I always have the email that appears in the senderās name.
Thx 
Hi @killianAB , it never worked out for me. I think that something is wrong with the plugin. However, I found another way to do what I wanted (that was sending a welcome message). I just followed what @lucie told me to do on this thread [New Plugin] Sendinblue Contacts - #15 by fcastillosa.apps and then I created a welcome message automation in sendinblue. It is working beautifully and messages are being sent directly by sendinblueās order not through any API, so the email gets sent with the exact parameters that you set it up in sendinblue (including the senders name).
1 Like
Thank you @pachocastillosr
Thatās the way it works. I used" the automation part of Sendinblue and itās perfect!
Thanks again 
1 Like
Apologies for providing not helpful suggestions regarding the sender name question. The actual sender name can be configured on the Sendinblue side, as I have said.
When you are creating a new template in Sendinble, there are 2 fields āfrom Nameā and āfrom Emailā. They are containing the info on the currently created sender. You can add a new sender and verify it, f you want:
Still, Iām glad you have found the workable solution for you. 
Regards,
Zeroqode Team
Hi,
I have a problem with JSON, one email didnāt leave because of a " in the email.
Is there a workaround ?
The first " mark the JSON object āproduct nameā but the second are just what my user placed in the product title.
Thanks a lot !
Hi @marie, thanks for the question.
The " " marks used by the user to limit the product title are conflicting with the message body, which even if is transmitted through HTML, still comes through JSON format.
That would mean that use of the double " mark changes the JSON request itself.
To avoid the above-mentioned error, please advise your user to use the ' ' marks for limiting the product title.
Hope it helps.
Regards,
Zeroqoe Team
1 Like
Hi @ZeroqodeSupport ,
Have tried this like others users but nothing happens for the sender name. Keep appearing the email when sending with the plugin.
Did a test directly from my sending blue account and sender name appeared correctly.
Any way you could look this into detail and give a solution please?
If you use the Send Email action, there is a Sender Name field - Screenshot by Lightshot. It works with no issues on our site - Screenshot by Lightshot.
If you use the Send Email + File action (Screenshot by Lightshot), it works well too - Screenshot by Lightshot.
You need to insert a sender name into the body parameter into the Send Email + File and Send Email + Template actions the way I show you here:
I recommend using some JSON validator as it is more convenient to customize the JSON body parameters in there and validate them, than just typing into the ābodyā field. (this for example https://jsonlint.com)
Hope it helps.
Regards,
Zeroqode team
Can we use this plugin to send file attachments using base64 and without file url?
Hi @shu.teopengco, thanks for reaching out.
Sure thing you can. To do so, please follow the supporting documentation (namely p. 3. Send SMTP Mail + File)
Hope it helps.
Regards,
Zeroqode Support Team
Thank you!
1 Like
Hello bubblers and @ZeroqodeSupport Team!
Iām facing an issue and I canāt really figure out if itās on Bubbleās side (a bug or something like that) or the pluginās side.
I have list of documents which I want to send by e-mail (one specific at a time) to some people with an Endpoint for the Sendinblue SMTP plugin.
When I try to do it with a totally new doc (doc created by the user with name, text, etc) it works perfectly. But when I āduplicateā the contract (using a reusable element and an workflow to create a new doc with the information of the previous one), it just simply doesnāt trigger the Sendinblue endpoint (all the other Bubble actions work).
Iāve downloaded the CSV, compared all the values from the 2 objects and saw that the information are identical. Only the ācreate dateā, āmodify dateā, āunique idā, etc are different, but because they canāt be the same 
Can someone give a hand, please?
Hi @luiz1 , thanks for reaching out.
Allow us to check the reported issue and see for a possible solution.
We will come with feedback in a due course.
Regards,
Zeroqode Support Team
1 Like
Hi @luiz1, thanks for your patience.
Apologies, but on some examples it would be much easier for us to understand your user case. Would you kindly share the details of your setup and use case (screenshots)?
Also, please note that unfortunately, the current plugin functionality doesnāt allow sending emails to a list of users, only one by one (that is why first mail is sent and following are not). Sorry for the inconvenience.
Regards,
Zeroqode Support Team
Hi team, thanks for your quick reply!
Sure, you can see below the screenshots.
In regards to the list of users, I was aware of that. The endpoint was scheduled to work on a list to surpass this issue. Thanks anyway for the comment!
1 - This is the reusable element used to duplicate docsā¦
ā¦ and its workflow. As you can see, itās really simple.
2 - The reusable is used in a RG to, among other actions, to āduplicateā the doc (as text, it does not create a pdf).
When I create a doc from scratch without duplicating it, and call the API endpoint on a list (below), it works fine. But when I try to do the same thing with a duplicated doc, it just simply ignore the API call.
The process is the same, with the same values (exception of Unique ID, etc), but when and only when I duplicate the doc, it doesnāt work. The only variables that are NOT the same are the ones below. All the other ones are exactly the same.
Hope it helps!
In the meantime, I just took the āduplicateā option off 
Thanks a lot!
Dear @luiz1 , allow us to analyze provided information internally and come back with a feedback asap.
Thanks for your patience.
Regards,
Zeroqode Support Team
1 Like
Hey guys!
I would like to ask a question.
Is there an easy way to send emails through Bubble using Amazon SES? Because it provides about 60,000 free emails per month for applications hosted on amazon. That is about 2,000 emails per day, in addition to charging $1 for every 10,000 additional emails. Iāve been trying to connect with Bubble for 3 days, but itās not that simple. My app requires about 17 emails per user for each full initial flow or about 15 transactional emails. If you know any way to implement this, it would be nice to know, even if it costs something.
Dear @luiz1, thanks for your patience.
The reported issue (sending a list of documents to some people) might be related to the restriction that has both Sendinblue and Bubble platform itself.
If during one minute on the same endpoint comes the same API request (with the same data), the Bubble platform ignores the second one (in order to avoid an accidental repeat of the API calls).
As a possible solution, please do the following:
- make sure your API allowance per minute is respecting the limit imposed by Sendinblue, see the link for reference: Limits
- check if the number of your API requests is less than 1000 requests/minute, see the link for reference (Rate limit): Reference | Bubble
- try to make an ordinary workflow that will send emails, instead of backend workflow.
Hi @imad30, thanks for the question.
A possible solution for your inquiry could be the setup of relevant API calls through the API Connector because as far as we know, there is no dedicated plugin for Amazon SES currently.
See the link for reference:
We canāt say it is the easy way, but it is a viable one. Kindly note that for successful setup a corresponding level of Bubble skills is required.
Hope it helps.
Regards,
Zeroqode Support Team
2 Likes
Hi,
Im having the exact same issue as @pachocastillosr The sender name is not appearing in the email.
Here is my configuration :
Bubble workflow :
Sendinblue email template configuration :
Sendinblue global sender parameters
Inbox result :
As you can see the sender_name has been setup everywhere to be āTrouver un rĆ©parateurā while the name being displayed in the inbox is ārideā which is the part before @ in the email (ride@trouver-un-reparateur.fr)
Thanks for your help,
Pierre