The email infrastructure
for autonomous recruitment screening.
Developers building recruitment agents need primitives to read applications, reply with screening questions, and label candidates by pipeline stage. Mailgent provides the email API so your agent can screen candidates, manage hiring pipelines, and coordinate interviews without recruiter bottlenecks.
API Primitives used
mail.list_messagesReceive applications
Monitor the recruiting inbox for new applications, candidate responses, and follow-up questions about the role.
mail.get_threadReview candidate history
Load the full conversation thread to understand a candidate's qualifications, previous interactions, and any questions they have asked.
mail.replySend screening questions
Reply with role-specific screening questions, assessment links, or interview scheduling options.
mail.update_labelsTrack pipeline stage
Label candidates as new, screening, interview, offer, or rejected. Keep the pipeline organized.
Recruiters drown in applications. Great candidates get lost.
A single job posting generates hundreds of applications. Recruiters spend days reading resumes, sending screening emails, and coordinating schedules — often responding so slowly that top candidates accept other offers before hearing back. Speed is a competitive advantage in hiring, and manual screening is the bottleneck.
Developers building recruitment agents need email primitives to process applications, engage candidates, and manage pipeline stages. Mailgent provides mail.list_messages for intake, mail.get_thread for candidate context, mail.reply for screening, and mail.update_labels for pipeline tracking.
How to build it.
mail.list_messagesReceive and read applications
Your agent monitors the recruiting inbox with mail.list_messages, pulling new applications. It reads each message and attached resume to assess initial fit.
mail.replyScreen candidates
The agent replies with role-specific screening questions using mail.reply — years of experience, relevant skills, salary expectations, availability. It adapts questions based on the role.
mail.update_labelsScore and advance
Based on screening responses, the agent scores candidates and labels them by stage using mail.update_labels. Top candidates are flagged for interview scheduling.
Example prompt
“Check for new applications to the Senior Engineer role. Send screening questions about system design experience and availability. Score responses and label anyone with 5+ years experience as 'interview-ready'. Notify the hiring manager.”
What developers build.
Initial resume screening
Build agents that read applications, assess candidate fit against job requirements, and immediately reject or advance qualified applicants to screening.
Screening questionnaires
Build agents that send role-specific screening questions to candidates via email, score their responses against your criteria, and advance qualified applicants to the interview stage.
Interview scheduling
Build agents that coordinate interview times between candidates, hiring managers, and panel members via email, handling reschedules and sending confirmations.
Candidate nurturing
Build agents that keep promising candidates warm during long hiring cycles with periodic updates, company news, and check-ins on their availability.
Why not use an ATS?
Applicant Tracking Systems organize candidates in a database, but the communication still happens via email. Most ATS platforms send rigid templates and cannot hold natural screening conversations. Candidates experience a robotic process that reflects poorly on your employer brand.
Mailgent gives you email primitives for natural candidate engagement. mail.reply holds real conversations, mail.get_thread maintains context across interactions, and mail.update_labels tracks pipeline stage. Your agent screens like a recruiter, not a form.
Candidate data isolation
Recruitment emails stay in a dedicated agent identity. Candidate information never mixes with other business communications.
GDPR-ready pipeline
Every candidate interaction is logged. Support data deletion requests with a clear record of what was stored and when.
Bias audit support
Full conversation logs enable audit of screening criteria and decisions for fairness review.