Start hereAutomationsGuidesYour planThe stackAboutWeekly email▶ YouTubeTelegram

“He asked to be removed. Two days later, he got another email.”

"Remove me" email → marked → confirmation, within a minute

By · Updated · Get guides by email

Now every request is handled in a minute.

A "remove me" email waits until someone is free. The sender is marked in the list and gets a confirmation within a minute, as spam law and GDPR require.

MakeGmailGoogle Sheets4 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: UNSUBSCRIBE BOT

Short answer

A "remove me" email waits until someone is free. The sender is marked in the list and gets a confirmation within a minute, as spam law and GDPR require.

Tools
Make, Gmail, Google Sheets
Cost to run
4 Make credits (operations) per run

The problem

A removal request that waits two days is a violation — and an angry customer. The consultant who manages the client's lists is responsible for it, and has no time to read every incoming email.

What happens when it runs

  1. Gmail detects an email containing "unsubscribe" / "remove me" / "stop"
  2. Search the sender in the mailing list sheet
  3. Update: status "removed" + date
  4. A short confirmation email: "You are removed. No further mail from us."

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 detection keywords
  • The mailing list spreadsheet id and email column
  • The confirmation wording

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.

  • Mailing list · email | status | removed_on (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

  • Keyword detection also catches "do not remove me". Review the removal log weekly and fix by hand — an unnecessary removal beats an illegal email.
  • This handles requests by email only. Whoever clicks an unsubscribe link in a mailing tool is handled by the tool. The two lists must stay in sync, and that is a different automation.

Questions

What does not work in ""Remove me" email → marked → confirmation, within a minute"?

Keyword detection also catches "do not remove me". Review the removal log weekly and fix by hand — an unnecessary removal beats an illegal email. This handles requests by email only. Whoever clicks an unsubscribe link in a mailing tool is handled by the tool. The two lists must stay in sync, and that is a different automation.

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

The detection keywords; The mailing list spreadsheet id and email column; The confirmation wording.

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

Make, Gmail, Google Sheets. 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.

Next step

All automations →
STATUS EMAIL

Every Thursday: project status → an email to the client, without writing it

Clients ask "what's happening" because nobody wrote. One status word in a sheet becomes a tidy weekly email to the client every Thursday, with no writing.

MakeGoogle SheetsGmail3 ops/run✓ imported in Make
MONTHLY REPORT

On the 1st: the month's summary → an email to the client, without opening a sheet

Clients want the same three numbers every month: leads in, deals closed, invoices open. On the 1st at eight they arrive in one email, from the sheet.

MakeGoogle SheetsGmail5 ops/run✓ imported in Make
RENEWAL NOTICE

Contract ends in 30 days → renewal email to the client → alert to you

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.

MakeGoogle SheetsGmailTelegram4 ops/run

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