How to Create an Automated Follow-Up Sequence in Make.com

Follow-up sequences are one of the most impactful automations you can build for clients. Research consistently shows that 80 percent of sales require five or more follow-ups, yet most businesses stop at one. An automated sequence built in Make.com ensures every lead gets the persistent, personalized follow-up they deserve without anyone on the team having to remember to do it. This guide covers the complete architecture — multiple interconnected scenarios, reply detection, AI personalization, and the maintenance structure that makes the system sustainable.

The Three Failure Modes to Design Around

Before building anything, understand the three failure modes that kill most follow-up automations. Failure mode one: no reply detection. The system keeps sending emails even after someone has responded, which destroys trust and can get the sending domain marked as spam. Every serious follow-up system must monitor the inbox and stop the sequence the moment a reply comes in. Failure mode two: generic templated messaging. Sending the same email to a roofing contractor and a dental practice with only the first name swapped out. Recipients can recognize copy-paste immediately. Failure mode three: wrong timing. Sending all seven emails in five days burns out the contact before they have had time to think.

Architecture: Multiple Interconnected Scenarios

A robust follow-up sequence in Make.com uses four separate scenarios rather than one giant workflow. The Enrollment Scenario fires when a new lead is captured, adds them to the sequence tracker, and schedules the first email. The Sequence Manager runs every 30 minutes, checks for contacts that are due for their next touch, and sends the appropriate email. The Reply Detector runs every 15 minutes, monitors the inbox for replies, and updates contact status to stop the sequence. The A/B Test Analyzer runs weekly to assess which email variants are performing better.

Separating these into distinct scenarios makes the system maintainable six months after you build it. When reply detection breaks, you fix it without touching the sending logic. When a client wants new email templates, you update Airtable records without touching any scenario at all.

Step 1: Set Up the Airtable Sequence Tracker

Create an Airtable base called Follow-Up Sequences with fields for Contact Name, Email, Company, Current Step (number, starts at 0), Sequence Status (Active, Paused, Completed, Replied, Unsubscribed), Next Send Date, Lead Source, Enrolled At, Last Email Sent, Notes, and Sequence Type. The Sequence Type field allows one system to handle multiple different sequences — for example, a cold outreach sequence, a warm inbound sequence, and a past-client re-engagement sequence simultaneously.

Create a second table called Email Templates with fields: Sequence Type, Step Number, Subject Line, Body (HTML), and Delay Days. Populate it with your email templates. When you want to update copy, change it in this table. No touching the scenario. This separation is what makes the system actually maintainable for clients.

Step 2: Build the Enrollment Scenario

Create the Enrollment Scenario in Make.com with a webhook trigger or a native integration like HubSpot Watch New Contacts or Typeform Watch Responses. Before creating any Airtable record, add an Airtable Search Records module to check whether the contact already exists by email. Add a filter that only continues if the search returns zero results. This prevents duplicate enrollments when someone submits the same form twice.

When creating the Airtable record, set Next Send Date to one hour from now using the Make.com date function. Set Current Step to 0 and Sequence Status to Active. After creation, add a Slack notification to let the team know a new lead has enrolled. For the most common lead sources — website forms, HubSpot, Typeform — standardize the incoming data into one consistent shape before it hits the enrollment scenario. Your scenario only needs to handle one data format, regardless of source.

Step 3: Build the Sequence Manager

The Sequence Manager runs every 30 minutes and is the core of the system. It starts with a Schedule trigger, then an Airtable Search Records module filtered to Sequence Status equals Active and Next Send Date is less than or equal to the current time. Add an Iterator to process each due contact one at a time. Then fetch the email template for the contact's current step from the Email Templates table.

Before sending, add an OpenAI Create a Completion module to personalize the opening line. Pass the contact's name, company, industry, and the email topic to GPT with a prompt requesting one sentence that feels personal and specific to their business. Prepend the output to the template body. This adds roughly one cent per ten emails and consistently improves reply rates. Then send the email via Gmail. After sending, add a Sleep module of two to three seconds between each email to avoid Gmail API rate limits when processing large batches.

After the send, use a Router to check whether this was the last step in the sequence. If not, update the Airtable record: increment Current Step by one, set Last Email Sent to now, and calculate the new Next Send Date by adding the Delay Days from the template. If it was the last step, set Sequence Status to Completed.

Step 4: Build the Reply Detector

Create the Reply Detector scenario with a Gmail Watch Emails trigger running every 15 minutes on the inbox. When a new email arrives, use Airtable Search Records to find the matching contact by the sender's email address. Add a filter to only continue if a match exists with Sequence Status equal to Active.

Update the matching record to set Sequence Status to Replied. Then add an OpenAI Create a Completion module to classify the reply as INTERESTED, NOT INTERESTED, QUESTION, OUT OF OFFICE, or UNSUBSCRIBE. Route each classification: INTERESTED gets an immediate calendar booking link sent via Gmail; NOT INTERESTED gets status updated to Replied No and added to suppression list; QUESTION gets a draft response generated by OpenAI and posted to a Slack thread for a human to review; OUT OF OFFICE gets the return date parsed and Next Send Date updated to one day after that date; UNSUBSCRIBE gets status set to Unsubscribed and a confirmation email sent.

Step 5: Handle Business-Hours Sending and Timezone Logic

Emails sent Tuesday through Thursday between 9 AM and 11 AM consistently show higher open and reply rates than emails sent on Mondays or Fridays. Add a filter before every send that checks the day of week and hour of day. If the current time falls outside business hours or on a weekend, skip the send and update Next Send Date to the next business day at 9 AM instead.

Use Make.com's formatDate function with the E format code to get the numeric day of week (1 equals Monday, 7 equals Sunday). If the result is 6 or 7, calculate the days until Monday and add that to the next send date. This small detail prevents your client's automated emails from landing at 3 AM on a Saturday, which both wastes the send and signals to email providers that the messages are automated.

Scaling This for Multiple Clients

Once built for one client, replicating for the next is mostly configuration. Each client gets their own Airtable base (clone the structure) and their own set of Make.com scenarios (clone from your master template, update the Airtable and Gmail connections). Total setup time per new client: 20 to 30 minutes.

Charge $500 to $1,500 for setup depending on complexity, plus $200 to $400 per month for maintenance. The maintenance fee covers Make.com operation costs, your monitoring time, and ongoing optimization. Sequences need tuning every 60 to 90 days. Subject lines stop working, seasonal response rates shift, and new competitors enter the market. A retainer keeps you engaged and keeps the system performing. For a deeper look at the AI personalization layer, see how to personalize cold emails at scale with AI and how to write cold email sequences that convert.