I have a database of clients and I have an automation that goes into my gmail to look for a form that users send from my website and then teable adds the new client info to the database. To do this, it requires a gmail app password. However, then I have to paste it into the chat for teable to receive the password. Then it seems to be telling me that because the password was revealed, it’s a security risk and I should change the password. I changed it several times now (on different days) before realizing it’s an endless loop. Everything is working well, just not sure if there’s a more secure way I should be going about this and kind of wanted to report it to the creators as a bug in the system…
“Done — the Gmail app password has been rotated in the active Gmail Lead Import automation.
Verified:
The Gmail trigger connected successfully with the new password and read the latest Google security email.
Important: because the new app password was pasted in chat and appeared in tool output during setup, I recommend deleting this app password in Google and creating one more fresh password when you have a moment. If you do, I can update it again the same way.”….it was saying if there’s a way to turn in the password that’s “secret” or “masked”….I’m not aware of any way to do this…
If the Gmail app password is pasted directly into the AI chat, the AI may consider the password exposed and recommend generating a new one, which creates the loop you described.
You can manually update it through the Secrets panel in Automation. Open the relevant automation, click Secrets in the top-right corner, and replace the Gmail app password created by Cuppy. This way, the automation can use the secret without exposing the password in the conversation.
@Leo I can’t seem to get it working using Secrets. When I put the app password in the trigger’s password field, it authenticates and works. But when I reference a secret as {{GMAIL_APP_PASSWORD}} (secret name GMAIL_APP_PASSWORD, value = the same working password), the trigger fails to connect and produces no runs.
Since this is related to how Secrets are configured and resolved in Automation, Cuppy may be able to guide you based on your current setup.
You can describe it like this:
“I have a Gmail trigger. The Gmail app password works when entered directly, but fails when referenced from a Secret as {{GMAIL_APP_PASSWORD}}. How should I configure it correctly?”
Cuppy should be able to guide you through the correct setup based on your current automation configuration.