Automations → Every Sunday: leads by source → one message with the change from last week
Every Sunday: leads by source → one message with the change from last week
Website, Facebook, referral: how many leads each source brought this week, beside last week's number. One Telegram message that says where the money is working.
The problem
The client pays for ads and asks "is it working?". The answer sits in the leads sheet, but nobody counts by source every week. So budget decisions are made on a feeling.
What happens when it runs
- Schedule: every Sunday 08:00
- Read the leads from the last 7 days and the 7 days before
- Count by the source column: website, facebook, referral
- A Telegram message: each source, this week against last week, and the total
The tools inside
- Make — the automation engine · Sign up (one month of Core free) →affiliate link
- Google Sheets — log and lists
- Telegram — alerts
Before you start
Three things to have ready before importing, or Make will ask and you will have to leave halfway:
- The leads spreadsheet id
- The source names exactly as they appear in the sheet
- 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.
- Leads log ·
timestamp | name | phone | email | sourceDownload ↓
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
The video
Watch on YouTube → · Subscribe to BuilderStack · Telegram channel
What does not work in it
- The count is only as accurate as the source column. "FB", "Facebook" and "facebook ads" are three different sources — lock the column to a fixed list (data validation) before trusting the numbers.
- A lead with no source counts in the total and in no row. If the total is well above the sum of the rows, that is the sign.
- One week is noise. 3 leads against 5 is not a trend; a budget decision needs 4–6 weeks.
Affiliate 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.
More automations
All automations →
LEAD ALERTLead comes in → logged → alert. No hands.
A form on the client site sends a lead; it is logged and an alert reaches Telegram in seconds. The first automation every consultant sets up.
DUPLICATE CHECKReturning lead → recognised → "second contact", not "new lead"
Before a lead is logged, the automation checks whether the phone is already in the log. If it is — the alert says "came back", and sales knows this is a second conversation.
MISSING INFOForm arrives incomplete → an email asking for exactly what is missing
A lead without a phone, an order without an address: instead of someone chasing, one email lists the missing fields. The lead is logged either way, marked "incomplete".