n8n automation
Birthday texts that go out without anyone remembering.
- Client
- Matys Nsir · Bastide Confort Médical
- Sector
- Medical equipment
- Duration
- February 2026 · in production
The problem
Client birthdays were tracked by hand from irregular CSV exports. Numbers entered in inconsistent formats, duplicates across files, dates in the wrong shape for the CRM, and a manual send that got skipped the moment a week got busy. The gesture existed on paper and disappeared in practice.
The architecture
- 01
CSV import
extraction and validation
- 02
Normalisation
E.164 format + CRM dates
- 03
Deduplication
JavaScript rules
- 04
Cron 8am
autonomous daily run
- 05
Google Sheets
real-time log
The product
Anonymised screenshots — client names masked, amounts and volumes fictional
Data before automation
A French phone number can be written at least six ways in a client export. Until that's resolved, no send automation holds: it fails silently on part of the base and nobody notices. Normalising to the international E.164 format is step one of the workflow, not an option.
A log you can actually read
Every run writes to a Google Sheet in real time: who received, at what time, with what status, and why a recipient was skipped. The client can check for himself, without asking me. That's the difference between a system you endure and a system you control.
Stack
- n8n
- JavaScript
- Google Sheets API
- SMS API
- CRM Universal
- Cron
The outcome
0
manual sends left in the process
8am
daily trigger, unsupervised
2
workflows: manual import and autonomous run
5.0
reviews on Upwork and Malt
Malt · 5.0 · 01/03/2026
« Oussama is a responsive, professional freelancer and a pleasure to work with. He delivered both requested workflows seriously and efficiently, while taking the time to clearly explain the steps and how it all works. »
Need something similar?
I read every message myself and reply within 24 hours. No automated quote, no form disappearing into a void.
Start a projectOther work