🔓 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

FollowUpBoss + Gmail: lead follow-up that sticks

FollowUpBoss + Gmail: lead follow-up that sticks - n8n workflow automation template
Lisa Granqvist Partner Workflow Automation Expert
FollowUpBoss + Gmail: lead follow-up that sticks - n8n workflow automation template
Get a free AI assessment → Get a free AI assessment → ⬇️ Use template

Leads come in, you mean to follow up, and then the day happens. By the time you remember, the hot one is cold, and the “easy win” is suddenly a lost deal.

This FollowUpBoss automation hits real estate agents first, honestly. But marketing managers and small sales teams feel the same drag when follow-up depends on memory and manual checks. The goal is simple: every new lead gets the right outreach, on the right channel, without you babysitting the process.

You’ll see how this workflow pulls new leads from FollowUpBoss, cleans and validates contact data, then sends personalized email and/or text (including WhatsApp) via Gmail and Twilio while keeping your records tidy for reporting.

How This Automation Works

Here’s the complete workflow you’ll be setting up:

n8n Workflow Template: FollowUpBoss + Gmail: lead follow-up that sticks

Why This Matters: Leads Go Cold When Follow-Up Is Manual

Most “lead follow-up systems” break in boring places. The lead lands in FollowUpBoss, someone skims it on mobile, and then it’s a coin flip whether the next step happens. You also waste time doing tiny admin tasks that feel safe but don’t close deals: fixing phone formats, checking if the email is real, hunting duplicates, deciding whether to text or email, then trying to remember what you sent. And if you get the channel wrong (texting a bad number, emailing a blank address), you lose time and momentum.

The friction compounds. Here’s where it breaks down in real life.

  • New leads get treated unevenly because follow-up depends on who saw the notification first.
  • Phone numbers and emails arrive messy, so outreach fails silently or you spend a few minutes cleaning every record.
  • Duplicates sneak in, which means two messages go out (awkward) or the “real” lead gets ignored.
  • Channel decisions take mental energy when you’re busy, so you default to “I’ll do it later” and later never comes.

What You’ll Build: Automated Multi-Channel Lead Outreach

This workflow runs on a schedule, checks the last time it ran, and pulls only the newest leads from FollowUpBoss using an HTTP request. From there it validates the basics before any message goes out: contact records are filtered, email and phone fields are checked, and obvious bad data gets routed away from the “send” steps. Then it makes a practical decision about how to reach each lead. If both email and phone look usable, it sends a personalized Gmail email and a Twilio text. If the phone is invalid, it takes the email-only path. If the email is missing, it switches to SMS or WhatsApp. Finally, it stores the current run time so the next run only processes fresh leads, keeping the process consistent and repeatable.

The workflow starts with scheduled lead retrieval from FollowUpBoss. It cleans and validates contact info, then routes each person into the correct outreach path (email, SMS, WhatsApp, or a combination). After messages are sent, processing is batched and the run is recorded so you don’t re-contact the same lead.

What You’re Building

Expected Results

Say your team gets 40 new leads a week. Manually, it’s easy to spend about 5 minutes per lead checking for missing info, cleaning phone/email, deciding a channel, then sending messages. That’s roughly 3 hours of repetitive work, plus the follow-up you forget when things get busy. With this workflow, the “human time” is closer to 10 minutes to set it up and spot-check a sample; the scheduled run, validation, batching, and sending happens in the background.

Before You Start

  • n8n instance (try n8n Cloud free)
  • Self-hosting option if you prefer (Hostinger works well)
  • FollowUpBoss for your lead source and contact fields.
  • Gmail to send personalized email outreach.
  • Twilio (SMS/WhatsApp) to message leads by phone.
  • OpenAI API key (get it from your OpenAI dashboard).

Skill level: Intermediate. You’ll connect accounts, add credentials, and sanity-check the routing logic for your data.

Want someone to build this for you? Talk to an automation expert (free 15-minute consultation).

Step by Step

Scheduled lead pull from FollowUpBoss. The workflow runs on a schedule trigger, looks up the previous run time, then fetches only the most recent leads via an HTTP request so you don’t reprocess old contacts.

Cleaning and validation. Leads get filtered and checked for missing details. Email and phone validation happens before any message is sent, which prevents wasted sends and reduces “bounce” chaos in your reporting.

Smart routing to the right channel. Using If/Switch logic, contacts with good email and phone go down the full path (Gmail plus Twilio SMS). Missing email routes to SMS/WhatsApp. Invalid phone routes to email-only. Simple. Effective.

Send, then track the run. Gmail and Twilio dispatch the outreach, and batching keeps the workload stable if you have lots of leads. At the end of each path, the workflow stores the current run time for the next scheduled run.

You can easily modify the message copy and channel rules to match your brand voice and compliance needs. See the full implementation guide below for customization options.

Step-by-Step Implementation Guide

Step 1: Configure the Scheduled Trigger

Set the workflow to run on a fixed schedule so it can pull only newly created leads since the last run.

  1. Add the Scheduled Automation Start node as the trigger.
  2. Set Rule to an interval of minutes and Minutes Interval to 3.
  3. Connect Scheduled Automation Start to Retrieve Previous Run.

Step 2: Connect Follow Up Boss API

Use the last run timestamp to fetch only recent leads from the Follow Up Boss API.

  1. In Retrieve Previous Run, keep the JavaScript as provided to read lastRun from workflow static data.
  2. Configure Fetch Recent Leads with URL set to =https://api.followupboss.com/v1/people?createdAfter={{$json["lastRun"]}}.
  3. Set Authentication to genericCredentialType and Generic Auth Type to httpBasicAuth.
  4. Credential Required: Connect your httpBasicAuth credentials in Fetch Recent Leads.
  5. Connect Fetch Recent Leads to Delay Processing and set Amount to 6.

⚠️ Common Pitfall: If lastRun isn’t stored yet, Retrieve Previous Run defaults to 15 minutes ago—this is expected on first run.

Step 3: Set Up Lead Validation and Routing

Split leads into individual records, validate contact data, and route leads to the correct outreach path.

  1. In Split Lead Records, set Field To Split Out to people.
  2. In Filter Valid Contacts, set conditions for Email Status and Phone Status with expressions ={{ $json.emails[0].status }} and ={{ $json.phones[0].status }} to equal Valid.
  3. Configure Validate Email & Phone to require both ={{ $json.emails[0].status }} and ={{ $json.phones[0].status }} equal Valid.
  4. In Check Missing Contact Info, keep the condition ={{ $json.emails[0].status }} equals Valid to route to email-only or SMS-only paths.
  5. Note that Check Missing Contact Info outputs to both Batch Email Only Path and Batch SMS Only Path, depending on the condition result.

⚠️ Common Pitfall: Ensure your API response includes emails and phones arrays—missing arrays can cause the status checks to fail.

Step 4: Map Lead Fields for Outreach

Normalize lead data into consistent fields before sending emails and messages.

  1. In Map Lead Fields, set firstName to ={{ $json.firstName }} and lastName to ={{ $json.lastName }}.
  2. Set Source to ={{ $if($json.source === "<unspecified>", "Manually/Other", $json.people[0].source) }} in Map Lead Fields.
  3. Map Email to ={{ $json.emails[0].value }} and Phone Number to ={{ $json.phones[0].value }} in Map Lead Fields.
  4. Repeat the same mapping structure in Map Lead Fields B and Map Lead Fields C for the email-only and SMS-only paths.
  5. Batch Full Contact Outreach outputs to both Store Current Run Time and Map Lead Fields in parallel to update the last run timestamp while preparing outreach data.

Step 5: Configure Outreach Actions

Send emails, SMS, and WhatsApp messages based on validated lead data.

  1. In Dispatch Email Message, set Send To to ={{ $json.Email }}, Subject to Following Up!, and Message to your email body.
  2. Credential Required: Connect your gmailOAuth2 credentials in Dispatch Email Message.
  3. In Send Text Outreach, set To to ={{ $('Batch Full Contact Outreach').item.json.phones[0].value }}, From to [YOUR_ID], and Message to your SMS copy.
  4. Credential Required: Connect your twilioApi credentials in Send Text Outreach.
  5. In Send WhatsApp Alert, set To to =+1{{ $('Batch Full Contact Outreach').item.json.phones[0].value }} and enable To WhatsApp.
  6. Credential Required: Connect your twilioApi credentials in Send WhatsApp Alert.
  7. Configure Dispatch Email Message B for the email-only path with Send To set to ={{ $json.Email }} and connect gmailOAuth2 credentials.

Use different message templates in Dispatch Email Message and Dispatch Email Message B to tailor outreach for different lead types.

Step 6: Test and Activate Your Workflow

Verify the workflow end-to-end, then switch it on for production use.

  1. Click Execute Workflow to run Scheduled Automation Start manually with test data.
  2. Confirm that Fetch Recent Leads returns new leads, then watch the flow through Split Lead Records and Validate Email & Phone.
  3. Verify that emails, SMS, and WhatsApp messages are sent from Dispatch Email Message, Send Text Outreach, and Send WhatsApp Alert.
  4. Check that Store Current Run Time updates the stored timestamp on completion.
  5. Toggle the workflow to Active to run it every 3 minutes in production.
🔒

Unlock Full Step-by-Step Guide

Get the complete implementation guide + downloadable template

Troubleshooting Tips

  • FollowUpBoss credentials can expire or need specific permissions. If things break, check your FollowUpBoss API access (and the HTTP Request node’s auth settings) first.
  • If you’re using Wait nodes or external sending, 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.

Next Steps

If your team also needs a lightweight system for meeting-booking follow-ups, Google Sheets + Gmail: follow ups that book meetings pairs well because it gives you a simple “send list” you can control without touching the CRM.

For teams doing outreach and then monitoring responses in real time, HighLevel + Slack: never miss a Gmail reply again helps you react fast when a lead finally replies (the moment that actually matters).

When you want to tighten qualification as well as speed, Gmail + HubSpot: qualify leads, faster follow ups is a nice add-on, because it turns “someone responded” into structured pipeline movement.

Need internal visibility so leads don’t fall into a black hole? Gmail + Slack follow ups that keep leads warm is great when sales and ops share ownership and you want a clear trail of what got sent.

Finally, if you want a cleaner audit trail for outreach performance, Google Sheets to Gmail, outreach emails sent and logged focuses on sending plus logging, which is perfect for weekly reporting and list hygiene.


Quick reference:

Quick Answers

What’s the setup time for this FollowUpBoss automation automation?

About an hour if your accounts and API keys are ready.

Is coding required for this lead follow-up?

No. You’ll mostly connect accounts, paste API keys, and adjust the message templates.

Is n8n free to use for this FollowUpBoss automation 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 OpenAI API usage and Twilio messaging costs.

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 modify this FollowUpBoss automation workflow for different use cases?

Yes, and you should. Most teams swap the Gmail content in the “Dispatch Email Message” nodes, adjust the If/Switch rules that decide email vs SMS/WhatsApp, and update the “Map Lead Fields” steps to match their FollowUpBoss fields. You can also turn off WhatsApp entirely by disabling the “Send WhatsApp Alert” node. If your compliance rules are strict, add an opt-out line and route “do not contact” leads to a no-send path.

Why is my FollowUpBoss connection failing in this workflow?

Usually it’s the FollowUpBoss API token or permissions used in the HTTP Request node. Regenerate the token, confirm it can read people/leads, and update it in n8n. If the workflow suddenly returns zero leads, also check the “last run” logic, because a bad stored timestamp can make your query too restrictive.

What volume can this FollowUpBoss automation workflow process?

A lot, as long as you batch it. n8n Cloud Starter gives you a monthly execution limit, while self-hosting has no execution cap (your server is the limit). This workflow uses Split in Batches nodes, so it can chew through big lead lists without timing out; just keep an eye on provider limits from Gmail and Twilio if you scale up fast.

Is this FollowUpBoss automation automation better than using Zapier or Make?

It depends. n8n is usually better for this kind of branching logic (email-only vs SMS-only vs both), batching, and tracking a “last run” state without paying extra for every path. Zapier or Make can be quicker for a simple two-step “new lead → send email,” but this workflow has more moving parts: validation, routing, and multi-channel sends. If you’re going to run this hourly or for high lead volume, self-hosted n8n is often the most cost-stable choice. Talk to an automation expert if you want help choosing.

Once this is live, follow-up becomes a system instead of a daily scramble. The workflow handles the repetitive checks and sending so you can focus on the conversations that actually close.

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.