Skip to main content
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

Schedule a weekly sourcing pass. You review the matches and decide whom to contact; the routine only prepares drafts.
1

Connect your tools

If needed, Agent prompts you to connect Google Drive, GitHub, and Ashby. Provide the job description, must-have criteria, location, seniority, and target count. Confirm the correct Ashby workspace so existing candidates can be excluded.
2

Review and create the routine

Agent opens New routine with the title, schedule, time zone, and prompt filled in. Check Monday at 9:00 in your time zone. Keep the instruction not to send any outreach, then select Create routine.
3

Review your weekly shortlist

Each run reads the job description, searches GitHub, and skips people already in Ashby. It adds new sourced candidates with evidence of relevant experience and outreach drafts. The shortlist returns to the same Replit chat. You review and send; do not use the routine as the only hiring decision.
4

Find the routine and check its runs

Open Routines in the Replit sidebar. Select the run count to expand the history, use the play button to run it now, or use the switch to pause and resume the schedule.Open three GitHub profiles, check the evidence against your must-haves, and confirm they were not already in Ashby before contacting anyone. Refine noisy criteria in the chat.

​
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.

Generate release notes

Same GitHub connector for what the team already shipped.

Build an investor pitch deck

Same Google Drive connector for hiring managers who also pitch the company.