n8n automation

Automated email and SMS outreach, personalised by AI

An n8n workflow pulls contacts from a Google Sheet, writes each person their own message, sends the email and, for mobile numbers, an SMS too. The sheet shows you straight away what went out and what was delivered.

n8n · OpenAI / OpenRouter · Google Sheets · SMS gateway

In short

Automated, AI-personalised email and SMS outreach is an n8n workflow that, on a schedule, takes the next batch of contacts from a Google Sheet and writes a separate message for each one, using their name, context and an offer matched to what the sheet says about them. It then sends the email and, if the number is a mobile, an SMS through a gateway API, and checks whether the text was delivered. It suits businesses that write to customers or leads on a regular basis: follow-ups after meetings, reminders, invitations, offers to their own list. The sheet stays your control panel, showing who got an email, who got a text and what happened to each.

Workflow

This is the workflow in n8n

A simplified, interactive version of our workflow. Drag the nodes and run it to watch the data flow.

Drag the nodes · click “Run”

Execution log

    AI email + SMS: Sheet → AI writes the message → email → number check → SMS via gateway → statuses back in the sheet

    Screenshot from the build

    The full workflow in our n8n

    A real, unedited screenshot from the n8n editor. The interactive version above is simplified; here you can see every node, branch and error path.

    Full size
    n8n workflow: AI-personalised email & SMS
    Workflow in n8n. Built by Bartłomiej Chwajoł.

    Sound familiar?

    What this solves

    One-template bulk email looks like spam, and gets read that way.

    The language model writes every message individually from the columns in your sheet: name, industry, last contact, product. An output parser makes sure there is always a subject and a body in a fixed format.

    You send texts from a separate dashboard and never know which ones arrived.

    The workflow checks whether the number is a mobile, sends the SMS through the gateway API and keeps asking for the status until the message leaves the queue. The outcome (delivered, rejected, failed) lands in the sheet in plain words.

    Sending to the whole list at once runs into mailbox limits or a block.

    Contacts go out in small batches with pauses between messages. Each row gets a status as soon as it is sent, so after a pause or an error the workflow never writes to the same person twice.

    How it works

    Step by step

    1. 01

      Scheduled start

      A Schedule Trigger runs the workflow at set times, for example on weekday mornings. For testing you can start it by hand.

    2. 02

      A batch of contacts from the sheet

      Only rows waiting to be sent are read from Google Sheets, and a Limit node caps how many go in one run. A loop then handles them one by one.

    3. 03

      AI writes the message

      A Basic LLM Chain, using a model via OpenRouter or OpenAI, writes the subject and body from the contact’s data and your guidelines: tone, length, sign-off and what must never be promised.

    4. 04

      Email goes out

      The email is sent from your own mailbox and the row gets a status and date. A short wait spreads the sending out over time.

    5. 05

      Phone number check

      A Code node cleans up the number format and an IF node lets only mobiles through. Landlines and invalid numbers are flagged in the sheet.

    6. 06

      SMS through the gateway

      An HTTP Request sends the text through the gateway API. If the gateway rejects it, the workflow logs the reason and moves on to the next person.

    7. 07

      Delivery status in the sheet

      The workflow waits a moment and asks the gateway for the status while the SMS is still queued. It turns the status code into a readable label and saves it next to the contact.

    Implementation details

    This workflow is built for regular, personal contact with your list, not for a designed newsletter. Instead of a campaign tool you have a sheet: each row is a person and the columns describe what you know about them. AI uses that data to write a message that reads like a normal email from a human, not a template with the first name swapped in.

    How the AI writes. The prompt holds your rules: tone, length, sign-off, off-limits topics and anything the message must never promise, such as discounts or dates that aren’t in the sheet. The model only sees the columns it needs for personalisation. A Structured Output Parser enforces the response format, so an empty or cut-off message never reaches the send step.

    A human at the start. When we deploy it, the first runs are in test mode: messages go to your own address or wait in the sheet for approval. Once you’re happy with the copy, you flip a status in the sheet and sending to customers begins. You can keep approval switched on for selected segments, such as your biggest accounts.

    Statuses, retries and errors. Every row has a separate status for email and SMS. The workflow tells apart a non-mobile number, a gateway rejection, a queued message and a delivered one. Status polling has a retry cap, so the loop never spins forever. A mailbox or API error doesn’t stop the whole batch: the row gets a description of the problem and you get an alert.

    Consent and opt-outs. We can set the workflow to write only to rows marked as consented and to skip anyone who has unsubscribed. The legal basis for contacting people is yours to own, but the automation applies the rule every single time, with no quick exceptions.

    New to the tool? Read what n8n is and how it works. For more ideas on automating customer communication, see our 15 AI automation examples for business, or get in touch to talk through your setup.

    01

    Integrations

    • n8n
    • Google Sheets
    • OpenAI
    • OpenRouter
    • SMTP / Gmail
    • SMS gateway API
    02

    What you need

    • A Google Sheet of contacts (or a CRM export) with columns to personalise from
    • A sending mailbox with SMTP access, or a Google Workspace account
    • An SMS gateway account with an API for sending and status checks
    • An API key for a language model (OpenAI or OpenRouter) on your own account
    • Consent for email and SMS contact across the list you write to
    • An n8n instance on your server or in n8n Cloud (we can set it up)
    03

    How we tailor it

    • Contacts straight from your CRM (e.g. HubSpot, Pipedrive) or your store’s customer base instead of a sheet
    • Email only, SMS only, or SMS as a second step a few days after the email
    • Approval of the copy before sending, in the sheet, on Slack or in Telegram
    • Sending windows, no weekends and a pace that suits your mailbox
    • Follow-up sequences with different copy after a set number of days

    FAQ

    Frequently asked questions

    Isn’t this just spam with extra steps?

    Not if you write to people who agreed to hear from you and you have something specific to tell them. The workflow doesn’t buy lists or scrape addresses; it only works with your sheet. Personalisation and a steady pace make the messages look like ordinary correspondence, but consent always comes first.

    Which AI model writes the messages?

    The workflow uses models through OpenRouter or directly from OpenAI, so you can switch models without a rebuild. For short messages a cheaper model is usually enough. You pay the provider for usage from your own account, and the cost depends on how many messages you send and how long they are.

    Which SMS gateway does it work with?

    Any gateway with an API for sending messages and checking their status. The SMS goes out through an HTTP Request node, so switching gateways usually means a new API address, new credentials and a different mapping of status codes.

    Can I read the message before customers get it?

    Yes. The simplest option is for the AI to save the copy in the sheet, with sending starting only once you change the status to “approved”. You can also get a preview on Slack or Telegram with an approve button.

    How long does it take to set up?

    Once you have the contact sheet, a mailbox and an SMS gateway account, setup with testing usually takes 1–2 weeks. Most of that time goes into tuning the prompt on your real examples so the messages sound like you.

    Get a quote

    Want this in your business? Tell us what it should do.

    Describe your process and the tools you use. We reply within one business day with an implementation plan.

    What do you need?

    Goal, deadline, links to inspiration — the more specifics, the more accurate the quote.

    Other builds

    More n8n automations

    1. 01 AI songs for YouTube OpenRouter · fal.ai · YouTube Data API · Telegram An n8n workflow takes an idea from the queue, writes the lyrics, generates a song with vocals, cover art and a video, then sends you a preview on Telegram. Nothing reaches YouTube until you approve it.
    2. 02 Allegro listing optimisation with AI Allegro REST API · OpenAI · Google Sheets · Gmail Every hour, an n8n workflow takes the next offers from a sheet, pulls their data and category parameters from the Allegro API, and AI writes a new title and description. Changes reach Allegro only after validation, and every offer is backed up first.
    3. 03 AI email assistant on Telegram IMAP · OpenAI · Telegram Bot API · SMTP An n8n workflow reads your inbox, filters out spam and sends the emails that matter to Telegram. You record a voice note with your answer, AI turns it into a finished email, and one button sends, revises or discards it.
    4. 04 Multichannel product listing WooCommerce REST API · Allegro API · Erli API · OpenAI You enter the product data once, and an n8n workflow picks the category on each platform, writes the copy, prepares the images and creates the product in WooCommerce plus offers on Allegro and Erli. At the end you get one record with the result from every channel.
    5. 05 AI WooCommerce product translation WooCommerce · WordPress REST API · OpenAI · Google Sheets An n8n workflow takes untranslated products from a queue, and AI translates their titles, descriptions, attributes and SEO meta into the languages you choose. Each result is checked for completeness and length before it reaches your store.
    6. 06 AI SEO landing pages for WordPress Google Search Console · OpenRouter · WordPress REST API · Google Sheets An n8n workflow takes a keyword from a sheet, analyses the search results, plans the structure and writes a landing page with links to your existing pages. The finished page lands in WordPress as a draft for you to approve.