“Picture a six thousand dollar support plan that ends on Friday, and nobody remembered the date.”
Contract ends in 30 days → renewal email to the client → alert to you
Now a renewal is a conversation a month early, not an apology.
Every morning Make checks the contracts sheet. A contract ending within 30 days gets one renewal email to the client, the row is stamped, you get an alert.
Get the ready-to-import blueprint by email
The full build is on this page, free, no email needed.

Short answer
Every morning Make checks the contracts sheet. A contract ending within 30 days gets one renewal email to the client, the row is stamped, you get an alert.
- Tools
- Make, Google Sheets, Gmail, Telegram
- Cost to run
- 4 Make credits (operations) per run
The problem
A retainer, a maintenance plan or a yearly licence ends on a date someone wrote down once. Nobody looks at that column until the client asks why the service stopped, or quietly does not renew. Thirty days of notice turns a lapse into a conversation.
What happens when it runs
- Every morning: search the contracts sheet for status "active", an end date in the next 30 days and an empty notice_sent
- For each: one short email to the client with the service and the end date, asking whether to renew
- Today's date goes into notice_sent, so the same contract never gets a second notice
- A Telegram message to you: which client, which service, which date
The tools inside
Disclosure: links marked "paid link" pay us a commission from the vendor if you sign up. Your price is unchanged, and every file here works without them. How we choose tools →
- Make — the automation engine · Sign up (one month of Core free) → paid link · we earn a commission
- Google Sheets — log and lists
- Gmail — email
- Telegram — alerts
Before you start
Three things to have ready before importing, or Make will ask and you will have to leave halfway:
- The contracts spreadsheet id
- Columns A–G: client, email, service, end_date (YYYY-MM-DD), status, notice_sent, notes
- Your name for the signature
- Chat ID
Sheet templates
The file maps columns by position. Start from exactly these headers, in this order — a column in the wrong place writes a phone number into the email column.
- Contracts sheet ·
client | email | service | end_date | status | notice_sent | notes(Sent with the blueprint by email)
How to import (2 minutes)
- In Make: Scenarios → Create a new scenario
- At the bottom, the three dots (⋯) → Import Blueprint → choose the file you downloaded
- Click every module with an exclamation mark: choose your connection (Google, Telegram) — Make creates one in a click if you have none
- Replace every value in double curly braces ({{…}}) with your own from the list above
- Run once with a test row in the sheet. Only when it passes — Schedule and ON
Read more
What does not work in it
- It sends one notice per contract. When the client renews, write the new end date, set status back to "active" and clear notice_sent, or next year's notice never goes out.
- A contract that already ends in less than 30 days gets its notice the first morning, so switching it on over an old sheet can send several emails at once. Check the list first.
- It does not renew anything and does not read the reply. The reply lands in your Gmail; the status in the sheet is yours to change.
Questions
What does not work in "Contract ends in 30 days → renewal email to the client → alert to you"?
It sends one notice per contract. When the client renews, write the new end date, set status back to "active" and clear notice_sent, or next year's notice never goes out. A contract that already ends in less than 30 days gets its notice the first morning, so switching it on over an old sheet can send several emails at once. Check the list first. It does not renew anything and does not read the reply. The reply lands in your Gmail; the status in the sheet is yours to change.
What do I have to fill in after importing the blueprint?
The contracts spreadsheet id; Columns A–G: client, email, service, end_date (YYYY-MM-DD), status, notice_sent, notes; Your name for the signature; Chat ID.
Which tools does it use, and what does a run cost?
Make, Google Sheets, Gmail, Telegram. Each run uses 4 Make credits (operations).
Is the blueprint free?
Yes. The ready-to-import file is sent free to the email address you enter; the newsletter is a separate box you can leave unticked. The full build is on this page without any email. The file contains no connections and none of our ids, and works whether or not you use the paid Make link on the page.
Build your automation plan →Four questions, three automations ranked for your business.
Paid link. If you sign up through it we earn a commission from Make; your price is the same, and the link gives you one month of Core free.


