Google apps script to send two custom HTML messages to anyone automatically.

JavaScript 6.19% HTML 93.81%

google-sheet google-apps-script automation automated-email html-templates collaborate ghdesktop github github-campus-experts learn

google-apps-script-send-custom-emails's Introduction

Google Apps Script Send Custom Emails

Using Google apps script on a google sheet to send two custom html messages to anyone automatically.

HTML Templates

This repo contains two html templates you can change whatever you want in them but to ease the process I created a JSON object Named changes which contains what you need to change per email.

Welcome Email
Feedback Email

Steps

Step 1

Open Google Drive
Create a new Google Sheet
Name it whatever you want

Step 2

Inside your spreadsheet
Add two columns Name, Email
Add your first name and email to try this script
Open the Script editor from the navigation menu
Tools -> Script editor

Step 3

Inside your Script editor
Replace all the code in Code.gs with the code in Code.gs
Save the Script
Name it whatever you want

Step 4

Inside your Script editor
Create two HTML files from File -> New -> HTML file
Name the first one Welcome-Email
Name the second one Feedback-Email
Replace all the code in Welcome-Email.html with the code in Weclome-Email.html
Replace all the code in Feedback-Email.html with the code in Feedback-Email.html
Save both files

Step 5

Inside your Script editor
Go to Code.gs
Adjust your range "A2:B2"
Write your chapter's Name
Write the number of the event
Write the day of the event
Write the time of the event
Place your event's link
Place your chapter's Website link
Write the Powered by phrase
Change the Subject of the Email to be sent
Save the file

Step 6

Inside your Script editor
Choose the Function you want to run
Press Play button
Authinticate it and you are ready to go
Check your email to find the output of what you have just done

Each time you only need to add the emails and names to your spreadsheet then repeat Step 5, Step 6.

Learning

This repository contains a LEARN.md which users can learn and understand how the project works.

Through this, users can even potentially move on to contributing and improving the project.

Contribution

How to contribute to the project?

While contributing, it must be necessary that each contributor keeps in mind the Code Of Conduct.

This repository is open for everyone to contribute and is maintained by John Aziz.

google-apps-script-send-custom-emails's People

Contributors

Stargazers

Watchers

Forkers

alhassanessawy mou514 lnfran85 kureharyosuke

google-apps-script-send-custom-emails's Issues

Community Exchange Introduction/Tracking

👋 Hi @john0isaac,

I am your GitHub mentor for the GitHub Education, Community Exchange (CX) project. I'll be collaborating with you on preparing your repo for CX.

You mentioned in your submission that you wanted to submit a Learn + Collaborate repo. This means that you would like to teach students, step by step, how to build this project as well as invite other students to collaborate and add features to this repo. I will generate issues, which will provide guidance on how to prepare your repo for a Learn + Collaborate CX submission on June 1, 2022.

This issue will serve as a tracking issue to track all issues related to CX. I recommend creating a new branch for every issue and opening a pull request to track changes so we can effectively collaborate with each other and merge changes when you and I feel like those changes are ready to be merged on your primary branch.

If you have any questions or concerns, please feel free to leave a comment on this issue or any of the other issues that are generated.

I look forward to working with you

Issues

Convert it to a Chrome Add On

Is your feature request related to a problem? Please describe.
I want this automation to be converted to an add-on and posted on the Google Marketplace for everyone to use.

Add More HTML Templates

Is your feature request related to a problem? Please describe.
We need to add more HTML templates to make it more applicable for any user, not just the two specific HTML files.

Describe the solution you'd like
Follow the learn.MD on how to create an HTML template email and add it to the repository.

Describe alternatives you've considered
I considered getting templates from the internet but they might be licensed so we need to create our own templates.

Add issues

As the maintainer of a Collaborate repo, keeping Issues up-to-date will help the student community understand what they can do to contribute. Issues should vary by the easy (update documentation) to the difficult (add a new feature). The more involved you are, the more opportunities there are to collaborate.

Recommendations:

Add issues of varying difficulty to the repo often.
Generate issues even if you plan on solving them, so the repository appears as active.
Contribute/commit often to the repo so it does not go stale.

In order to submit your project into CX you will need at least one issue, but we recommend more so other students have an idea on where to start.

Add LEARN.md

Learn repos should have a LEARN.md file to teach another student how to build your project step by step. You can explain how to build your project with text, code snippets, images, or even short (5 minute) long video lessons. As the maintainer of a Learn repo, the LEARN.md file requires you to think critically about how to explain the building of your project and how to also make it engaging. We don't expect you to be an expert teacher, but we would like you to reflect on how difficult it was to get to your level of knowledge, and then provide friendly guidance to help other students to learn.

Add templates for issues

Issue templates are very helpful for a collaboration repo. When users identify a bug or want to add a new feature, you can provide templates so you can collect all the pertinent information you need to fix a bug or add a new feature.

We recommend creating a “Report Bug” and “Feature Request” issue template.

Some suggested prompts/questions you can add to a “Report Bug” template are:

Briefly describe the bug
What is the expected behavior?
Please provide step by step instructions on how to reproduce the bug

Some suggested prompts/questions you can add to a “Feature Request” issue template are:

Briefly describe your feature request
What problem is this feature trying to solve?
How do we know when the feature is complete?

Update README

Your README already has great content. I would suggest going into a little more detail on why this would be useful. Perhaps some real life examples to get other folks thinking, "oh I could use this."

I would also recommend adding:

How to contribute to your project
Explain to users that there is a LEARN.md
Mention your code of conduct

Add Code of Conduct

We recommend that every repo has a code of conduct. If you don’t feel comfortable creating your own Code of Conduct from scratch we highly recommend using one of the templates provided by GitHub. If you do use a template, please read through the template and ensure that you can and will abide by the Code of Conduct.

Please follow these instructions on how to add a Code of Conduct.

john0isaac / google-apps-script-send-custom-emails Goto Github PK