Document expiry reminders in Google Sheets: work passes, licences, insurance, domains
Keep every expiry date in one Google Sheet and get a Telegram ping 60, 30 and 7 days before each. Work passes, licences, insurance, domains. Free, no code, about 90 minutes.
Published 3 Nov 2026 · Facts checked 3 Nov 2026
What you'll have by the end: one Google Sheet listing everything in your business that expires, and a Telegram message on your phone 60, 30 and 7 days before each date. Work Permit: Ah Kow expires on 15/03/2027. Owner: Siti. When the renewal's done, someone types the new date into the sheet and the pings stop by themselves. Next year's round starts on its own.
Every small business has a handful of dates that hurt when they slip past. A foreign worker's pass. The shop's insurance. The food licence. The domain your website and email run on. Nobody forgets these on purpose. They live in a drawer or in one person's head, and they come round once a year, which is exactly long enough to forget them.
Is this for you?
Build it if you've got more than about ten expiry dates across staff, licences, policies and subscriptions, and today they're tracked in a spreadsheet nobody opens, a desk calendar, or "Siti remembers". Clinics, F&B outlets, renovation firms and agencies with foreign staff all fit. A spreadsheet that turns red when a date gets close only helps when someone opens it. This build is for the list nobody opens.
Skip it if any of these is true, and do the other thing instead:
- You have fewer than about ten dates. Put each one in Google Calendar as an event on the expiry day and give it a couple of early alerts. Google's path is to click the event, then Edit event, then under Notifications click Add notification, then Save at the top. "You can change how often you want to get alerts in advance", so set them weeks out (Google). Twenty minutes, nothing to maintain.
- Your HR or payroll system already tracks pass expiry. Turn its alerts on. Native beats glued-on.
- Nobody will keep the sheet up to date. This is the catch, and no tool fixes it. The build reads dates. If a pass gets renewed and nobody changes the sheet, you'll be pinged about something that's done. If a new hire's pass never goes in, you'll hear nothing. Before you build, decide whose job the sheet is. One name.
- You want a full expiry-tracking app, with document uploads, sign-offs and an audit trail across several sites. That's what the paid tools are for. This build is the free version of the core job: a list, and a nudge.
Keeping the list in Excel at the moment? Copy the columns into a Google Sheet in Step 2. That's the whole migration.
Why Telegram rather than email? A reminder only works if someone reads it, and an email reminder lands in the same pile as the renewal notice you already missed. (I build AI agents for a living, and the proactive assistant I run on my own server delivers through Telegram too.) WhatsApp would be nicer for some teams, but the free WhatsApp Business app can't be driven by an automation like this; the app-versus-API split explains why.
If this is your first look at AI automation in Singapore, it's a gentle start. There's no AI in it at all. It's a daily schedule and a message.
Two things to know before you commit an hour and a half:
- You'll paste two short formulas, one into the sheet and one into Make. You don't need to understand them. You do need to copy them exactly.
- Once, you'll open a long web address in your browser and read a screenful of raw text to find one number. It looks alarming. It takes a few minutes and you never do it again.
Everything else is clicking and typing words into boxes. No code, no card.
What it costs
S$0 a month, and no credit card anywhere. Checked 3 November 2026. Free tiers change, so glance at the linked pages before you build.
| Part | Free tier | Card needed? |
|---|---|---|
| Google Sheets | Free with a personal Google account: "All Google accounts come with up to 15 GB of storage" (Google One) | No |
| Make (the wiring) | "If you are on the Free plan, you have 1000 credits per month" (Make pricing), and there's "No time limit on free plan" (Make) | No. Make's homepage says "No credit card required", and its beginner guide says the free tier "does not require a credit card, and is forever free" (Make) |
| Telegram bot | The Bot Platform "is free for both users and developers" (Telegram) | No |
The credit maths, which is why this stays free. Make bills in credits, and for ordinary apps "1 operation equals 1 credit" (Make). This build reads your whole sheet once a day, and "Search modules use 1 credit per run, even when they return multiple bundles" (Make). The filter that picks out today's reminders costs nothing: Make lists "Router modules and filters" among the modules that "don't use credits". Each Telegram ping is one more.
So it's about 31 credits a month for the daily read, plus one per ping. Forty tracked items, each pinged three times a year, adds about 10 a month. Call it 40 or so out of 1,000. (That sum is ours, built on the quoted rules.) You could track a few hundred items and barely notice.
If you ever outgrow it, it won't be because of this build. Make says its free plan includes "enough credits and active scenarios to build and run real automations" (Make). That's an allowance, not unlimited. If you already run other builds from this site, check the current number of active scenarios on its pricing page before you switch this one on. Paid plans are listed on the same page. Read the price in the billing mode you'd actually pay, because Make's own FAQ says "prices are cheaper with the annual payment in advance compared to monthly payments".
Before you start (about 10 minutes)
Open three things. No payment details anywhere.
- A Google account. Your normal Gmail is fine. It'll own the sheet.
- Telegram, on your phone, and ideally on a computer too for the one step where you copy a long number.
- A free Make account. Sign up at make.com. The sign-up page offers Sign up with Google or Sign up with your work email, and its button reads Sign up for free. If Make asks a few onboarding questions, answer whatever's true. None of it asks for a card.
Then the slow bit, which isn't the build: find your dates. Pass expiry dates, policy end dates from your insurance schedules, licence dates, the domain's renewal date from wherever you bought it. This can take longer than everything below. It's also the most useful hour in this whole exercise, because at the end of it you'll know what you've got.
Build it, step by step
Five steps. One and three are short. Two is the sheet. Four is the real work, and five is the clock.
Step 1 — Create the bot that will ping you (5 minutes)
A "bot" here is nothing clever. It's a Telegram account that can send you messages, and Make will hold its password.
In Telegram, open @BotFather. Make's Telegram guide links straight to it ("Go to https://telegram.me/BotFather") and then says: "To create a new bot type /newbot to the message box and press enter."
BotFather asks for a name and a username. The name can be anything; "Expiry Bot" is fine. The username has rules. It "must end in 'bot'", it's "5-32 characters long", and it "may only include Latin characters, numbers, and underscores" (Telegram). Something like sunshine_cafe_expiry_bot. If it's taken, add your initials and try again.
BotFather replies with a token, a long line that looks like 8123456789:AAF.... Telegram's warning is plain: "Keep your token secure and store it safely, it can be used by anyone to control your bot." Paste it into a note for the next hour.
Now search for your new bot's username in Telegram, open the chat, and send it any message. "hi" will do. Telegram is clear that "Bots can't start conversations with users" (Telegram), so this one message is what lets your bot reach you. It's also what Step 3 reads.
Already have a bot from the receipt playbook? Make a fresh one for this anyway. Step 3's lookup "will not work if an outgoing webhook is set up" (Telegram Bot API), and a bot that's already feeding a Make trigger may well have one. A new bot takes two minutes.
You'll know this worked when BotFather has given you a token and you've sent your bot one message.
Step 2 — Build the expiry sheet (20 minutes)
Open a new Google Sheet. At the bottom, rename the tab to Expiries. The exact spelling matters later.
Set the sheet to Singapore before you type a single date. Click File → Settings. Under "General", set the Locale and Time zone menus to Singapore, then click Save settings (Google). Google says the locale "changes the spreadsheet's default currency, date, and number formatting". Day-first versus month-first is exactly the mix-up that turns 3 April into 4 March without any error message. The check at the end of this step catches it if it happens anyway.
Put these five headers across row 1, one per cell:
| A1 | B1 | C1 | D1 | E1 |
|---|---|---|---|---|
Item | Expiry | Owner | Notes | Remind on |
Then fill in your list, one row per thing that expires:
| Item | Expiry | Owner | Notes |
|---|---|---|---|
| Work Permit: Ah Kow | 15/03/2027 | Siti | |
| Shop insurance policy | 30/06/2027 | Mei Ling | broker sends quote |
| Domain sunshinecafe.sg | 02/09/2027 | Marcus | auto-renew is off |
| Food shop licence | 31/01/2027 | Siti |
- Item should be specific enough that whoever reads the ping knows what to do. "Work Permit: Ah Kow", not "WP".
- Expiry is the date it actually expires. Type it the way you'd normally write a date.
- Owner is the one person who renews it.
- Notes is optional, a hint for future you. Keep FIN numbers, passport numbers and policy numbers out of it. Your data below explains why.
- Remind on stays empty. The formula fills it.
What belongs on the list? Anything with a date that costs you if it's missed. Work Permits, S Passes and Employment Passes. Business licences. Insurance policies. The domain your email depends on. The SSL certificate too, but only if your web host doesn't renew it automatically; many do, so ask yours before adding it. Then the odd ones: the lease, the van's road tax, the card your software subscriptions bill to.
Now the formula. Click E2 and paste this exactly:
=IF(B2="","",TEXT(B2-60,"yyyy-mm-dd")&" "&TEXT(B2-30,"yyyy-mm-dd")&" "&TEXT(B2-7,"yyyy-mm-dd"))
In English: if there's an expiry date, write out the three dates that fall 60, 30 and 7 days before it. TEXT is Google's function that "Converts a number into text according to a specified format". In the pattern, yyyy is "the year as four digits", dd is "the day of the month as two digits", and Google notes that for mm, "Month will be used unless this code is provided with hours or seconds" (Google). Those three dates are what Make will look for each morning.
Copy it down: click E2, copy, then select E3 down to E200 and paste. Rows without an expiry stay blank.
Notice the formula never looks at today's date. That's deliberate. It works out fixed dates from the expiry, so nothing depends on the sheet being open or recalculating. "Today" comes from Make, at the moment it runs.
The check that matters. For the Work Permit row above (expiry 15/03/2027), column E should read:
2027-01-14 2027-02-13 2027-03-08
Now look at your own rows. The last date in each should be exactly one week before the expiry you typed. If it's months out, the day and month got swapped: check the locale and retype the date. If column E shows an error instead of dates, the sheet didn't recognise what you typed as a date. Retype it.
You'll know this worked when you have an Expiries tab, five headers, your real rows, and three sensible dates in column E for every row with an expiry.
Step 3 — Find your Telegram chat ID (10 minutes)
Make needs to know which chat to send to, and Telegram identifies chats by a number, not a name. This is the fiddliest few minutes of the build, and the last thing in it that looks technical.
In a browser, go to this address, swapping in the token from Step 1:
https://api.telegram.org/bot8123456789:AAF.../getUpdates
Telegram documents this shape itself: "All queries to the Telegram Bot API must be served over HTTPS and need to be presented in this form: https://api.telegram.org/bot<token>/METHOD_NAME" (Telegram Bot API).
Read this part slowly. The address only works if all of these are right:
- The word
botis glued to the front of your token. No space, no slash between them. - There are no angle brackets. You're replacing
<token>, not keeping the<and>. /getUpdatesends with a capital U in the middle.
You'll get a screenful of dense text starting {"ok":true,"result":[. Don't read it all. Use your browser's find (Ctrl-F or Cmd-F) and search for "chat". You're looking for a fragment like:
"chat":{"id":123456789,"first_name":"Siti","type":"private"
The number straight after "id": is the one you want. Telegram calls it the "Unique identifier for this chat". Copy it exactly as it appears and paste it into your note next to the token.
If you see {"ok":true,"result":[]} instead, an empty pair of square brackets, nothing recent is waiting. Telegram doesn't keep these long; updates "will not be kept longer than 24 hours". Send your bot another "hi" and reload the page.
You'll know this worked when you've got two things saved: a token, and a chat ID number.
Step 4 — Wire it together in Make (give this one a patient 30–40 minutes the first time)
This is the meat. Two modules with a filter between them: read the whole sheet, keep only the rows due today, ping you about those. Make renames screens now and then, so where a label below sits somewhere slightly different, look for the same words.
In Make, "Click + Create a new scenario in the top-right corner to open the Scenario Builder" (Make). You get a blank canvas. "The giant plus in the center of the canvas lists the apps that you can add to your scenario". Search for Google Sheets.
In case it bothers you: the first module here is a search, not a trigger. That's allowed. Make's docs say "you can start your scenario with any possible module" (Make). The clock you set in Step 5 is what sets it off each morning.
Module 1 — Google Sheets → "Search Rows". Pick the plain one, not "Search Rows (advanced)". Click Create a connection, then Sign in with Google. Make's docs: "If prompted, authenticate your account, grant all requested permissions, and confirm access" (Make). Google will show a consent screen asking you to let Make reach your Sheets. That's expected.
Then fill in these fields (names from Make's docs):
- Search Method: Select from My Drive, so you can pick the file instead of typing an ID.
- Spreadsheet Name: your expiry sheet.
- Sheet Name:
Expiries. - Table contains headers: Yes. That's what makes Make call your columns
Item,ExpiryandRemind oninstead of letters. - Column range: pick a range that covers columns A to E.
- Filter: leave it empty. You want every row here. The filter you'll add in a minute does the picking, and it's free.
- Value render option: Formatted value, which Make describes as "calculated and formatted according to the cell's formatting". It keeps your expiry dates looking like dates in the message.
- Limit: "The maximum number of results Make should return during one scenario execution cycle." Put
300. That's comfortably more rows than you'll track.
Prime it now, before going further. Save the module, then "In the Scenario Builder toolbar, click the Run once button" (Make). A small bubble appears over the module. "Click on the output bubbles to view the details", and you should see your rows, each with its Remind on dates. Don't build the rest until this works. A problem here is easier to find now, before two more pieces sit on top of it.
Module 2 — Telegram Bot → "Send a Text Message or Reply" (module name from Make). To add it, "Click the + icon on the right side of the Google Sheets module" (Make) and search for Telegram Bot.
-
Connection: click Create a connection. "In the Token field, enter the token you copied from your Telegram Bot account", then "Click Save."
-
Chat ID: the number from Step 3.
-
Text: your reminder. Make's mapping panel opens when you "click inside the empty field" (Make) and lists the columns Module 1 found. Click one and it drops into the box as a coloured block. Type the plain words yourself and click in the bracketed bits:
⏰ [Item] expires on [Expiry] Owner: [Owner] [Notes] Renewed? Change the date in the sheet and these stop: https://docs.google.com/spreadsheets/d/...The four bracketed bits are blocks clicked in from the panel, not typed words. For the last line, copy your sheet's address from the browser bar and paste the whole thing in. Then every ping carries a link back to the sheet, which is where the fix happens.
-
Parse mode: leave it empty, so your words go out exactly as typed.
-
Disable Link Previews: Yes. Make's description: "Select whether you want to disable link previews for links in this message." Without it, Telegram may hang a preview card off the sheet link in every ping.
The filter. This is the part that decides what gets sent. Make's route in: "right-click on the dots between modules and select Set up a filter" (Make).
-
Label:
Due today. -
Condition: click in the box and pick Remind on from Module 1.
-
Text Operators: this starts on "Equal to". Change it to Contains. That's the label Make's own guides use: "Choose Text operator: Contains" (Make).
-
In the box below it, paste this exactly, curly brackets included:
{{formatDate(now; "YYYY-MM-DD"; "Asia/Singapore")}}
That's today's date, written in the same shape as your column E. formatDate is Make's function for when "You have a date value that you wish to convert (format) to a text value", and the last part is "The timezone used for the conversion" (Make), here Singapore's. The YYYY-MM-DD tokens mean "4 digit year", "Month number with leading zero" and "Day of month with leading zero" (Make).
Once pasted, it should turn into formula blocks rather than sitting there as plain typed text. If the curly brackets are still visible as text, delete it and build it from the panel instead. Make's rule is "To insert a function into a field, click the function name or drag it to the field" (Make); formatDate lives under Date and time functions, and its three slots take now, YYYY-MM-DD and Asia/Singapore.
Click Save on the filter. Then, as Make reminds you, "click the Save icon in the Scenario Builder toolbar to save your entire scenario."
Every row now goes through that filter each morning. The ones whose Remind on doesn't contain today's date stop there, at no cost. Only the due ones reach Telegram.
You'll know Step 4 worked when the test below sends you a ping. Before that, a Run once today will probably send nothing, unless one of your real dates happens to fall 60, 30 or 7 days from now. Nothing is the right answer.
Step 5 — Set the clock: 9am daily, Singapore time (10 minutes)
Two settings, and the order matters. Do the time zone first, or you'll schedule 9am somewhere else.
5a. Set your Make organisation's time zone to Singapore. Make is explicit that "The organization time zone defines the time used when executing scenarios and modules", while the user time zone only "defines how Make displays time" (Make). The path Make documents: click your profile icon in the upper-right corner and select Profile, then the Time zone options tab, then the edit icon next to your organisation. Search for Singapore and click Save. "Only organization owners and admins can edit the organization's time zone." On a free account you set up yourself, that's you.
5b. Schedule it. Back in the builder, "In the Scenario Builder toolbar, click Every 15 minutes to open the schedule settings" (Make). Make lists the options as "At regular intervals", "Once", "Daily", "Weekdays (Mon-Fri)" and a few more (Make). Choose Daily, not "Once", and set the time to 09:00.
5c. Turn it on. Save the scenario. Make's guide: "After you schedule your scenario, you'll be prompted to activate it. Click Activate scenario." Until you do, nothing runs by itself, however well Run once worked.
You'll know this worked when the toolbar shows a daily 09:00 schedule instead of "Every 15 minutes", and the scenario is switched on.
Test it works (10 minutes)
Do all four. The last one matters most.
- Add a test row. Item
TEST: delete me, Owner your name, Expiry exactly seven days from today (count it on your phone's calendar). The last date in its column E should be today's date. - Click Run once. Within seconds, a ping should land in Telegram naming
TEST: delete me. Tap the sheet link in it. Your sheet should open. - Change the test row's Expiry to eight days from today. Column E's last date is now tomorrow. Click Run once again. Nothing should arrive. That's the filter doing its job.
- Leave the test row overnight. Tomorrow at 9am it's exactly seven days out, and the ping should arrive without you touching anything. When it does, the build's finished. Delete the test row.
A scenario that works on Run once but was never activated will sit there doing nothing, quietly, forever. Test 4 is what proves yours isn't one of them.
When it doesn't
Nothing arrives at 9am, but Run once works. The scenario was never activated, or its schedule is still on the default. Open it and check the toolbar shows a daily 09:00 run and the scenario is on (Make).
It arrives at a strange hour. You set the schedule before the organisation time zone, or you changed your user time zone instead. Only the organisation setting decides when scenarios run (Make). Fix it, then reopen the schedule and re-enter 09:00.
Run once finds your rows, but the test row never gets pinged. The filter isn't matching. Check four things in order. The test row's column E really does contain today's date, in year-month-day shape. The filter's Condition is Remind on, not Expiry. The operator is Contains, not "Equal to". And the formula in the filter turned into blocks. If you can still see the curly brackets as typed text, Make will hunt for those literal characters, which never appear in your sheet.
Column E shows an error instead of dates. Either the Expiry cell isn't a date the sheet recognises (retype it), or the formula picked up a stray character (re-paste it from this page). If every row errors, your sheet's locale may want semicolons between formula parts instead of commas. Swap each , in the formula for ;.
Column E's dates are months away from where they should be. Day and month got swapped when you typed. Set the locale to Singapore as in Step 2, then retype the expiry dates.
The ping shows a five-digit number where the expiry date should be. Open Module 1 and set Value render option to Formatted value. Its neighbour, Date and time render option, "Specifies whether dates are shown as formatted text or numeric serials" (Make), so check that one too.
The getUpdates page shows {"ok":true,"result":[]}. Updates aren't kept "longer than 24 hours" (Telegram Bot API). Send your bot another message and reload.
The getUpdates page shows an error that mentions a webhook. The bot is already wired to something that listens for its messages, and getUpdates "will not work if an outgoing webhook is set up". Make a fresh bot (Step 1 again) and use that one.
The Telegram module errors about the chat. The Chat ID is wrong, or you never sent your bot a message. Send it "hi", redo Step 3, and paste the number again.
A date went past and you were never pinged. Two possible reasons. You added the row after its last checkpoint (anything added with less than seven days to go gets no ping at all), or the scenario was off or broken on the checkpoint day. Missed checkpoints are skipped, not caught up the next morning. Make's scenario history shows each day's run, so look there for a gap.
Pings keep coming for something you've already renewed. Nobody changed the date in the sheet. Change it and the pings stop, because the new date's checkpoints are a year away. That's the system working. It's the sheet that went stale.
New rows never get pinged. The formula wasn't copied that far down, so column E is empty for them. Copy E2 further down. If you've gone past 300 rows, raise the Limit in Module 1 too.
The real failure won't show up as an error. It's the sheet quietly drifting out of date. Put fifteen minutes in the owner's calendar on the first Monday of every month to scan it. Then make two habits stick: a new hire's pass goes in on their first day, and a renewal's new date goes in the day it comes through.
Your data (read this one)
A list of who works for you and when their pass expires is personal data. The PDPA defines personal data as "data, whether true or not, about an individual who can be identified" from that data, or from that data plus other information the organisation can get at (PDPC). So here's where it travels.
What leaves your business: every morning, Make reads every row of the Expiries tab, because the picking happens in Make. Item names, dates, owners and notes. Only the rows due that day go on to Telegram.
Keep identity numbers out of the sheet. The same PDPC guidelines single out "data that has been assigned exclusively to an individual for the purposes of identifying the individual (e.g. NRIC or passport number of an individual)" as a type that's "more likely to identify an individual". Your reminder doesn't need it. "Work Permit: Ah Kow" is enough to act on. The FIN stays in your HR file, where it already lives.
Google. The sheet stays in your Google account. Make reads it through the connection you approved in Step 4. Make's privacy notice says "Google Workspace APIs are not used to develop, improve, or train generalized AI and/or ML models" (Make).
Make. The rows pass through Make's servers each morning. Its privacy notice tells EU, UK and Swiss residents their personal data "may be transferred outside of the European Economic Area (EEA), UK or Switzerland", and says it will be deleted "upon your request" or "as soon as it is no longer serving the purpose for which it has been collected". The notice gives no retention period for scenario run history, so assume it sits in your account until you clear it. One more reason to keep the sheet lean.
Telegram. The pings go into a private chat between you and your own bot. Nobody else is in it. Telegram's privacy policy says of bot developers: "They are completely independent from us" (Telegram). In this build, the developer is you. The bot answers to your token and your Make account.
No AI touches any of it. There's no model in this build, so nothing in your list is sent off to train one.
Who sees the sheet is the part you control most. Share it only with the people who handle renewals. Tracking when a staff member's pass expires is part of employing them, which is a sound reason to hold the date. It isn't a reason for the whole office to see it.
Switch it off
No lock-in, nothing to cancel. You never entered a card, so there's no bill.
To pause it, open the scenario in Make and switch it off. Make describes this as "clicking the ON/OFF button in the scenario details page" (Make). It stays built, and you can switch it back on whenever you like.
To remove it properly:
- Delete the scenario in Make, along with the Google Sheets and Telegram connections you made for it. The exact menu wording moves around, so look for the scenario's options and your account's list of connections.
- Revoke Make's access from Google's side. That's the step that truly cuts the cord. Go to your Google Account's linked apps page at myaccount.google.com/linkedapps, click Access to your Google Account, pick Make, click See details, then Remove access and Confirm (Google).
- Delete the bot via @BotFather. Its command list includes "/deletebot – delete your bot and free its username. Cannot be undone." (Telegram). Once it's gone, the token is dead even if someone copied it.
Keep the sheet, though. Even without the pings, it's the list you didn't have before.
What's next
An earlier nudge for Employment Passes. MOM says "You can apply to renew an EP up to 6 months before the pass expires" (MOM). If you'd like to start that early, swap the column E formula for this one, which adds a 180-day ping in front:
=IF(B2="","",TEXT(B2-180,"yyyy-mm-dd")&" "&TEXT(B2-60,"yyyy-mm-dd")&" "&TEXT(B2-30,"yyyy-mm-dd")&" "&TEXT(B2-7,"yyyy-mm-dd"))
It applies to every row, which does no harm. An early ping about the domain is a calm ping. The same trick adds a ping on the day itself: add &" "&TEXT(B2,"yyyy-mm-dd") before the final bracket.
Send it to a group instead of yourself. If two or three people share renewals, put the bot in a small admin group. Groups have one Telegram quirk (the bot can't hear ordinary chatter, so you send it a command first), and the roster reminders playbook walks through it in its Step 3. Swap the Chat ID for the group's number and you're done.
One tidy list instead of separate pings. On a heavy day you might get four messages in a row. Make's text aggregator is built for this; its own tutorial uses one to send "one organized list" instead of a stack of notifications (Make). The roster playbook's Step 4 shows the set-up. Add it once the plain version has run for a month.
More from the same bot. The token and chat ID you've got now work for any Telegram nudge. Low-stock alerts from a Google Sheet and the daily money snapshot use the same pairing.
Before you build a third and fourth of these, read the real cost of automation. Free tools are free. The upkeep isn't, and this build is the clearest example: the software runs for nothing, and the sheet needs a person.
Everything above was written from each tool's official documentation on 3 November 2026, with no build behind it and no screenshots. That's what Level 1 research means on this site. Screens move. If a button's been renamed since, the thing you're looking for is described in words next to it, and the linked doc is the current truth. More builds like this one are in the playbooks library.
Sources
Every factual claim above traces to one of these, fetched on the fact-check date in the byline.
- Make pricing FAQ — 'If you are on the Free plan, you have 1000 credits per month'; annual cheaper than monthly (fetched 3 Nov 2026)
- Make homepage — 'No credit card required', 'No time limit on free plan' (fetched 3 Nov 2026)
- Make — 'free tier plan… does not require a credit card, and is forever free' (fetched 3 Nov 2026)
- Make — credits: 1 operation equals 1 credit (fetched 3 Nov 2026)
- Make — search modules use 1 credit per run; filters use none (fetched 3 Nov 2026)
- Make — connecting Google Sheets: Create a connection, Sign in with Google (fetched 3 Nov 2026)
- Make — Google Sheets Search Rows fields: Search Method, Table contains headers, Value render option, Limit (fetched 3 Nov 2026)
- Make — Telegram Bot app: /newbot, token connection, 'Send a Text Message or Reply' fields (fetched 3 Nov 2026)
- Make — '+ Create a new scenario' and the plus in the centre of the canvas (fetched 3 Nov 2026)
- Make — a scenario can start with any module (fetched 3 Nov 2026)
- Make — the + icon on the right side of a module adds the next one (fetched 3 Nov 2026)
- Make — set up a filter: Label, Condition, the Text Operators dropdown (fetched 3 Nov 2026)
- Make — 'Choose Text operator: Contains' (fetched 3 Nov 2026)
- Make — mapping: click inside a field to open the panel (fetched 3 Nov 2026)
- Make — insert a function by clicking its name; the Date and time functions tab (fetched 3 Nov 2026)
- Make — formatDate (date; format; [timezone]) (fetched 3 Nov 2026)
- Make — date tokens YYYY, MM, DD (fetched 3 Nov 2026)
- Make — the Run once button and output bubbles (fetched 3 Nov 2026)
- Make — schedule options, including Daily (fetched 3 Nov 2026)
- Make — Every 15 minutes opens the schedule; Activate scenario (fetched 3 Nov 2026)
- Make — the organisation time zone decides when scenarios run (fetched 3 Nov 2026)
- Make — active vs inactive scenarios and the ON/OFF button (fetched 3 Nov 2026)
- Make — the text aggregator sends 'one organized list' (fetched 3 Nov 2026)
- Make Privacy Notice — Google Workspace APIs not used to train AI; transfers; deletion (fetched 3 Nov 2026)
- Telegram — the Bot Platform is free; bots can't start conversations (fetched 3 Nov 2026)
- Telegram — BotFather: /newbot, username rules, token safety, /deletebot (fetched 3 Nov 2026)
- Telegram Bot API — request URL form, getUpdates, 24-hour window, webhook conflict (fetched 3 Nov 2026)
- Telegram Privacy Policy — bots are independent of Telegram (fetched 3 Nov 2026)
- Google Sheets — the TEXT function and its date patterns (fetched 3 Nov 2026)
- Google Sheets — set a spreadsheet's locale and time zone (fetched 3 Nov 2026)
- Google Calendar — add a notification to an event (fetched 3 Nov 2026)
- Google — remove an app's access to your Google Account (fetched 3 Nov 2026)
- Google One — every Google account comes with 15 GB (fetched 3 Nov 2026)
- MOM — renew an Employment Pass up to 6 months before it expires (fetched 3 Nov 2026)
- PDPC — Advisory Guidelines on Key Concepts (revised 29 Apr 2026): the personal data definition; NRIC and passport numbers (fetched 3 Nov 2026)
How we're funded: some links on this page are affiliate links — if you sign up through one, we may earn a commission, at no extra cost to you. It never changes what we recommend. Full disclosure.
Get the next one in your inbox
The Red Dot Report — one useful automation email a week.