✉ Automate Follow-Up of Email Leads a Week After

Problem Statement

Have you received an email/Gmail enquiry about your services, and you responded but there was no further replies from the user? This could result in lost sales.

Would it be nice if you could automate the sending of a reminder in the same Gmail thread a week later, to remind them that you are still awaiting their response?

Scenario

Scheduling

Run daily at time of your choice.

1. Trigger module

Find all emails between 8 and 7 days ago, in a specific folder/label (e.g.: Leads), that was sent by you.

Insert your email address in the “Sender” field.

2. See if there is a later response from the user

Find all emails sent by the recipient after the date in the original email sent by you.

Make sure “Continue the execution of the route even if the module returns no results” is YES, because we want to send the reminder if there are NO results.

3. Continue if there are no results

Just check if “date” does not exist.

If date exist means there are results - we do nothing.

4. Send an email to the user

  • Quotes original email
  • Keep in the same Gmail thread (using the references array)

Blueprint

follow-up-a week-later-on-email-non-replies.json (24.5 KB)

3 Likes

You will need to set up a Google Restricted connection to your email.

For more information, see

How to create an OAuth app in GCP: https://www.make.com/en/help/tutorials/calling-google-apis-via-the--http-make-a-oauth-2-0-request--module ← FOLLOW THIS

1. Enable the Gmail API

Direct Link: Google Cloud console

Screenshot_2024-02-16_130236

2. Insert all the known Google Redirect URIs for your app

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

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.

https://www.make.com/oauth/cb/oauth2
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-analytics-4
https://www.integromat.com/oauth/cb/oauth2
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-analytics-4

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.

3. Publish your GCP OAuth2 app

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

You might need to set your OAuth application to “Production”, otherwise the credentials expire very frequently. For more information, see Gmail/Google Drive verification issues (error 400): how to solve

1. To do this, go to menu item “OAuth consent screen”

or click here https://console.cloud.google.com/apis/credentials/consent

2. Then click the button below if the Publishing status is not “In production”

2 Likes