Interview Scheduling Automation Workflow: Slots Offered, Confirmed, Rescheduled
Scheduling an interview is six emails and a calendar puzzle, repeated for every candidate at every stage. The workflow reads the panel's calendars, offers the candidate three slots that work for everyone, books the one they pick, sends invitations with the right links, reminds both sides the day before, and handles 'can we move it' in the same thread without the recruiter touching it. The ATS stage updates itself, and no-shows drop because the candidate had a reminder and an easy way to reschedule.
- Built and run for you$197/month
- Custom build$2,000–3,500 one-time
- TriggerATS stage change (candidate moved to interview)
- Reference stackClaude + n8n
Per recruiter, up to 200 interviews a month, one calendar system. Panels across several companies (agency), interview loops with sequential rounds booked together, or an ATS without an API are a custom build.
Written by Max Zeshut
Founder at Agentmelt · Last updated Sep 14, 2026
Recruiters spend a third of their week on scheduling: finding slots across three calendars, chasing candidate replies, moving interviews, updating the ATS by hand. Every reschedule restarts the whole thread.
A candidate moved to 'interview' gets slot options within minutes, books in one click, and both sides get the invitation and a reminder. Reschedules take one reply. The recruiter's calendar stops being a switchboard.
How the workflow runs
Trigger, then 8 steps.
Trigger — ATS stage change (candidate moved to interview). Moving a candidate to an interview stage in Greenhouse, Lever or Ashby — or a row change in the tracking sheet — starts scheduling for that stage's panel.
- 01Read the stageIntake & triggersWebhookCandidate, role, interview stage, the panel for that stage, duration, and whether it is video or on-site.
- 02Find common slotsMatching, validation & reconciliationGoogle CalendarFree/busy across every panel member for the next ten working days, inside their working hours, avoiding lunch and back-to-back blocks; three options, spread across days.
- 03Offer the slotsDrafting & generationGmailOne email from the recruiter with three buttons or links, the format, who they will meet, and what to prepare — written for the stage, not a template dump.
- 04BookScheduling & remindersGoogle CalendarThe chosen slot becomes an event on every calendar with the video link or room, the candidate's CV attached for the panel, and the interview kit.
- 05RemindNotifications & escalationTwilioCandidate: 24 hours and 2 hours before, by email and SMS if they gave a number. Panel: 30 minutes before, with the CV and the scorecard link.
- 06Handle changesClassification & triageAI AgentA reply asking to move, cancel or ask a question is understood and acted on in the same thread; new slots are offered without the recruiter.
- 07Sync the ATSWrite-back & actionsHTTP RequestInterview scheduled, rescheduled, completed or no-show is written back to the candidate's record; the scorecard is opened for the panel.
- 08ReportEvaluation & learning loopsGoogle SheetsTime from stage change to booked, reschedule rate, no-show rate by role and stage, so the recruiter sees where the process drags.
Each capability page explains the pattern and lists every automation that uses it.
The template is built on n8n. The same steps run on Make, Zapier or plain code; the tool is chosen to fit your accounts, and you own the result.
- 01 Read the stage —
Webhook - 02 Find common slots —
Google Calendar - 03 Offer the slots —
Gmail - 04 Book —
Google Calendar - 05 Remind —
Twilio - 06 Handle changes —
AI Agent - 07 Sync the ATS —
HTTP Request - 08 Report —
Google Sheets
Data it touches
- ATS stages and panels
- Panel calendars (Google, Outlook)
- Candidate contact details
- Interview kits and scorecards
- Video-conferencing links
Guardrails
- Panel working hours and blocked times are respected; the workflow never books over a 'focus' block or outside hours.
- Candidates are never offered a slot less than 24 hours away unless the recruiter allows it for the stage.
- Every change is written to the same email thread, so the candidate has one conversation, not five.
- SMS only with a number the candidate gave; opt-out honoured.
- The recruiter is copied on every candidate-facing message and can take over any thread by replying.
Standard or custom
When this becomes a custom build.
The subscription covers the standard version — $197/month, setup and maintenance included. Three things move it to a custom build ($2,000–3,500 one-time), delivered into your accounts to keep. If one of them is you, say so on the audit and the plan prices both.
An agency scheduling against client panels in several calendar systems.
Full loops — several rounds booked as one sequence with dependencies.
An ATS or HRIS without an API, where write-back has to go through files or a browser.
Running the standard version first is the usual path: the exceptions it logs in the first month are the scope of the custom build, with your own numbers. How custom builds work.
Three slots, not a calendar link
A scheduling link hands the puzzle to the candidate and produces slots nobody on the panel wanted. Offering three specific times — spread across days, inside everyone's working hours, avoiding back-to-back interviews — is what a good coordinator does, and it books faster. The workflow computes those three from live availability every time.
Reschedules are the real cost
Half of interviews move at least once. Each move by hand is a fresh round of emails and a chance to lose the candidate. Handling 'can we do Thursday instead' in the same thread, automatically, with new slots offered in minutes, is where most of the recruiter's week comes back.
Reminders halve no-shows
Candidates who get a reminder the day before and two hours before, with a one-tap way to reschedule, show up. Panels who get the CV and the scorecard thirty minutes before run better interviews. Both are cheap; both are usually skipped when a person is doing the scheduling.
Tools in the stack
What it connects to.
| Tool | Role in this workflow |
|---|---|
| n8n | Orchestration, calendar logic, reminders, ATS sync |
| Claude | Understanding replies and drafting the candidate-facing messages |
| Greenhouse / Lever / Ashby | Stages, panels, write-back |
| Google Calendar / Outlook | Availability and bookings |
| Twilio | SMS reminders |
Building it in Zapier instead? The step-by-step recipe.
Zapier has no importable file, so this is the build guide: the same process as the n8n template and the Make blueprint, one Zap step per line. Expect 10–14 steps; the AI steps use the Anthropic (Claude) app, rules go in Code by Zapier, and every AI step is followed by a Filter that stops the Zap when Claude flags the item for a person.
Before you start
– Keep the values from "Config (edit me)" somewhere the steps can read them — a Storage by Zapier key each, or a Formatter → Utilities step at the top of the Zap: your name, your email, company, time zone, quiet hours (21–8), approver (channel or email), test mode.
– Connect the apps once: Anthropic (an API key), plus Greenhouse / Lever / Ashby, Google Calendar / Outlook, Twilio.
– Turn the Zap on with test mode on; read the first runs in Zap History before switching it off.
Steps
- Trigger — Webhooks by Zapier — Catch Hook (trigger). Moving a candidate to an interview stage in Greenhouse, Lever or Ashby — or a row change in the tracking sheet — starts scheduling for that stage's panel.
- Google Calendar — Create Detailed Event — Find common slots. Free/busy across every panel member for the next ten working days, inside their working hours, avoiding lunch and back-to-back blocks; three options, spread across days.
- Gmail — Send Email — Offer the slots. One email from the recruiter with three buttons or links, the format, who they will meet, and what to prepare — written for the stage, not a template dump.
- Google Calendar — Create Detailed Event — Book. The chosen slot becomes an event on every calendar with the video link or room, the candidate's CV attached for the panel, and the interview kit.
- Twilio — Send SMS — Remind. Candidate: 24 hours and 2 hours before, by email and SMS if they gave a number.
- Anthropic (Claude) — Send Message. Model
claude-sonnet-5, max tokens 2000, temperature 0.2. Paste the system prompt below; the user message is the fields from the previous step.You are the "Handle changes" step of the Interview Scheduling Automation Workflow workflow run by Agentmelt. Task: A reply asking to move, cancel or ask a question is understood and acted on in the same thread; new slots are offered without the recruiter. Rules: - Panel working hours and blocked times are respected; the workflow never books over a 'focus' block or outside hours. - Candidates are never offered a slot less than 24 hours away unless the recruiter allows it for the stage. - Every change is written to the same email thread, so the candidate has one conversation, not five. - SMS only with a number the candidate gave; opt-out honoured. - The recruiter is copied on every candidate-facing message and can take over any thread by replying. - Answer only from the data provided in the input. If something is missing, say so in the output instead of guessing. - If this step produces a message or a document, put the full text in `draft` (and a `subject` if it is an email); put a one-line summary in `summary`. - Set `needs_human` true whenever you are unsure, the input is unusual, or a rule above applies; a person will look at it. - Return valid JSON matching the output schema; no prose outside the JSON. Reply with a single JSON object and nothing else: the fields the task needs, plus "needs_human" (true when unsure), "confidence" (0–1) and "summary" (one line).
- Code by Zapier (JavaScript) — parse Claude's JSON. Input
text= Claude's reply; codereturn JSON.parse(inputData.text);so the fields become mappable in later steps. - Filter by Zapier. Only continue if
needs_human(from the previous step) *does not exactly match*true. Everything Claude is unsure about stops here — check Zap History for those, or add a Paths step whose second path posts the item to your approver. - Webhooks by Zapier — Custom Request. POST
https://harvest.greenhouse.io/v1/applications/…/move(Greenhouse Harvest API; add the API key header). Interview scheduled, rescheduled, completed or no-show is written back to the candidate's record; the scorecard is opened for the panel. - Google Sheets — Create Spreadsheet Row — Report. Time from stage change to booked, reschedule rate, no-show rate by role and stage, so the recruiter sees where the process drags.
Guardrails to keep
– Panel working hours and blocked times are respected; the workflow never books over a 'focus' block or outside hours.
– Candidates are never offered a slot less than 24 hours away unless the recruiter allows it for the stage.
– Every change is written to the same email thread, so the candidate has one conversation, not five.
– SMS only with a number the candidate gave; opt-out honoured.
– The recruiter is copied on every candidate-facing message and can take over any thread by replying.
Full blueprint: https://agentmelt.com/workflows/interview-scheduling-automation/ · n8n template and Make blueprint: https://github.com/zeshutmax/agentmelt-blueprints
Want this running without building it?
Automation workflow
$197/month
We set up, host and maintain this workflow on n8n and connect it to your tools. Setup included, cancel monthly, you keep the JSON.
Custom build
$2,000–3,500 one-time
Your systems, your rules, your edge cases. A one-off build on Claude and n8n, delivered with documentation and a walkthrough.
Per recruiter, up to 200 interviews a month, one calendar system. Panels across several companies (agency), interview loops with sequential rounds booked together, or an ATS without an API are a custom build.
Also sold one-time, installed in your own accounts, as part of the recruiters package and the hr teams package — kit $49 · install $249 · package $490.
FAQ
Frequently asked questions.
Does it work with Outlook calendars?
Yes — Google Calendar and Microsoft 365 are both standard. Mixed panels (some on each) are fine.
What if a candidate asks a question instead of picking a slot?
The reply is classified; questions about format, location or preparation are answered from the interview kit; anything else goes to the recruiter with the thread.
Can the candidate still email the recruiter directly?
Always. The recruiter is copied on every message and any reply from them takes the thread over; the automation steps back until the recruiter hands it the next stage.
Sources
What this blueprint is built on.
Vendor documentation the steps rely on, and the rules the guardrails are written against.
- Greenhouse — Harvest API developers.greenhouse.io/harvest.html
- Google — Calendar API: free/busy query developers.google.com/calendar/api/v3/reference/freebusy/query
- Twilio — Programmable Messaging docs www.twilio.com/docs/messaging