Post: How to Build Automated Interview Scheduling in Make.com: Complete Walkthrough
Before You Build: Prerequisites
You need: Make.com account (Core plan minimum), API access to your ATS, Google Workspace admin access for Calendar API, and Gmail or SMTP access for candidate emails. Gather all API credentials before starting. Our OpsBuild™ approach always starts with a credentials audit — half of stalled implementations come from incomplete API access, not technical complexity.
Module 1: ATS Webhook Trigger
In Make.com, create a new scenario. Add a Webhooks module as the trigger. Copy the webhook URL Make.com generates. In your ATS admin settings, find “Webhooks” or “Notifications” and create a new webhook pointing to your Make.com URL. Set it to fire on the “Stage Changed” event for your target stage (typically “Phone Screen” or “Technical Interview”).
Test immediately: move a test candidate to that stage in your ATS and verify Make.com receives the webhook payload. Inspect the data structure — note exactly how candidate ID, name, email, and role data are structured in the payload.
Module 2: Parse Candidate and Role Data
Add a Tools → Parse module or use a Set Variable module to extract the fields you need: candidateId, candidateName, candidateEmail, candidateTimezone (if available), roleId, roleName, and hiringManagerId. Clean any HTML encoding in name fields using a Text → Replace module.
Module 3: Get Interviewer Assignment
Add a Make.com Data Store module configured to read from your role-to-interviewer mapping store. Query by roleId to get the assigned interviewer’s name, email, and Google Calendar ID. If you do not have a data store yet, create one with fields: roleId, interviewerName, interviewerEmail, calendarId, interviewDuration.
Module 4: Query Calendar Availability
Add a Google Calendar → List Events module. Set the calendar to the interviewer’s calendar ID from Module 3. Query the next 10 business days. Use a filter to collect busy times. Then use a custom function or iterator to generate 30-minute slots (or your standard duration) and exclude busy periods, pre-meeting buffer time, and slots outside business hours. Output: array of available slot timestamps in UTC.
Module 5: Convert to Candidate Time Zone
Use the Date/Time → Convert module or a custom function to convert each UTC slot to the candidate’s local time zone. If candidate timezone is unknown, default to Eastern Time with a note in the email. Format each slot as “Tuesday, May 6 at 2:00 PM ET / 11:00 AM PT.”
Module 6: Send Candidate Booking Email
Add a Gmail → Send Email module. Use an HTML email template that presents the top 3 available slots as clickable links. Each link is a Make.com webhook URL with the selected slot encoded as a URL parameter. Example: https://hook.make.com/[your-hook]?slot=2026-05-06T14:00:00Z&candidateId=12345. Subject line: “Choose Your Interview Time — [Role Name] at 4Spot.”
Module 7: Handle Candidate Slot Selection
Create a second Make.com scenario triggered by the slot-selection webhook. This scenario receives the selected slot and candidateId, creates a Google Calendar event with both parties, sends confirmation emails to the candidate and interviewer, and updates the ATS stage to “Interview Scheduled.”
Module 8: Error Handling and Escalation
Add an error handler to every HTTP module and external service call. If the ATS update fails, log to a Google Sheet. If no calendar slots are available, send an internal Slack alert to HR for manual scheduling. Set a 48-hour follow-up trigger to detect candidates who did not select a slot and send one reminder email before escalating to HR.
- Start with a credentials audit — confirm all API access before building any modules
- The role-to-interviewer data store is reusable across multiple automation scenarios — build it once
- Time zone conversion is the most common source of candidate scheduling complaints — always confirm the candidate’s local time
- Build Module 8 (error handling) from the start, not as an afterthought — production failures without error handling create silent errors
- The two-scenario architecture (trigger + confirmation) is cleaner and more maintainable than one complex scenario
Frequently Asked Questions
What Make.com plan do I need for interview scheduling automation?
The Core plan ($9/month) handles up to 10,000 operations per month — enough for teams scheduling up to 500 interviews per month. Teams scheduling 500+ interviews per month need the Pro plan ($16/month) for higher operation limits.
How do I connect Make.com to Greenhouse or Lever?
Both Greenhouse and Lever have native Make.com connectors available in the app directory. You connect via API key from your ATS admin settings. Authentication is OAuth or API token depending on the ATS.
Can Make.com handle multi-interviewer panel scheduling?
Yes, but it requires additional logic. You need to query multiple calendars, find the intersection of available slots, and present only times when all required interviewers are free. This is a more complex scenario but fully buildable in Make.com using array filtering.
For the complete HR workflow automation framework, see our pillar resource: Automated Offer Letters with Make.com: Transforming Talent Acquisition.
RELATED POST
