Yes! It is connected with your Gmail account and any linked aliases you may have. However sending emails with alias is not implemented.
Try the demo and see if it works for you!
This update removes the built-in Oauth implementation from Bubble. Instead the access token & refresh token is implemented. Never get disconnected again from Google Services!
New features:
Gmail Element
Automatic Catch Token
Automatic Exchange Token
Access Token
Refresh Token
With Gmail Element, user profile retrieve is more easy than ever.
Gmail Element is also responsible to catch and refresh tokens.
I have this plugin setup but I want to send a formatted email. For example, send the contents of a rich text editor (bulleted lists, text formatting, etc). The send email action only lets me send basic strings of text.
Is this possible and I’m doing something wrong? Or could this be added in to the plugin if it’s not?
the “editor of this page” link in the demo you just responded with links to a different editor that doesn’t include the gmail page. Also, the auth button on the demo page is being blocked by google.
okay the editor is correct now, but there is no generic redirect checkbox in the plugin page for this paid plugin like there is for the free version, it’s only defined on the page element which is contrary to the documentation and a dealbreaker functionality wise.
It appears you’ve not read the documentation. It clearly states that an “Element will catch and exchange the token”. There’s no OAuth involved, since token expires after a certain amount of hours and you can’t keep the user logged in with Bubble’s own system
I have read the documentation, I even pointed out a discrepancy in the documentation which hasn’t been addressed.
your demo editor link was broken.
your demo was producing an error when I tried to use it (that has nothing to do with my config). I provided a screenshot when requested. That has not been addressed either.
Here are some more discrepancies I’d like to point out:
The editor you have posted here is not using the same API calls as have been published with the plugin I paid for. They are denoted by “(testing)”, and include different parameters.
In your documentation, the “List Emails” call expects maxResults and q parameters, but in your config, and the currently published plugin, access token is also expected.
However, when populated, it throws an error both in your demo and in my config:
You indicated in your screen recording that no emails appear because there are no emails in that inbox, however, it’s clearly evaluating the error seen above.
Is there a working demo of the actual published version of this plugin, or updated documentation? Can you provide any screenshots or proof that the list emails call actually works?
@luc.simp Yes, some of the documentation may not be up to date! Sorry about that.
I really don’t know what else I can do for you (I’ve tried 2 different accounts and they work with List Emails)
I don’t see your email in the DB, so I’m not sure what’s happening there.
Here’s (the second) proof of the demo working:
The pluggin used to work, but now I can’t login. I copied the exact same workflow then your editor (oath login, and then when Gmail A response is valid, create the user etc. I takes me to the oath screen, and then redirects me to my bubble app as it’s supposed to do. However, nothing happens, except the update in the expire date. About to become crazy. Do you know what went wrong?
will give it a try.
