How to Automate Lead Follow-Up for Your Spanish Business

You don’t usually lose leads because your service is bad. You lose them because nobody replied quickly enough.

A potential client fills in your contact form at 18:40 on a Tuesday. You’re with a customer, driving between jobs, or closing up your restaurant. By the time you remember to reply the next morning, they’ve already spoken to two competitors. That happens every week in small businesses across Almería, Murcia, Alicante, and Granada.

If you want more enquiries to turn into paying clients, you need a system that replies instantly, logs the lead properly, alerts your team, and chases the opportunity if nobody has followed up. This is exactly the kind of business automation we build at CostaDelClicks using n8n and, where it makes sense, Make.com. We do not default to Zapier for this kind of workflow because once lead volume grows, n8n usually gives Spanish SMEs better flexibility and lower ongoing cost.

What automated lead follow-up actually means

Automated lead follow-up means your business responds to a new enquiry without waiting for a human to remember.

That does not mean replacing personal sales with robotic spam. It means using automation to handle the first few predictable steps:

1. Capture the enquiry
2. Save it to your CRM
3. Send an instant acknowledgement email
4. Notify the right person internally
5. Check whether anyone followed up within 48 hours
6. Trigger a reminder or second message if needed

This works especially well for service businesses in Spain where leads arrive outside office hours. Estate agents, accountants, holiday rental managers, trades, legal firms, clinics, and consultants all deal with the same problem: the enquiry comes in when the team is busy.

At CostaDelClicks, we usually recommend building this with n8n rather than relying on overpriced automation tools. If you want a broader comparison, read our guide on n8n vs Make.com vs Zapier 2026. Zapier is fine for simple one-step tasks, but once you need branching logic, waiting periods, CRM checks, and lower running costs, n8n is usually the better fit for growing SMEs in Spain.

Key insight: automate the first two minutes of your lead response first. That alone usually fixes the biggest leak.

The step-by-step workflow: contact form to 48-hour follow-up

Here’s the simple workflow we’re building:

Contact form → CRM → email sequence → Slack notification → 48-hour follow-up

That sounds technical, but the logic is straightforward. Every part has one job.

Step 1: Capture the lead from your contact form

When someone submits your website form, your system should send structured data into n8n immediately.

Typical fields:

• Name
• Email
• Phone
• Company
• Service requested
• Message
• Preferred language
• Source page or campaign
• Consent checkbox

If your website is slow, broken on mobile, or hard to use in English and Spanish, fewer people will fill in the form in the first place. That’s why we usually address the website and the automation together. Our web design services focus on fast, static websites built as pre-rendered HTML and served on Cloudflare’s edge network. That is why our sites routinely score 100/100 on Lighthouse and load in under 0.4 seconds FCP. We also build bilingual English and Spanish sites properly, with native structure and hreflang implementation, not machine-translated pages bolted on afterwards. If website performance is part of the issue, our posts on why your website speed matters in Spain and how to pass Core Web Vitals are worth reading too.

What to do now: make sure your form collects only the fields you actually use. Too many fields reduce conversions.

Step 2: Validate and clean the data in n8n

The first thing n8n should do is check the incoming data before sending it anywhere else.

Basic checks:

• Is the email present and valid?
• Is the message clearly spam?
• Is the enquiry missing key info?
• Is the lead English-speaking, Spanish-speaking, or bilingual?
• Does the service request match one of your actual services?

You can use an IF node in n8n to separate valid leads from junk. Spam can go into a review queue or be marked automatically. Good leads move forward.

This matters more than people think. If bad data goes into your CRM, your sales process gets messy fast. We’ve audited enough local business systems to know that half the problem usually isn’t lack of leads. It’s poor handling after they arrive.

Step 3: Create or update the contact in your CRM

Once n8n confirms the lead is valid, it should create a new contact in your CRM or update an existing one.

Your CRM record should include:

• Full contact details
• Date and time of enquiry
• Service interest
• Lead source
• Notes from the form
• Owner or team member assigned
• Follow-up status
• Last contact date

If the email already exists, don’t create a duplicate. Update the record and log the new enquiry as an activity.

This is where many Spanish SMEs still rely on inbox folders, notebooks, or spreadsheets. That works until you get busy. Then leads disappear. A proper CRM gives you visibility. An automation layer makes sure it stays updated without manual admin.

If you’re still working from spreadsheets, our guide on replacing spreadsheets with automated CRMs will help you think through the next step.

What to do now: define your CRM stages clearly. For example: New Lead → Contacted → Qualified → Proposal Sent → Won/Lost.

Step 4: Send an instant acknowledgement email

This is the first message the lead receives. It should go out within seconds.

Its job is simple:

• Confirm the enquiry arrived
• Set expectations for response time
• Reassure the lead that a real person will reply
• Keep your brand front of mind while they wait

A good follow-up email looks like this

Subject: Thanks — we’ve received your enquiry

Body:

• Thank them by name
• Confirm what they asked about
• Tell them when you’ll reply
• Add a phone or WhatsApp option if urgent
• Keep it short

Example:

Hi Sarah,
Thanks for contacting us about website redesign support in Almería. We’ve received your message and a member of our team will review it shortly. If your enquiry is urgent, you can also reply directly to this email or contact us by phone.
Speak soon,
CostaDelClicks

If you serve both local Spanish businesses and expat-run SMEs, make this bilingual or route by language automatically. We build bilingual systems natively because this is a normal business reality in southern Spain, not an edge case. If your site still treats language as an afterthought, read should your website be bilingual?.

What to do now: promise a realistic response time. If you can usually reply in one business day, say that — don’t promise “within the hour” if you won’t deliver it.

Step 5: Notify your team in Slack

Your lead should not sit quietly in a CRM hoping someone notices it.

As soon as the CRM record is created, n8n should send a Slack notification to the right channel or person. That message should include the key details needed to act fast.

Example Slack alert:

• New lead from website
• Name
• Service requested
• Budget if provided
• Location
• Language
• Link to CRM record
• Link to source page
• Priority label

For example:

New website lead: John Smith
Service: holiday rental website
Location: Mojácar, Almería
Language: English
CRM: [View record]

If you run a small team, this can go into a general #sales or #enquiries channel. If you want cleaner handling, route by department:

• Web design enquiries → sales
• Automation enquiries → ops or solutions
• Existing client support → account management

This is the point where automation starts saving real time, not just looking clever. The person who needs to act knows about the lead instantly. For a business handling 20 to 30 enquiries a month, that usually removes at least 1 to 2 hours of copy-paste admin and internal chasing.

We build these workflows with internal logic that matches how the business actually works. A law firm in Granada won’t route leads the same way as a restaurant in Murcia or a holiday rental operator in Alicante. The automation needs to reflect your process, not force you into someone else’s template.

What to do now: choose one internal alert channel and one named owner for each lead type. If everyone owns it, nobody owns it.

Step 6: Wait 48 hours, then check if the lead was handled

Now for the most important part: the delayed follow-up.

Many businesses set up instant emails and Slack alerts but never build the safety net. That means the lead still gets forgotten if the team is busy, on holiday, or assumes someone else replied.

In n8n, add a Wait node for 48 hours. After that delay, the workflow checks the CRM record.

It should ask:

• Has the lead status changed from “New Lead” to “Contacted”?
• Has a note or activity been added?
• Has the assigned team member updated the record?
• Has the lead replied to the first email?

If yes, end the workflow.

If no, trigger the next action.

What should happen after 48 hours?

You have three sensible options:

Option 1: Send an internal reminder only

Best if your sales process is personal and you don’t want too many automated client emails.

Option 2: Send a second follow-up email

Best if the first email was just an acknowledgement and no human reply has happened yet.

Option 3: Do both

This is usually the best setup for small businesses.

A second email might say:

Hi Sarah,
Just a quick follow-up in case you still need help with your enquiry. If you’d like to move forward, reply to this email and we’ll get back to you.
Best,
CostaDelClicks

Keep it light. No guilt. No pressure.

If you want a deeper look at the business case behind this, see our post on the ROI of business automation and our related guide on how much time does automation actually save?.

What to do now: test the 48-hour branch with a dummy lead before going live. Most mistakes happen in the delay, status check, or stop conditions.

The n8n workflow logic, mapped simply

Here’s what the actual n8n logic looks like in plain English:

Node-by-node logic

1. Trigger: Website form submission webhook
2. Set node: Clean field names and standardise data
3. IF node: Check required fields and basic spam rules
4. CRM node: Search for existing contact by email
5. IF node: If exists, update contact; if not, create new contact
6. CRM node: Create lead/opportunity record
7. Email node: Send instant acknowledgement
8. Slack node: Notify internal team
9. Wait node: Pause workflow for 48 hours
10. CRM node: Re-check lead status and activity
11. IF node: Has a human followed up?
12. If yes: End workflow
13. If no: Send reminder email and/or Slack escalation
14. CRM node: Log follow-up action

Pseudo-logic version

WHEN new form submitted
  IF email valid AND not spam
    FIND contact in CRM by email
    IF contact exists
      UPDATE contact
    ELSE
      CREATE contact
    ENDIF

    CREATE lead record
    SEND acknowledgement email
    SEND Slack notification
    WAIT 48 hours

    CHECK CRM lead status
    IF status = Contacted OR activity exists
      END workflow
    ELSE
      SEND follow-up email
      SEND Slack reminder
      UPDATE CRM with reminder note
    ENDIF
  ELSE
    FLAG submission for review
  ENDIF

That’s the core engine. Once it works, you can expand it. At CostaDelClicks, this is usually where we add reporting, language-based routing, and exception handling so the workflow survives real-world messiness rather than only working in a demo.

What to do now: map your own process on paper before you build anything. If you cannot describe the workflow in twelve lines, it is too messy to automate well.

Where this workflow usually breaks

A lot of businesses try to automate lead follow-up and get poor results because the workflow itself isn’t the problem. The surrounding process is.

Problem 1: The form sends weak leads

If your website attracts the wrong enquiries or hides the right information, automation won’t fix that. Better positioning, clearer service pages, and faster load times usually improve lead quality before the workflow even starts.

This is why our approach at CostaDelClicks often combines site structure, messaging, and automation. A slow 2012-style brochure site with a buried contact form is not a lead system.

Problem 2: Nobody owns the lead

If the Slack alert goes to everyone, it often goes to nobody. Assign an owner.

Problem 3: The CRM isn’t updated properly

Your 48-hour logic only works if the team changes lead status when they make contact.

Problem 4: The follow-up email sounds automated

People can tell. Write like a human.

Problem 5: You automate too much, too early

Don’t build ten-branch logic before you’ve nailed the basic workflow. Start with:

• form capture
• CRM entry
• instant email
• team alert
• 48-hour check

Then improve it.

Key insight: most failed automation projects are really ownership problems disguised as tech problems.

A practical example for a Spanish business

Let’s say you run an English-speaking and Spanish-speaking property services business in Alicante.

A visitor lands on your site at 21:15 and submits a quote request.

Here’s what happens automatically:

• The form sends data to n8n
• n8n validates the email and service category
• The lead is added to your CRM as “New Lead”
• The visitor gets an immediate email in their preferred language
• Your sales channel in Slack receives the lead details
• The lead is assigned to the right person
• After 48 hours, n8n checks the CRM
• If nobody has updated the lead, Slack gets a reminder and the client gets a polite follow-up email

Nothing gets forgotten. Nobody needs to remember the admin. Your team only handles the human part.

That’s why we often recommend automation alongside web design Alicante work. The website should generate the lead, and the workflow should protect it. When we build this kind of setup, we usually review the site, the form, the CRM stages, and the follow-up logic together, because fixing only one layer rarely solves the leak.

What to do now: walk through your last five leads and note where each one could have been delayed, lost, or mishandled. That is the best starting brief for this workflow.

How to make the workflow even better later

Once the basic setup works, you can add more useful logic.

Lead scoring

Mark leads as high priority if they mention:

• urgent timeline
• clear budget
• high-value service
• commercial project
• repeat enquiry

Language routing

Send English leads to one team member and Spanish leads to another.

Source tracking

Tag whether the enquiry came from:

• Google Ads
• organic search
• Google Business Profile
• Facebook
• referral
• direct website traffic

WhatsApp alerts

If your team lives in WhatsApp more than Slack, route notifications there too. We’ve covered the wider topic in WhatsApp Business automation and connect your website to WhatsApp using n8n.

AI-assisted qualification

For high-volume businesses, AI can categorise incoming enquiries by intent, urgency, or service type before they hit the CRM. That can remove repetitive triage work, but it should not replace your sales team. It only works well when the underlying workflow is already clean. If you’re exploring that route, our guides on AI for small businesses in Spain and automating lead qualification are the next step.

What to do now: don’t add these extras until your basic workflow has run cleanly for at least two weeks without missed leads.

What tools do you actually need?

You do not need a giant enterprise stack.

For most SMEs in Spain, you need:

• A fast website with a clear contact form
• A CRM that your team will actually use
• An email sending tool
• Slack or another internal alert system
• n8n to connect the whole process

That’s it.

If you’re starting from scratch, keep the setup lean. The goal is not complexity. The goal is to stop losing warm leads.

At CostaDelClicks, we usually self-host n8n where possible because it gives clients better long-term value, more control, and fewer unnecessary monthly bills. For businesses in Almería, Murcia, Alicante, and Granada, that matters more than flashy dashboards. The same logic applies to websites: we build in Astro rather than WordPress because most SMEs do not need plugin bloat, maintenance headaches, or the security risk that comes with a stack of third-party add-ons.

What to do now: list the five tools you already use today, then identify the missing link between form submission and human follow-up. That gap is usually where the leak is.

Final checklist: your lead follow-up automation setup

Before you launch, check these points:

• Your contact form works properly on mobile
• Required fields are sensible, not excessive
• Spam filtering is in place
• CRM duplicates are handled
• The instant email sounds human
• Slack alerts go to a real owner
• The 48-hour wait and status check are tested
• Follow-up emails stop once a human has replied
• Everything is logged in the CRM
• Consent and GDPR handling are clear

If you also need to tighten up compliance, our guide to GDPR for Spanish business websites is worth reviewing before you go live.

What to do now: use this list as a pre-launch test sheet, not a vague reminder. Tick off each item against a real dummy enquiry.

FAQ