🔓 Unlock all 10,000+ workflows & prompts free Join Newsletter →
✅ Full access unlocked — explore all 10,000 AI workflow and prompt templates Browse Templates →
Home › n8n › Workflow
January 22, 2026

NocoDB + Gmail: follow-ups sent, tracking stays clean

NocoDB + Gmail: follow-ups sent, tracking stays clean - n8n workflow automation template
Lisa Granqvist Partner Workflow Automation Expert
NocoDB + Gmail: follow-ups sent, tracking stays clean - n8n workflow automation template
Get a free AI assessment → Get a free AI assessment → ⬇️ Use template

Following up shouldn’t feel like detective work. But when your “next touch” date lives in one place, your drafts live somewhere else, and your sent history is a mystery, leads slip through the cracks.

This NocoDB Gmail follow-ups automation hits sales reps first. Recruiters and agency owners feel it too, because high-volume outreach only works when the boring parts run themselves. You get consistent follow-ups, without missing touches or accidentally emailing twice.

Below, you’ll see how the workflow pulls due leads from NocoDB, personalizes the right follow-up (up to four), sends it via email, and updates your record so tracking stays clean.

How This Automation Works

The full n8n workflow, from trigger to final output:

n8n Workflow Template: NocoDB + Gmail: follow-ups sent, tracking stays clean

The Problem: Follow-ups fall apart when tracking and sending are separate

Most follow-up systems break in a predictable way. You log leads in a database, set a “follow up on Friday” date, and then Friday arrives and you’re busy. So you scroll, filter, copy an email template, tweak a line, send it, and then forget to update the record. Next week you can’t remember what you sent, so you either overthink it or you send something twice. Worse, “Not Interested” leads keep showing up because nobody marked them correctly. It’s not hard work. It’s fragile work.

One missed update creates the next mess. Then the mess grows.

  • Due dates get stale, so you end up following up late (or not at all).
  • Template edits happen in the moment, which means your tone and offer drift across reps and campaigns.
  • Manual tracking makes it easy to send the wrong stage, like a “checking in” email to someone you never emailed.
  • “Not Interested” contacts keep resurfacing because the exclusion logic is never consistent.

The Solution: AI-personalized follow-ups sent on schedule, with NocoDB updated automatically

This workflow turns your lead database into a daily follow-up machine. Every morning (set to 10 AM by default), n8n pulls your lead rows from NocoDB, checks who is due today based on the “Next Follow up/Contact” date, and immediately removes anyone marked “Not Interested.” Then it routes each lead to the correct follow-up stage (1 through 4) based on what has already been sent. For that stage, an AI step personalizes the message by inserting the recipient’s name while keeping your template intact, so your emails stay consistent. Finally, the email sends via an SMTP “Send Email” node (or Gmail if you swap it), and NocoDB is updated to mark that follow-up as sent and schedule the next one.

The workflow starts with a daily schedule trigger, then NocoDB decides who is due. A switch chooses the correct follow-up, AI personalizes it, email goes out, and your NocoDB row is updated so the sequence stays reliable.

What You Get: Automation vs. Results

Example: What This Looks Like

Say you manage 120 active leads and you follow up with 25 of them on a typical day. Manually, you spend maybe 5 minutes per lead to look up the record, choose the right template, personalize it, send it, then update NocoDB. That’s about 2 hours a day. With this workflow, it’s closer to 10 minutes to review your due list and spot-check a few messages while n8n does the sending and updates in the background.

What You’ll Need

  • n8n instance (try n8n Cloud free)
  • Self-hosting option if you prefer (Hostinger works well)
  • NocoDB for your lead table and follow-up dates
  • Gmail to send follow-ups via OAuth (optional swap)
  • LLM API key (get it from Groq or OpenAI) for personalization

Skill level: Intermediate. You’ll connect accounts, map a few NocoDB fields, and adjust the follow-up templates.

Don’t want to set this up yourself? Talk to an automation expert (free 15-minute consultation).

How It Works

Daily trigger at 10 AM. n8n starts on a schedule, so follow-ups happen even when your calendar is chaos.

Due leads are pulled and cleaned up. The workflow retrieves lead records from NocoDB, filters to “due today,” and removes anyone flagged as not interested so they never enter the sending path.

The right follow-up is chosen and personalized. A routing step selects stage 1–4, then an AI composition step inserts the lead’s name into your template while keeping the rest of your message stable.

Email goes out and the record is updated. n8n sends the message (SMTP by default, Gmail if you switch nodes), then marks that follow-up as sent in NocoDB and sets the next follow-up date.

You can easily modify the follow-up timing to match your sales cycle based on your needs. See the full implementation guide below for customization options.

Step-by-Step Implementation Guide

Step 1: Configure the Schedule Trigger

This workflow starts on a schedule and then pulls lead records for follow-up evaluation.

  1. Add and open Scheduled Automation Start.
  2. Set Rule to an interval schedule with Trigger At Hour set to 10.
  3. Connect Scheduled Automation Start to Retrieve Lead Records.

Step 2: Connect NocoDB for Lead Retrieval

Pull all leads from NocoDB so the workflow can decide who needs a follow-up.

  1. Open Retrieve Lead Records.
  2. Credential Required: Connect your nocoDbApiToken credentials.
  3. Set Operation to getAll and Return All to true.
  4. Set Project ID to psinm4yvd05vnvy and Table to mznkwe3wz0dofde.
  5. Connect Retrieve Lead Records to Filter Due Contacts.
Tip: Ensure your NocoDB table contains the fields used later, including email, first_name, Next Follow up/Contact, and the follow-up status fields.

Step 3: Filter Due Leads and Route Follow-up Stages

Filter records due for follow-up, exclude uninterested leads, and route each record to the correct follow-up stage.

  1. In Filter Due Contacts, set the conditions to check if {{ $json['Next Follow up/Contact'] }} equals or is before {{ $now.format('M/dd/yy') }}.
  2. Connect Filter Due Contacts to Exclude Uninterested.
  3. In Exclude Uninterested, set the condition to require {{ $json['Not Interested'] }} to be empty.
  4. Connect Exclude Uninterested to Route Follow-up Stage.
  5. In Route Follow-up Stage, configure each rule to route when the respective follow-up field is empty: {{ $json['Follow Up 1 (Day 3) Y/N'] }}, {{ $json['Follow Up 2 (Day 7) Y/N'] }}, {{ $json['Follow Up 3 (Day 12) Y/N'] }}, and {{ $json['Follow Up 4 (Day 16) Y/N'] }}.
⚠️ Common Pitfall: The date comparison uses M/dd/yy format. If your NocoDB date format differs, the filters may not match correctly.

Step 4: Set Up AI-Powered Personalization

Each follow-up email is personalized using Groq models connected to the chain LLM nodes.

  1. Open Primary Groq Model and set Model to openai/gpt-oss-120b.
  2. Credential Required: Connect your groqApi credentials in Primary Groq Model.
  3. Repeat for Secondary Groq Model and Tertiary Groq Model with Model set to openai/gpt-oss-20b, and for Quaternary Groq Model with openai/gpt-oss-120b.
  4. Confirm each model is connected as the language model to its corresponding node: Primary Groq Model → Compose Follow-up One, Secondary Groq Model → Compose Follow-up Two, Tertiary Groq Model → Compose Follow-up Three, Quaternary Groq Model → Compose Follow-up Four.
  5. In each Compose Follow-up node, keep the personalization prompt and ensure the name variable uses {{ $json.first_name }}.
Tip: The AI nodes do not store credentials directly. Credentials must be added to the parent Groq model nodes, not the Compose Follow-up nodes.

Step 5: Configure Email Sending and Status Updates

Send the personalized email and update the lead record to mark the follow-up stage and next date.

  1. For each email node (Dispatch Follow-up One through Dispatch Follow-up Four), set Text to {{ $json.text }} and To Email to {{ $('Retrieve Lead Records').item.json.email }}.
  2. Credential Required: Connect your smtp credentials in all four Dispatch Follow-up nodes.
  3. Connect each dispatch node to its status update node: Dispatch Follow-up One → Mark Follow-up One, Dispatch Follow-up Two → Mark Follow-up Two, Dispatch Follow-up Three → Mark Follow-up Three, Dispatch Follow-up Four → Mark Follow-up Four.
  4. In the NocoDB update nodes, set the status field values to Y and set Id to {{ $('Retrieve Lead Records').item.json.Id }}.
  5. Configure next contact dates: in Mark Follow-up One use {{ $now.plus(4, 'Days').format('M/dd/yy') }}, in Mark Follow-up Two use {{ $now.plus(5, 'Days').format('M/dd/yy') }}, in Mark Follow-up Three use {{ $now.plus(4, 'days').format('M/dd/yy') }}.
  6. Credential Required: Connect your nocoDbApiToken credentials to all NocoDB update nodes (Mark Follow-up One, Mark Follow-up Two, Mark Follow-up Three, Mark Follow-up Four).
⚠️ Common Pitfall: The To Email field pulls from Retrieve Lead Records; if your lead table uses a different email column name, update {{ $('Retrieve Lead Records').item.json.email }} accordingly.

Step 6: Test and Activate Your Workflow

Run a full test to verify filtering, personalization, sending, and status updates before enabling production automation.

  1. Click Execute Workflow and monitor data passing from Scheduled Automation Start to Retrieve Lead Records and Filter Due Contacts.
  2. Verify that Route Follow-up Stage sends each lead to the correct Compose Follow-up node based on empty follow-up fields.
  3. Confirm the Dispatch Follow-up nodes send emails and the corresponding Mark Follow-up nodes update the lead record with the correct next contact date and status.
  4. Once successful, toggle the workflow to Active so it runs on the schedule.
🔒

Unlock Full Step-by-Step Guide

Get the complete implementation guide + downloadable template

Common Gotchas

  • NocoDB credentials can expire or need specific permissions. If things break, check your n8n credential settings and the NocoDB API token first.
  • If you’re using Wait nodes or external rendering, processing times vary. Bump up the wait duration if downstream nodes fail on empty responses.
  • Default prompts in AI nodes are generic. Add your brand voice early or you’ll be editing outputs forever.

Related Workflows

If your team also needs a more complete outreach flow (not just follow-ups), NocoDB to Gmail, personalized cold emails with follow ups pairs well because it keeps the same database-first tracking discipline.

When speed matters and you want someone to act the moment a follow-up is sent, Gmail + Slack follow ups that keep leads warm adds a simple internal alert loop.

If you live in a dedicated CRM and NocoDB is not your source of truth, FollowUpBoss + Gmail: lead follow-up that sticks is a cleaner fit for teams who want pipeline stages and follow-ups in one place.

Need to react to replies instead of just sending? HighLevel + Slack: never miss a Gmail reply again helps you catch warm responses fast so they don’t die in an inbox.

Finally, if your “database” is a spreadsheet and that’s not changing anytime soon, Google Sheets + Gmail: follow ups that book meetings gives you a similar outcome with a simpler data layer.


Quick reference:

Frequently Asked Questions

How long does it take to set up this NocoDB Gmail follow-ups automation?

About 45 minutes if your NocoDB table is ready.

Do I need coding skills to automate NocoDB Gmail follow-ups?

No. You’ll mostly map fields (name, email, dates) and paste your email copy into the AI prompt nodes.

Is n8n free to use for this NocoDB Gmail follow-ups workflow?

Yes. n8n has a free self-hosted option and a free trial on n8n Cloud. Cloud plans start at $20/month for higher volume. You’ll also need to factor in LLM API costs, which are typically fractions of a cent per personalization (this template notes about $0.001 with Groq).

Where can I host n8n to run this automation?

Two options: n8n Cloud (managed, easiest setup) or self-hosting on a VPS. For self-hosting, Hostinger VPS is affordable and handles n8n well. Self-hosting gives you unlimited executions but requires basic server management.

Can I customize this NocoDB Gmail follow-ups workflow for a different schedule (like 2, 5, 10, 14 days)?

Yes, and it’s one of the first tweaks you should make. Update the “Mark Follow-up One/Two/Three/Four” NocoDB update nodes so they write your preferred next date (instead of the default cadence like day 3, 7, 12, 16). You can also change the schedule trigger time from 10 AM to whatever fits your outreach window. If you want more than four follow-ups, you’ll duplicate the route, compose, send, and mark pattern for a fifth stage.

Why is my NocoDB connection failing in this workflow?

Usually it’s an expired or wrong API token in your n8n NocoDB credentials. It can also be a base/table change (renamed fields break mappings), or missing permission to update rows. If it fails only on busy days, check for rate limits and reduce batch size by filtering more aggressively.

How many leads can this NocoDB Gmail follow-ups automation handle?

Hundreds per day is normal on a modest setup.

Is this NocoDB Gmail follow-ups automation better than using Zapier or Make?

It depends on how strict you want the logic to be. This workflow uses routing for four stages, database updates, and AI personalization all in one run, which is the kind of “branchy” setup that gets expensive and annoying in many no-code tools. n8n also gives you a self-host option, which is handy when you start doing daily runs at scale. Zapier or Make can be totally fine for a two-step reminder flow, but this is more of a mini system than a single zap. Talk to an automation expert if you want help choosing.

Once this is running, your follow-up engine doesn’t depend on memory or motivation. The workflow handles the repetitive stuff, and your NocoDB tracking stays trustworthy.

Need Help Setting This Up?

Our automation experts can build and customize this workflow for your specific needs. Free 15-minute consultation—no commitment required.

Talk to Automation Expert →

Lisa Granqvist

Workflow Automation Expert

Expert in workflow automation and no-code tools.

×

Use template

Get instant access to this n8n workflow Json file

Copy and import json workflow into your n8n workflow

💬
Get a free quote today!
Get a free quote today!

Tell us what you need and we'll get back to you within one working day.

Get a free quote today!
Get a free quote today!

Tell us what you need and we'll get back to you within one working day.