Start hereAutomationsGuidesYour planThe stackAboutWeekly email▶ YouTubeTelegram

“A task a week overdue, and nobody noticed.”

A task overdue by 3 days → an alert to the consultant, not the client

By · Updated · Get guides by email

Now she knows before the client does.

Overdue tasks do not disappear, they sink. Once a day, every open task 3 days late surfaces in one Telegram message to its owner, before the client asks.

MakeGoogle SheetsTelegram3 operations / run✓ Imported successfully into our Make account

Get the ready-to-import blueprint by email

Yes — email me BuilderStack's weekly issue: one new Make automation or guide a week, from O.S. Maintenance Buildings Ltd (Israel). It may include paid links. Unsubscribe anytime. Optional. We use your address only to send this email; it is stored by Brevo (EU) until you unsubscribe. You can access or delete it at any time — see the privacy policy.

We use your address only to email you this file. Without the box ticked, that is the only email you get, and the address is deleted after 30 days. Privacy policy.

The full build is on this page, free, no email needed.

▶ Watch the 30-second video

Video cover: OVERDUE ALERT

Short answer

Overdue tasks do not disappear, they sink. Once a day, every open task 3 days late surfaces in one Telegram message to its owner, before the client asks.

Tools
Make, Google Sheets, Telegram
Cost to run
3 Make credits (operations) per run

The problem

The task log looks tidy, but between the rows sit tasks a week past due that nobody touched. They surface when the client calls. By then it is not a delay, it is a trust problem.

What happens when it runs

  1. Schedule: every day 08:30
  2. Read the task log: status open, due more than 3 days ago
  3. Aggregate into one list: task · client · days overdue
  4. A Telegram message to the consultant (or the team group) — not to the client

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 →

Before you start

Three things to have ready before importing, or Make will ask and you will have to leave halfway:

  • The task log spreadsheet id
  • Days overdue threshold (default 3)
  • 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.

  • Task log · task | client | due | status (Sent with the blueprint by email)

How to import (2 minutes)

  1. In Make: Scenarios → Create a new scenario
  2. At the bottom, the three dots (⋯) → Import Blueprint → choose the file you downloaded
  3. Click every module with an exclamation mark: choose your connection (Google, Telegram) — Make creates one in a click if you have none
  4. Replace every value in double curly braces ({{…}}) with your own from the list above
  5. Run once with a test row in the sheet. Only when it passes — Schedule and ON

New to Make? Start here →

No Make account yet?The file imports only into Make. Signing up through the link gives you one month of Core free, and us a commission. The file works without the link.
Sign up for Make →paid link · we earn a commissionPaid 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.

The video

Watch on YouTube → · Subscribe to BuilderStack · Telegram channel

Read more

What does not work in it

  • An overdue task appears every morning until it is closed. That is on purpose — but after a week the message becomes noise. If the same 10 tasks repeat, the problem is not the alert.
  • The alert does not distinguish "a day late" from "a month late" beyond the number. Tasks that are truly stuck need a decision, not a reminder.

Questions

What does not work in "A task overdue by 3 days → an alert to the consultant, not the client"?

An overdue task appears every morning until it is closed. That is on purpose — but after a week the message becomes noise. If the same 10 tasks repeat, the problem is not the alert. The alert does not distinguish "a day late" from "a month late" beyond the number. Tasks that are truly stuck need a decision, not a reminder.

What do I have to fill in after importing the blueprint?

The task log spreadsheet id; Days overdue threshold (default 3); Chat ID.

Which tools does it use, and what does a run cost?

Make, Google Sheets, Telegram. Each run uses 3 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.

Next step

All automations →
EMAIL → TASK

Labelled email → task in the log → reminder

Tag an email with one label and it becomes a task with a due date and an alert. One screen for everything that is waiting.

MakeGmailGoogle SheetsTelegram3 ops/run✓ imported in Make
MORNING DIGEST

Every morning: what is due today → one message

At seven in the morning one Telegram message arrives with every task due today, by client. One screen to open the day, instead of five.

MakeGoogle SheetsTelegram3 ops/run✓ imported in Make
ERROR ALERT

A Make scenario fails → a row in the error log and a Telegram alert in seconds

Every failing scenario posts to one webhook: the failure is logged in an errors sheet and sent to you on Telegram with the error and the scenario link.

MakeGoogle SheetsTelegram3 ops/run✓ imported in Make

What will it cost? Make cost calculator →Build your automation plan →