Automate interview slot scheduling via GoodTime and sync confirmed interviews back to the ATS and calendar
domain: goodtime.io · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Connect GoodTime to your ATS (Greenhouse, Lever, iCIMS, or Jobvite) using the ATS-specific integration guide; Greenhouse requires a Harvest API key with the permissions specified in GoodTime's integration documentation.
Connect GoodTime to the interviewers' calendars (Google Workspace or Microsoft Office 365) so GoodTime can read availability and write confirmed interview events.
Configure interviewer panels and availability rules in GoodTime for each role or stage so the scheduling engine can propose valid slots without manual coordinator input.
When a candidate advances to a scheduling stage in the ATS, GoodTime automatically syncs the candidate and requisition data via the ATS API or streaming API (for iCIMS); the scheduling request is created within GoodTime.
GoodTime generates available slot options and sends the candidate a self-scheduling link; once the candidate selects a slot, GoodTime writes the confirmed calendar event to all participants and updates the ATS stage or activity log.
Monitor the GoodTime dashboard for scheduling failures or expired candidate links; configure reminder sequences to prompt candidates who have not selected a slot within a defined window.
Known gotchas
Interviewer calendar access must be actively maintained — if a calendar connection is revoked or an OAuth token expires, GoodTime will show interviewers as having no availability and slots will stop generating without obvious error messaging to recruiters.
The iCIMS integration uses the iCIMS Streaming API, Profile API, and List API in combination; a misconfiguration of any one of these can cause candidate data to stop syncing while other iCIMS functions appear healthy.
Self-scheduling links sent to candidates have an expiration window; if candidates delay responding and the link expires, a coordinator must manually regenerate and resend it — build an escalation alert for links approaching expiry.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?