I want to customize and setup dinamically a signature in a bunch of Google Workspace users
I look around a way to programmatically change from a module inside a scenario the signature of an email in gmail.
I find out that there is not a currently module that do that but I figue out that I can make an HTTP Make a OAuth 2.0 call to the right API. Following this guide I should make the right connection to with the right oAuth credentials.
Now I have to tell the module the right parameter for update this signature. I watch this video:
That shoudl explain the right wayt to do that in Python but I think that I can do also with Make even if I pass the right data to the module.
I try to start the module and it gives me an âOK - Successâ but, after when I go to the gmail nothing change.
Can someone help me to figure out how to solve this issue?
Please share screenshots of relevant module fields and filters in question? It would really help other community members to see what youâre looking at.
You can upload images here using the Upload icon in the text editor:
2. Scenario blueprint
Please export the scenario blueprint file to allow others to view the mappings and settings. At the bottom of the scenario editor, you can click on the three dots to find the Export Blueprint menu item.
(Note: Exporting your scenario will not include private information or keys to your connections)
Hello @samliew,
thanks for your reply. The scenario is very simple because I donât put in this time all the logic that I want to achieve. I think âBefore I figure out about the connection to the Gmail Api and after I construct all the scenario and the logic for changing the signatureâ.
Anyway you find the sceenshot attached to this message such as the blueprint.json
Here are all the known redirect URIs you need for your Google Cloud Console OAuth app. If you set these up, you can reuse the same GCP app for other Google apps and modules on Make.
Once youâve set these up, you can use/reuse the same Make connection for all the supported Google apps & modules on Make - youâll only have to enable the respective APIs for your custom app in Google Cloud.
You can find the Client ID and Client Secret in the OAuth2 app you created in GCP, on the right-hand side of where you inserted the 8 callback URLs in step 2:
Hello @samliew,
thanks for your kindly reply. Firstly I want to change the signature (also for alias) and not get it, but also get it could be usefulâŚso anyway thanks.
I try to figure it out and I think that I setup everything correct. Attached hereto some screenshot
Scopes:
As a workspace administrator, you could try using existing tools to manage your organization.
Here is a free tool for Google Admins that allows you to update user signatures on the organization, OU, group, or individual level: Signature Manager for Gmail
As for the connection set-up in Make, you need to sign in with the main Google Workspace service account and not one of the sub-accounts, otherwise you can only amend your own signature.
Hello @samliew,
thanks for your reply. I canât use the external tools you suggested because some features that I need is missing. For example (but there are more) I have to update the signature for each sendas email for each users, also the text inside signature comes from a complex scenario inside Make. So call the correct API and make it working is crucial in my case.
Anyway follow this link and this link and your previous answers I figure out how to use API for my userâŚso THANK YOU
Please note that one of the two linked guide has screen and information expired and it could be a great thing to update it with latest screen and data (such as the redirect urls)
Now Iâm in a little (very little) step to solve my issue. In the latest post you are right:
As for the connection set-up in Make, you need to sign in with the main Google Workspace service account and not one of the sub-accounts.
So I create a serivce account inside app and grant it access to all the Workspace domain. I put it as propertary and I give to it the right scope. When I try to use in the connection (taking the right client id and password) I have this error back (I translate from Italian so some words could be different but the sense should remain the same):
You canât access to this app because itâs not compliance with Google OAuth 2.0.
Thinking of it there is no place where I create or editing the service account where I can put the alla authorized redirect so it could be for this reason that it doesnât work. Or perhaps something otherâŚcan you help me to make this little step forward?
Here are all the known redirect URIs you need for your Google Cloud Console OAuth app. If you set these up, you can reuse the same GCP app for other Google apps and modules on Make.
Once youâve set these up, you can use/reuse the same Make connection for all the supported Google apps & modules on Make - youâll only have to enable the respective APIs for your custom app in Google Cloud.
You can find the Client ID and Client Secret in the OAuth2 app you created in GCP, on the right-hand side of where you inserted the 8 callback URLs in step 2:
Hello @samliew
thanks for your reply. Unfortunately something doesnât work. In your answer you assume that I use a user account and not a service account as I do.
The problem is when I setup a service account and the fact I donât have a space where to put the Authrorized redirect URIs