How we handle GDPR data-subject requests on a deadline
Legal
The interview-scheduling agent we run on Kortix — daily, it finds candidates ready to schedule in Greenhouse, checks interviewer availability on Google Calendar, and drafts a slot proposal to the candidate and the calendar invites for a coordinator to confirm.
Once a candidate clears a screen, scheduling the next round becomes its own small project: read the interview plan to see who's on the panel, find a time when every one of those interviewers is actually free, propose it to the candidate, and get invites onto everyone's calendar before the slot goes stale. None of it is hard, but it's tedious across several interviewers and several candidates at once, and every day it sits undone is a day the loop stalls.
We run an interview-scheduling agent on Kortix that does the coordination every day. For every candidate marked ready to schedule in Greenhouse, it reads the interview plan, checks the panel's availability on Google Calendar, and drafts a slot proposal to the candidate plus the calendar invites for each interviewer. It never sends anything and never touches a hiring decision — a coordinator reviews every proposal and invite before it goes out. This is how we keep our own interview loops moving.
Scheduling an interview loop means combining two things that live in different systems: the interview plan — who's on the panel, how many rounds, how long each one runs — sits in Greenhouse, while whether those people are actually free sits in their calendars. Checking both by hand, for every candidate who clears a screen, is the kind of coordination work that's easy to fall behind on the moment more than one requisition is open at once.
The usual workarounds don't hold up. A shared scheduling link only works if every interviewer keeps it current, and it says nothing about who the panel actually is for this candidate. A coordinator juggling several calendar tabs and a Greenhouse tab in parallel can do it, but it doesn't scale past a handful of loops, and a slipped invite reads as disorganized to a candidate who's interviewing elsewhere too.
On Kortix, a daily cron triggers an agent. It spawns a fresh session (a cloud sandbox) that reads every candidate marked ready to schedule in Greenhouse, pulls that candidate's interview plan to see who's on the panel, checks each panelist's Google Calendar for open slots, and drafts a slot proposal for the candidate along with a calendar invite per interviewer. Every draft lands with the coordinator; the agent sends nothing and decides nothing about the candidate.
Open your Kortix workspace, start a new session, paste this prompt and send it. The agent writes the agent file, the interview-scheduling skill and the daily trigger, and opens a change request for you to review. Prefer clicks? Choose Use this template instead.
Set up a daily interview scheduling agent in this workspace.
Create the agent agents/interview-scheduler.md. Its job is to draft interview slot proposals and calendar invites for the coordinator to review. It may use the Greenhouse and Google Calendar connectors and the coordinator review email channel.
Create the skill skills/interview-scheduling/SKILL.md with these rules:
Add a cron trigger interview-scheduling-sweep to kortix.yaml. It runs the interview-scheduler agent every day at 08:00 with the prompt "Load the interview-scheduling skill and run one complete scheduling sweep."
Tell me which of these connectors are not connected yet.
Open a change request with all of it. Do not merge it.
Open Connectors in your workspace and connect Greenhouse and Google Calendar, then connect the coordinator review inbox under Channels. Credentials are brokered server-side and never enter the agent's machine.
Reads candidates ready to schedule and their interview plans.

Checks panel availability and drafts each interviewer's invite.

Delivers drafted slot proposals to the coordinator for review.
Merge the change request, then start a session with the interview-scheduler agent and send this prompt. Check the proposed slots against the panel's calendars before you let the schedule take over.
Run one interview scheduling sweep.
The change request added this trigger to kortix.yaml. From now on the agent
runs every day at 08:00, each run in a new session on its own cloud computer.
To change the time, edit the cron line, or open Triggers in the workspace.
triggers:- slug: interview-scheduling-sweep name: Daily interview-scheduling sweep on: cron: "0 0 8 * * *" run: agent: interview-scheduler prompt: Load the interview-scheduling skill and run one complete scheduling sweep.The agent has no send action and no action that creates a live calendar event. Every proposal and invite waits in the coordinator review inbox. The coordinator confirms the time with the candidate and sends everything. The agent never rejects a candidate, moves a stage or drafts an offer.
Each run ends with one batch in the coordinator review inbox. This is what a run looks like in the session:
Found 4 candidates ready to schedule. Drafted proposals with 3 open slots each for 3 of them. 1 panel has no common free slot in the next 5 business days, so that candidate is listed for the coordinator to handle.
Once it works, paste any of these into the same session.
When a panel has no common free slot, name the interviewer who blocks the most slots so the coordinator can ask for a swap.
Show each proposed slot in the candidate's time zone from Greenhouse, and in the interviewers' time zone in the invite drafts.
Every Friday, send the coordinator a list of candidates who have waited more than 5 business days for a confirmed slot.
The agent touches a candidate's next step in the hiring process, so the boundary between "proposed" and "confirmed" is the control that matters:
Scheduling an interview loop now starts with a proposal and a set of invites already drafted against the panel's real calendars, instead of a coordinator opening five tabs to find one time that works. The coordinator's day starts with a review instead of a hunt, and every send and every hiring call still stays with a person.