Skip to content
agentusehub

Source and screen candidates and reply over WhatsApp

Recruiters run OpenClaw to monitor GitHub for new contributors overnight, score resume folders against a job description, and draft WhatsApp replies held for human approval.

Time saved
Not reported
Setup time
Not reported
Running cost
Not reported
Cost range
Not reported

Use case overview

Recruiters run OpenClaw to monitor GitHub for new contributors overnight, score resume folders against a job description, and draft WhatsApp replies held for human approval.

Reported experience

  1. What they did

    OpenClaw runs on a dedicated machine such as a Mac Mini. A 6 AM scheduled task uses the browser skill to visit chosen GitHub repos, pull contributors, filter for recent activity and send a Telegram digest. For screening, the recruiter drops PDF resumes and a JD into the workspace, and the agent returns a ranked CSV with rationales. For replies, it drafts a response and sends it to the recruiter on WhatsApp, and sends it only after the recruiter says yes.

  2. How it went

    The guide says API costs run roughly $10 to $30 a month for light use and $100 to $200 for heavy use. It gives no measured sourcing results. LinkedIn scraping is fragile, and a clean first workflow takes most of a day.

  3. Worth knowing

    Sandboxing, approval prompts and workspace limits ship with 2.0 but are off by default, so turn them on before pointing the agent at candidate data.

Example prompts

Try with OpenClaw
Every night, check GitHub for new contributors to [repos or topics] who match [skills, location] and add them to [sheet]. Also score the resumes in [folder] against this job description: [paste JD], with a one-line reason each. Draft WhatsApp replies to [candidates or contacts], but hold them for my approval and never send without it.