Source candidates

Ashby already screens inbound applications. This workflow is outbound: read the job description in Drive, find engineers who match on GitHub, skip anyone already in Ashby, and draft outreach for you to send. Agent logs new people as sourced with a short why-they-fit and a draft on the candidate. You review and send. Don’t use this as the only hiring decision.

​

Best for

• Technical recruiters who need a sourced list when inbound volume is too low.
• Hiring managers who need GitHub-matched engineers without living in search all day.

​

Connectors

​

Before you start

Have a job description with must-haves vs nice-to-haves. Connect Drive, GitHub, and Ashby. Say location, seniority, and how many names you want. Don’t use this as the only hiring decision.

​

Prompt the agent

​

What to expect

Agent reads the job description, searches GitHub, skips anyone already in Ashby, and returns a shortlist with drafts. You review and send. First pass will be noisy. Tighten must-haves after you see it. Open three GitHub profiles from the list, check they match the must-haves, and confirm those people are not already in Ashby before you send anything.

​

Make it work for you

​

Troubleshooting

• The shortlist is noisy: tighten must-haves vs nice-to-haves after the first pass. Ask for recent commits in a specific language or repo type, and drop people who look like current customers or competitor employees.
• People already in Ashby still appear: confirm Ashby is connected to the right workspace and that Agent is matching on email or GitHub username, not only display name.
• Outreach went out: this workflow should only draft. If anything sent, stop the routine and tell Agent never to email or message candidates.

​

Related