Email module not working in scenario

Questions
1

I’ve made a scenario that parses a CSV file and I want to send it as an email to myself, but none of the email modules work. Has anyone used any of the email modules in a scenario before?

image
image1601×941 55.3 KB

Thanks

2

Hello @Admir_Ljubovic ,

You have to create a client for your email module in Google cloud console

HERE ARE THE STEPS INVOLVED:

1. Check if you’ve enabled Gmail API

2. Go to Branding and input all necessary details, Add make.com as the authorized domains .

3. Go to Clients then create an oath client. Choose Web application then add a name for your app, then add :

As the authorized redirect URIs

4. Go to data access and add the following scopes:

-https://www.googleapis.com/auth/userinfo.email

https://www.googleapis.com/auth/userinfo.profile

After that click update.

5. Last but not the least, check the Audience section and add your email as

a test user.

3

Are you using a Google mail i.e Gmail or a professional mail?

4

I’m using my personal gmail, but I’d prefer to send the email to my work email which has a proprietary domain

6

Thank you very much!

7

Have you been able to solve the problem?

8

Have you tried using the Gmail “Send an Email” module?

Here’s how to set it up:

How to Connect and Use Google APIs in Make!

0. Prerequisites

1. Enable Google APIs

2. OAuth Client

Direct Link: https://console.cloud.google.com/apis/credentials

  • 2a. Create “OAuth client ID” Credentials

    455×206 15.2 KB

  • 2b. Insert all the Google Redirect URIs for your app

    302×200 7.32 KB

    Insert All Google Redirect URIs

    Here are some commonly-needed 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.

    https://www.make.com/oauth/cb/oauth2
https://www.make.com/oauth/cb/google
https://www.make.com/oauth/cb/google/
https://www.make.com/oauth/cb/google-custom
https://www.make.com/oauth/cb/google-restricted
https://www.make.com/oauth/cb/google-cloud-speech
https://www.make.com/oauth/cb/google-search-console
https://www.make.com/oauth/cb/google-analytics-4
https://www.make.com/oauth/cb/google-ads2
https://www.make.com/oauth/cb/google-ads2/
https://www.make.com/oauth/cb/youtube
https://www.make.com/oauth/cb/chrome

    Including These Google Redirect URIs

    You are also required to insert the legacy URLs below from the old Integromat system that not been migrated to Make yet (same as the above list, but replace “make” with “integromat”):

    https://www.integromat.com/oauth/cb/oauth2
https://www.integromat.com/oauth/cb/google
https://www.integromat.com/oauth/cb/google/
https://www.integromat.com/oauth/cb/google-custom
https://www.integromat.com/oauth/cb/google-restricted
https://www.integromat.com/oauth/cb/google-cloud-speech
https://www.integromat.com/oauth/cb/google-search-console
https://www.integromat.com/oauth/cb/google-analytics-4
https://www.integromat.com/oauth/cb/google-ads2
https://www.integromat.com/oauth/cb/google-ads2/
https://www.integromat.com/oauth/cb/youtube
https://www.integromat.com/oauth/cb/chrome

    Note 1: Due to inconsistencies in Make’s implementation of the connections, there are two separate entries where has one is google and another ending in a forward slash google/ - you might need one or the other, so we have to use both!

    Note 2: Once you’ve set these up, you can use/reuse the same Google OAuth App ID + Secret for all the supported Google connections and modules on Make - you’ll just have to enable the relevant Google APIs!

3. OAuth consent screen

Direct Link: https://console.cloud.google.com/apis/credentials/consent/edit

  • 3a. Insert Two Authorised Domains

    • Insert make.com and integromat.com

    • Fill in other required fields

    • Click “Save and Continue”.

      390×301 14.1 KB

  • 3b. Add All Scopes

    • Click “Add or Remove Scopes”

    • Select 100 “Rows per page”, for each page, check all the rows, OR

    • Manually type in the scopes you need

    • Click “Update” at the bottom

    1476×1156 182 KB

  • 3c. Step through and go to dashboard

    At the last step/page, click “BACK TO DASHBOARD” instead of “Prepare for Verification”

  • 3d. Publish your GCP OAuth2 app

    You will need to set your OAuth application to “Production”, otherwise the credentials expire very frequently.

    • To do this, go back to “OAuth consent screen”

    • Then click the “PUBLISH APP” button

    • Then click the “CONFIRM” button

    479×206 9.36 KB

4. Create New Connection (HTTP, or respective Google module)

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 callback URLs in step 2:

471×488 18.6 KB

  • 4a. Specific Google module (Sheets, Docs, Drive, Gmail, etc.)

    Insert the GCP app client ID and secret here BEFORE clicking “Sign in”

    (Gmail example)

    525×643 65.1 KB

    OR,

  • 4b. HTTP OAuth 2.0 Request module

    708×401 44.2 KB

    You need a “Authorize Parameters” key of redirect_uri with the above Make OAuth2 callback URL.

    597×904 61.2 KB

Related Topics:

Hope this helps! Let me know if there are any further questions or issues.

— @samliew

9

I’ve done all of the steps, but I’m having problems with cenolis.com not being verified

10

In the audience section I can’t add an email. I’d like to add my own email so that I can use the email module.

11

That’s incorrect spelling, try re-copying the authorised URIs again. You might also be missing a step or two from the above.

If you require further assistance, please provide screenshots of what you have done.