Automate interview reminders by connecting your scheduling system to Make.com, parsing appointment timestamps, and firing a 24-hour and 1-hour email sequence without human intervention. Sarah, an HR Director at a regional healthcare organization, used this exact approach to cut no-shows by 60% and reclaim 6 hours per week.

What This Workflow Solves

Interview no-shows are not a candidate problem. They are a process problem — and they are almost entirely preventable. Sarah’s team was scheduling 15 to 25 interviews per week across three hiring managers and two HR coordinators. Every scheduled interview required someone to manually send a confirmation at booking, a reminder the day before, and a same-day reminder the morning of the interview.

With no standardized template and no tracking system, reminders were inconsistent during busy weeks. The result: two to three missed interview slots every week, wasted hiring manager time, and a candidate experience that felt disorganized even when the hiring process itself was sound.

The deeper issue was cognitive load. Small HR teams burn out not from volume but from the constant mental overhead of manual follow-up tasks. UC Irvine research on task-switching found that interruptions cost workers an average of 23 minutes of refocus time per disruption. Multiplied across a team of three sending reminders ad hoc throughout the day, the drag compounds fast.

Sarah’s constraint: her organization used Keap as the system of record, and it was not going away. Any solution had to work within Keap, not replace it. Make.com™ was the integration layer that made it work.

If you are new to building workflows in Make.com, start with this plain-English guide to Make scenarios before continuing. For the broader recruiting automation strategy this workflow fits into, see how HR can fix broken hiring processes without slowing down the business.

Snapshot: Sarah’s Interview Reminder Transformation

Before You Build: What to Confirm First

Three things must be true before you open Make.com and build a single module:

1. Your scheduling system outputs a reliable appointment trigger. Keap’s native appointment booking page fires a clean webhook-compatible event on every new booking. If your team schedules interviews through calendar invites or email threads, you need a different entry point.
2. Candidate email and first name are captured consistently. If either field is blank or inconsistently formatted across your contact records, your reminders will fail silently or fire to the wrong address.
3. Appointment type is distinguishable. Sarah’s Keap account booked both interviews and internal team meetings through the same system. Without a filter on appointment type, the scenario would fire reminders for every meeting on the calendar.

If you are unsure whether your current process is clean enough to automate, run an OpsMap™ audit before building anything. Automating a broken process at speed produces broken results at speed.

For non-technical HR teams building their first Make.com workflow, this walkthrough of how a non-technical HR team started building their own automations covers the foundational concepts without assuming prior technical knowledge.

Step 1 — Set Up the Keap Appointment Trigger in Make.com

Open a new Make.com™ scenario and add a Keap: Watch Appointments module as the trigger. Configure it to fire whenever a new appointment is created in your Keap account.

Critical data to confirm is being pulled at this module:

• Candidate first name
• Candidate email address
• Appointment start date and time (in ISO 8601 format)
• Appointment type label
• Hiring manager name (from a custom field if available)

Add a Filter immediately after this trigger module. Set the filter condition to: Appointment Type equals “Interview” (or whatever label your team uses for candidate-facing bookings). This single filter prevents the scenario from firing for internal meetings, one-on-ones, or vendor calls booked through the same system.

Run the module once against a test appointment to confirm all fields are populating correctly before proceeding. Do not skip this step. Silent failures in reminder workflows are almost always caused by assuming a field is populated when it is blank for a subset of records.

Step 2 — Parse and Format the Appointment Date-Time

This is where most builds break. Keap returns appointment timestamps in ISO 8601 format. Make.com handles this format natively — but calculating a scheduled time that is exactly 24 hours before the appointment requires explicit date arithmetic, not a simple offset.

Add a Make.com Tools: Set Variable module (or use the built-in date functions within a subsequent module). You need two computed values:

• reminder_24h: appointment start time minus 24 hours
• reminder_1h: appointment start time minus 1 hour

In Make.com’s date function syntax, this looks like:

{{addDays(triggerDate; -1)}}  ← 24-hour reminder
{{addHours(triggerDate; -1)}}  ← 1-hour reminder

Format both outputs to match the timezone your Keap account is configured in. Timezone mismatch is the second most common failure point in reminder workflows — a reminder that fires at 2 a.m. local time instead of 8 a.m. is worse than no reminder at all from a candidate experience standpoint.

Test this module by entering a known appointment time and verifying that the computed reminder times are correct before proceeding to the email modules.

Step 3 — Build the 24-Hour Reminder Email

Add a Make.com: Sleep module after your date-time parsing step. Set the sleep duration to trigger at your computed reminder_24h timestamp. This tells the scenario to pause execution until the correct firing time rather than sending the email immediately when the appointment is booked.

After the sleep module, add a Keap: Send Email module. Configure the following:

• To: candidate email field from the trigger
• Subject: “Your interview tomorrow — [time] confirmation”
• Body: Include first name, interview date, interview time, location or video link, and a clear instruction for what to do if they need to reschedule

Keep the email under 100 words. Candidates who receive long reminder emails at this stage do not read them — they scan for the time and the link. Everything else is noise that increases the chance they miss the critical detail.

Sarah’s 24-hour reminder template included exactly four elements: greeting with first name, interview date and time, interview format (in-person address or video link), and a single sentence with a reschedule contact. Nothing else.

Step 4 — Build the 1-Hour Reminder Email

After the 24-hour email module, add a second Make.com: Sleep module set to fire at the reminder_1h timestamp. Follow it with a second Keap: Send Email module.

The 1-hour reminder is shorter than the 24-hour version. Its only jobs are to resurface the time, resurface the link or address, and confirm the candidate is expected. A subject line like “Your interview starts in 1 hour” with two sentences in the body is sufficient.

Do not add new information at the 1-hour mark. If the candidate has a question at this stage, they need a phone number or reply-to address, not more content. Ensure the reply-to is set to a monitored inbox, not a no-reply address.

Step 5 — Apply a Confirmation Tag in Keap

After both reminder emails have been sent, add a Keap: Add Tag module to apply a tag — “Reminders Sent” — to the contact record. This single step transforms your reminder workflow from a black box into an auditable process.

The tag creates three downstream benefits:

1. Visibility: Any team member can see at a glance whether a candidate has received reminders without opening the email send log.
2. Deduplication: If a scenario is accidentally triggered twice for the same appointment (which happens during testing), you can add a filter at the top of the scenario that skips contacts already tagged “Reminders Sent.”
3. Reporting: Over time, the tag allows you to segment candidates by reminder status and correlate with no-show rates — giving you data to improve the workflow further.

This tagging pattern applies to every automated touchpoint, not just reminders. For a broader look at how tagging structures reliable automation, see how Sarah compressed a 45-minute onboarding process to under 4 minutes using a similar tag-driven structure.

Step 6 — Test Before Going Live

Do not activate the scenario on live candidate data until you have completed all three of the following tests:

1. Dry run with a test contact: Book a test appointment using your own email address. Confirm the scenario fires, both emails arrive in the correct format, the timestamps are accurate, and the tag is applied.
2. Edge case: same-day booking. What happens if a candidate books an interview that starts in 45 minutes? Your 24-hour reminder will attempt to fire in the past. Add a router that checks whether reminder_24h is greater than the current timestamp. If not, skip the 24-hour email and send only the 1-hour reminder.
3. Edge case: cancelled appointment. Keap does not automatically notify Make.com when an appointment is deleted. If a candidate cancels after the scenario has already started sleeping, both reminders will still fire. In phase one, Sarah accepted this limitation and handled cancellations manually. In phase two, she added a Keap tag check before each email module — if the appointment tag had been replaced with “Cancelled,” the email branch would skip.

For a structured approach to evaluating any automated workflow before it goes to production, this checklist for evaluating Make scenarios before production covers the key verification steps.

How to Know It Worked

Track three metrics for the four weeks following activation:

1. No-show rate: Count missed interview slots per week. Sarah’s baseline was 2–3 per week. After activation, it dropped to fewer than one per week — a 60% reduction.
2. Reminder tag coverage: In Keap, filter contacts by the “Reminders Sent” tag. The percentage of scheduled interview contacts carrying this tag should reach 95%+ within two weeks. Anything lower indicates a trigger or filter configuration issue.
3. Team time on reminders: Ask each coordinator to track time spent on manual reminder tasks for two weeks. Sarah’s team went from approximately 6 hours per week across the team to zero manual reminder tasks remaining.

If no-shows remain above baseline, the most common causes are: timezone mismatch in the date-time calculation, the filter on appointment type excluding valid interview records, or the reply-to address being a no-reply that candidates cannot reach if they have questions.

Common Mistakes When Building This Workflow

Skipping the appointment type filter

Without a filter, the scenario fires for every appointment in Keap. Hiring managers, staff one-on-ones, and vendor calls all receive candidate-facing reminder emails. This creates confusion and erodes trust in the automation within the first week of operation.

Using a static delay instead of a computed timestamp

A static 24-hour delay from the moment the scenario runs is not the same as a reminder sent 24 hours before the appointment. If the scenario runs at 3 p.m. on a Monday and the interview is at 9 a.m. on Wednesday, a static 24-hour delay sends the reminder at 3 p.m. on Tuesday — 18 hours before the interview, not 24. Use computed timestamps tied to the appointment start time.

Building personalization before the base workflow is stable

Adding merge tags for hiring manager name, job title, department, or interview format before the core sequence is tested introduces multiple failure points simultaneously. Build the plain-text sequence first, confirm it runs cleanly for two full weeks, then layer in personalization tokens one at a time.

Not monitoring the scenario error log in the first two weeks

Make.com logs every scenario run and every error. In the first two weeks after activation, check the error log daily. Most configuration issues surface in the first five to ten real-world runs, not during testing. For a systematic approach to error handling in Make.com, this guide to routed error handling in Make.com covers the setup in detail.

No process for same-day cancellations

As noted above, Keap does not push cancellation events to Make.com by default. Define a manual process for same-day cancellations on day one, even if you intend to automate it later. A documented manual fallback is better than an undocumented gap.

What to Build Next

Once the base reminder workflow runs cleanly for 30 days, three natural extensions add measurable value without introducing significant complexity:

1. SMS reminders via a Make.com HTTP module: Text reminders have significantly higher open rates than email for same-day touchpoints. Add an HTTP module to a Twilio or similar SMS API after the 1-hour email module. This was Sarah’s phase-two addition.
2. Candidate confirmation reply tracking: Add a unique tracking link to the 24-hour email that tags the contact in Keap when clicked. Contacts who do not click within 12 hours of the 24-hour reminder can trigger a secondary outreach step — a phone call flag sent to the HR coordinator’s task list.
3. No-show rescheduling sequence: If a candidate does not show, a Make.com scenario can detect the absence (via a Keap tag applied by the interviewer post-interview) and automatically send a rescheduling email with a new booking link within two hours.

For teams ready to extend beyond reminders into a full recruiting automation stack, this guide to automating HR and recruiting end-to-end covers the full pipeline from sourcing through onboarding. The reminder workflow built here fits into the broader framework described in the AI automation advantage in candidate sourcing.

If your team is weighing whether to build workflows like this in-house or work with a partner, this 2026 comparison of DIY automation vs. hiring a Make partner breaks down exactly when each approach makes sense.

Additional Reading

• What Is a Make Scenario? The Plain-English Guide for Zapier Users
• How a Non-Technical HR Team Started Building Their Own Automations With Make + AI
• How to Run an OpsMap Audit Before Automating Anything
• How Sarah Compressed a 45-Minute Onboarding Process to Under 4 Minutes
• How to Evaluate a Make Scenario Built by AI Before It Goes to Production
• How to Set Up Routed Error Handling in Make With AI Assistance
• How HR Can Fix Broken Hiring Processes: Reducing Candidate Frustration Without Slowing Down the Business
• DIY Automation vs. Hiring a Make Partner in 2026: When to Do Each
• The Real Reason Small HR Teams Burn Out: It’s Not the Workload
• Automate HR & Recruiting: End the Manual Data Drain, Unlock Growth
• 7 Questions to Ask Before You Automate Anything (The OpsMap Checklist)
• 6 Ways the Make MCP Changes Automation Work for HR Teams
• What Is Automation-First? Why You Should Automate Before You Add AI
• Recruiting Automation: Transforming Hidden Costs into Measurable ROI
• 8 Make.com Scenarios That Are Now Faster to Build With AI