Designed for recruiters reviewing applicant pipelines. The agent works only with accounts connected to your Nilyo user.
What you can ask your agent to do
Resolve the owned job or Recruiter project
Your agent completes a clear Nilyo action and keeps the result linked to the correct provider account for the next step.
List applicants in that parent context
Your agent completes a clear Nilyo action and keeps the result linked to the correct provider account for the next step.
Retrieve and summarize supported resume data
Your agent completes a clear Nilyo action and keeps the result linked to the correct provider account for the next step.
How this workflow works
- Specify Classic Jobs or Recruiter and select the parent job/project.
- Ask Claude to list applicants and preserve their returned IDs.
- Fetch resumes only for selected applicants and compare against stated criteria.
Avoid inferring protected characteristics or making automated employment decisions. Use the agent to summarize job-relevant evidence for human review.
Questions people ask
Can it mix Classic and Recruiter applicants?
No. The identifiers and parent contexts are deliberately separate.
Does it make hiring decisions?
It can organize evidence, but human reviewers remain responsible for fair, lawful decisions.
Can it contact an applicant?
Where supported, messaging requires a separate person/inbox resolution chain.
Why use Nilyo for this?
Nilyo gives your chosen agent access only to the accounts you connect. Your provider passwords are never shown to the agent, and reading information does not silently authorize sending, inviting or deleting.
If several accounts, people or companies match, the agent asks you to clarify. If the result of an important action is uncertain, it checks what happened before attempting it again.
Related workflows