SolutionsPricingWorkshopsBlogNewsAboutLet's Talk

Email Marketing Automation: Mail & WhatsApp That Run Alone

How to build an email marketing system that syncs with your CRM, sends via email and WhatsApp, and handles replies. No brand recommendations.

AutomushPublished 10 min read

Email marketing automation is a process that pulls a recipient list from one source (CRM, spreadsheet, or form), sends messages via email or WhatsApp on a schedule or trigger, and updates the system based on responses. We build these systems with n8n, the WhatsApp Cloud API, and integrations to CRM and spreadsheets, so the business sends once and gets a report on who opened, clicked, and replied.

The system starts from a list that updates continuously, not a static file. When a new customer enters the CRM or signs up via a form, they are added to the list automatically. When a customer asks to be removed, they are marked and no longer receive messages. This is stored in one source, and the system reads from it every time it sends.

Why build an email marketing system instead of using a ready-made service?

An email marketing system built on automation infrastructure gives full control over sources, sending channels, and logic. A ready-made email service holds the list on their platform, limits you to one channel (usually email), and charges per number of recipients or messages. When you build the system yourself, you connect it directly to your CRM, send via both email and WhatsApp from the same process, and pay only for API traffic.

We build it like this: an n8n workflow reads the list from the CRM or spreadsheet, filters by conditions (for example: customers who have not received a message in the last 30 days, or leads that entered this week), and sends via an email provider or the WhatsApp Cloud API. Each send is recorded back to the CRM with a timestamp, so you can see who received when.

The second advantage is that you can send multiple channels in the same campaign. For example: a customer with an email address receives via email, and a customer with only a phone number receives via WhatsApp. The system checks what exists and sends accordingly, without splitting the campaign into two tools.

How does an email marketing system connect to CRM and spreadsheets?

An automated email marketing system connects to a CRM via API or webhook, and to spreadsheets via the Google Sheets API. n8n has a ready-made node for each of these, and the process reads the data in real time or on a schedule.

When the CRM supports an API (most systems do), the process sends a GET request to an endpoint that returns a contact list. You can filter by date, tags, or custom fields. For example: “give me all leads whose status is ‘interested’ and who have not been sent a message this month”. The response comes back in JSON, and the workflow loops through each record and sends.

When the source is Google Sheets, the process reads the sheet row by row, skips rows already marked “sent”, and updates the column after sending. This works well for businesses that manage the list manually or import it from a file.

The connection between the email marketing system and the source is two-way: the process reads who to send to, and writes back when it was sent and what the result was. If the message failed (invalid email address, blocked phone number), this is recorded, and the system does not try again in the same cycle.

We use integrations to connect all these sources into one system, so the business does not need to switch between tools.

How do you send via email and WhatsApp from the same system?

An email marketing system that sends via email and WhatsApp uses two providers: an SMTP provider or API for email (like SendGrid, Amazon SES, or even Gmail API for small volumes), and Meta’s WhatsApp Cloud API for WhatsApp. Both channels run in the same n8n process, and the system chooses which channel to send to based on what exists in the record.

The process looks like this: for each contact, the system checks if there is an email address and if there is a phone number. If there is an email, it sends via an Email node or HTTP Request to the email provider. If there is a phone and the customer gave consent to receive messages on WhatsApp, it sends via the WhatsApp Cloud API. You can also send to both channels at the same time, but usually businesses choose one channel based on customer preference.

In email, the content can be HTML with images, buttons, and links. In WhatsApp, you can send an approved template message with variables, or a free-text message if the conversation is already open. Templates require prior approval from Meta and are limited to a certain format, but they allow sending to any number even if the customer has not opened a conversation with you.

Each send returns a response: success, failure, or pending. The system writes the status back to the CRM or spreadsheet, so you can see who received and who did not. If the message failed, the process can try again after a defined time, or send an alert to the manager.

What happens when someone replies to a message?

An email marketing system that handles replies listens to webhooks from the email provider and the WhatsApp Cloud API, captures the response, and updates the CRM or triggers a follow-up process. This is not mandatory for every email marketing system, but it turns it from a sending system into a two-way communication system.

In email, most providers send a webhook when someone opens a message, clicks a link, or replies. The process captures the webhook, identifies the customer by email address, and writes the action to the CRM. For example: “Customer X opened the message at 10:32, clicked the link at 10:35”.

In WhatsApp, when someone replies to a message, Meta sends a webhook with the reply content. The system can parse the reply (for example: if the customer wrote “yes” or “no”), update the CRM accordingly, and send a follow-up message. You can also route replies that are not understood to a queue where a human responds.

Handling replies turns the email marketing system into a system capable of managing a conversation. For example: sending an event invitation, capturing confirmation or refusal, and automatically sending arrival details to those who confirmed. All of this runs without manual intervention, and the business sees the results in the CRM.

How long does it take to set up an email marketing automation system?

Setting up an email marketing automation system takes between one week and three weeks, depending on the number of sources, the number of channels, and the logic of filtering and sending. A simple system that reads from a spreadsheet and sends email can be ready in days. A system that integrates CRM, email, WhatsApp, and reply handling takes more time.

The first stage is defining the source: connecting to the CRM or spreadsheet, defining the fields the system needs (name, email, phone, tags), and checking that the data is read correctly. This takes one to three days, depending on data quality and API complexity.

The second stage is building the process: defining the filter (who receives a message), writing the message content, connecting to the email provider or WhatsApp Cloud API, and testing sending. This takes a week on average, including tests on a small list before the real send.

The third stage is adding reporting and reply handling, if needed. This includes setting up webhooks, writing the logic that updates the CRM, and checking that the system handles every state (success, failure, reply). This can add another week.

After setup, the system runs on its own. The business updates the CRM or spreadsheet, and the system sends according to the defined schedule (once a day, once a week, or immediately when a new customer is added).

Stage What happens Time
Connect to source Define CRM or spreadsheet, map fields, test reading 1-3 days
Build sending process Filter, content, connect to provider, tests 5-7 days
Reporting and reply handling Webhooks, update CRM, handle failures 3-7 days

How do you measure if the email marketing system is working?

An automated email marketing system is measured by open rate, click rate, and reply rate, and each of these is recorded in the CRM or a dashboard. The goal is to see how many recipients actually read the message, how many acted, and how many replied.

Open rate in email is measured via a tracking pixel that loads when the customer opens the message. Most email providers provide this out of the box, and they send a webhook with the opening details. In WhatsApp, Meta sends a read confirmation (delivered, read) if the customer has not turned off this option. The system writes the status to the CRM, so you can see who opened and when.

Click rate is measured via unique links that the system creates for each recipient. When someone clicks, the link passes through a tracking server that records the click and redirects to the real destination. This works in both email and WhatsApp, and the data is written back to the CRM.

Reply rate is measured directly: how many people replied to the message. In WhatsApp this is simple, because every reply comes to a webhook. In email, it depends on whether the customer clicked “reply” and sent an email back. The system counts replies and updates the CRM, so you can see which content causes more interaction.

These metrics are collected in real time and displayed in a dashboard or a report that the system creates after each campaign. The business sees how many messages were sent, how many succeeded, how many were opened, and how many resulted in action. This helps decide which content works and which does not.

What happens when the system encounters an error?

An automated email marketing system that encounters an error (invalid email address, blocked phone number, or API failure) records the error, skips that recipient, and continues to the rest of the list. If the error repeats, the system sends an alert to the manager and stops trying to send to that recipient.

In n8n, every node can fail, and the process continues only if the node succeeded. When a node fails, you can define what happens: try again after a minute, skip and continue, or stop the entire process. In an email marketing system, the default setting is to skip and continue, because one error should not stop the entire campaign.

Every error is recorded in the CRM or spreadsheet with details: what the error was, when it happened, and for which recipient. For example: “Send failed for customer X - email address does not exist”. This allows cleaning the list and removing addresses that do not work.

If the API of the email provider or WhatsApp goes down, the system tries again after a predefined time (usually a minute or five minutes). If the second attempt also fails, the system stops and sends an alert. This prevents a situation where the system continues trying to send when the service is unavailable, wasting resources.

We build the systems with built-in error handling, so the business does not need to track every send manually. The system reports only when there is a problem that needs attention.

Can you send personalized messages to each recipient?

An automated email marketing system can customize the message content for each recipient based on data that exists in the CRM or spreadsheet. This includes first name, company name, last activity date, or any other field. The system reads the value from the record and replaces it in the message before sending.

In n8n, this is done via variables. For example, if the message is “Hello {{name}}, we wanted to update you on…”, the system replaces {{name}} with the customer’s real name from the record. This works in both email and WhatsApp, and it makes the message feel personal even if it is sent to thousands of recipients.

You can also customize the entire message content based on conditions. For example: customers who bought in the last month receive one message, and customers who did not buy receive a different message. The system checks the relevant field in the CRM and chooses which message to send.

In WhatsApp, personalization works only within approved templates. You can define variables (for example: name, date, amount), and Meta fills them at send time. You cannot send completely free content to a customer who has not opened a conversation, but within the template framework there is enough flexibility.

Personalization improves open rate and reply rate, because the customer sees that the message is intended for them. This does not require additional work after setup, because the system does this automatically for each recipient.

For more on how we build automations that integrate with the business’s existing systems, read the guide on lead management best practices which explains the connection between communication tools and CRM.

Frequently asked questions

Can an email marketing automation system also send SMS?

Yes, you can add SMS as an additional channel via an SMS provider that supports API (like Twilio or local providers in Israel). The process is identical to sending email or WhatsApp: the system reads the phone number, sends a request to the provider's API, and records the result back to the CRM. SMS costs more than WhatsApp, but it reaches devices that are not connected to the internet.

What happens if a customer asks to be removed from the mailing list?

The system can handle removal requests automatically. You can add an "unsubscribe" link in every message, which when clicked sends a webhook that updates the CRM and marks the customer as "do not send". In WhatsApp, you can detect keywords like "stop" or "unsubscribe", and update the status automatically. After the customer is marked, the system skips them in every future campaign.

Can you send file attachments in an email marketing automation system?

Yes, in email you can attach files (PDF, images, documents) via the email provider. In WhatsApp you can send files via the Cloud API, but they need to be stored at an accessible URL or uploaded to Meta's server. The system can read the file from a source (for example Google Drive or an internal server), and attach it to each message. There is a size limit per provider, usually up to 16MB in WhatsApp and up to 25MB in most email providers.

How much does it cost to run an email marketing automation system?

The cost depends on providers and volume. n8n is available in a self-hosted version at no licensing cost, or in a managed version starting from around $20 per month. Email providers charge per number of messages (SendGrid starts at $15 for 40,000 messages). WhatsApp Cloud API is free up to 1,000 free conversations per month, then charges by conversation category (marketing, utility, service). There is no cost per number of recipients in the list, only for what is actually sent.

Interested?system integration solutions

From the newsroom

All news

Which of your processes could run on its own?

A free 30-minute discovery call, no commitment. We map your processes together and tell you honestly whether and how automation can help.

Try a call with agent now