How we handle GDPR data-subject requests on a deadline
Legal
The outbound-sourcing agent we run on Kortix — daily, it finds candidates on LinkedIn for each open role, checks Greenhouse so no one already in the pipeline gets a duplicate reach-out, and drafts a personalized email for the recruiter to review and send.
Filling an open role isn't just reading the applications that arrive — the best candidates for a lot of roles aren't applying anywhere, they're already employed and not looking. Finding them means searching LinkedIn by hand, checking the ATS to make sure whoever you found isn't already in the pipeline, and writing an intro that actually references their background instead of a generic template. Done well, it's hours of work per role. Done under time pressure, it gets skipped and the role stays open longer.
We run a candidate-sourcing agent on Kortix that does the search and the first draft every day. For an open role, it finds matching candidates on LinkedIn, checks Greenhouse so it never resurfaces someone already in the pipeline, and drafts a personalized outreach email referencing each candidate's actual background. It sources and drafts only — the recruiter reviews every draft, and nothing sends and no one is added to the ATS without them. This is how we source our own outbound pipeline.
Outbound recruiting is a research problem before it's a writing problem, and neither half scales by hand. Searching LinkedIn for candidates who actually match a role's real bar takes real time, and doing it well across several open roles at once is more than one recruiter can sustain daily. Then there's the dedupe check: has this person already applied, already been contacted, already passed on an earlier round? Skipping that check means a candidate gets the same cold email twice, which reads as sloppy at best.
The usual shortcuts make it worse. A generic sourcing tool exports a list of profiles with no reference to the pipeline, so recruiters re-discover people who are already in Greenhouse. A templated outreach message goes out to everyone in the list with a name swapped in, and candidates who get a lot of these can tell instantly. Neither problem gets fixed by working faster — they get fixed by connecting the systems that already have the answer.
On Kortix, a daily cron triggers an agent. It spawns a fresh session (a cloud sandbox) scoped to an open role, searches LinkedIn for candidates matching that role's profile, checks the role's Greenhouse pipeline so it never proposes someone already there, and drafts a personalized outreach email for each new match — referencing that candidate's real background, not a template. Every draft lands in the recruiter's inbox for review; the agent never emails a candidate and never touches Greenhouse.
Open your Kortix workspace, start a new session, paste this prompt and send it. The agent writes the agent file, the outbound-sourcing 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 candidate sourcing agent in this workspace.
Create the agent agents/candidate-sourcing.md. Its job is to find new candidates for one open role and draft outreach for the recruiter. It may use the Greenhouse and LinkedIn connectors, and the recruiter review inbox.
Create the skill skills/outbound-sourcing/SKILL.md with these rules:
Add a cron trigger daily-sourcing-sweep to kortix.yaml. It runs the candidate-sourcing agent every day at 07:00 UTC with the prompt "Load the outbound-sourcing skill and run one complete sourcing sweep for the open role."
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 your ATS and LinkedIn. Then connect the recruiter's review inbox as an email channel. Credentials are brokered server-side and never enter the agent's machine.
Reads the role's pipeline to skip known candidates, read-only.
Searches for candidates who match the sourcing criteria.

Receives the drafted outreach batch for the recruiter to review.
Merge the change request, then start a session with the candidate-sourcing agent and send this prompt. Read every draft before you let the schedule take over.
Run one sourcing sweep for the open role.
The change request added this trigger to kortix.yaml. From now on the agent
runs every day at 07:00 UTC, 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: daily-sourcing-sweep name: Daily candidate-sourcing sweep on: cron: "0 0 7 * * *" run: agent: candidate-sourcing prompt: Load the outbound-sourcing skill and run one complete sourcing sweep for the open role.The agent drafts and stops. It has no send action and no write access to Greenhouse. The recruiter reviews each draft, edits it, sends it, and decides whether to add the candidate to the ATS.
Each run ends with one batch of drafts in the review inbox. This is what a run looks like in the session:
Reviewed 31 LinkedIn profiles and dropped 13 that were already in the pipeline. Drafted 18 personalized emails, each with the candidate's current role and the reason they matched. All 18 are in the review inbox, and nothing was sent.
Once it works, paste any of these into the same session.
Add a second open role with its own sourcing profile, and keep each role batch separate in the review inbox.
When I tell you which drafts got replies, add the angle that worked to the outreach notes in memory.
Also search GitHub for contributors to open-source projects that match the role skills, and dedupe them against the pipeline the same way.
The agent can search for and contact real people, so the boundary between "draft" and "send" is the control that matters:
Sourcing for an open role now starts with a batch already searched, deduped against the pipeline, and drafted with a real reference to each candidate's background. The recruiter's day starts with review instead of research, and every send and every ATS change still stays with them.