OpenClaw Job Hunt Agent: Wake Up to Job Matches (3 Setups That Work in 2026)

What a Job Hunt Agent Actually Does

Before picking a setup, agree on the job. A useful overnight job hunt agent does five things and stops short of a sixth that gets people in trouble.

• Pulls new postings from configured job boards every N hours (default: every 4 hours between 10pm and 6am local).
• Scores each posting against your skill profile and target salary band using a cheap model (Haiku-class is plenty).
• Filters hard requirements — location, remote-only, visa sponsorship, contract vs. full-time — before the model ever sees the listing.
• Delivers a morning digest via Telegram bot or email with the top 3-5 matches, each with a one-line rationale.
• Optionally drafts a tailored cover letter for the top match, ready for you to edit and send.
• Does NOT auto-apply. Auto-apply agents get flagged by ATS systems and burn bridges. Keep the human in the loop.

The fresh-posting timing matters more than people expect. A listing that drops at 2am Pacific gets twenty applications by 9am — your agent reading it at 4am and pinging you by 7am puts you in the first ten, which is roughly where recruiter attention concentrates.

Three Setups — Compared First

Here is the honest cost and effort breakdown for the three working setups. Pick by where you fall on the “I enjoy customizing” axis.

All three end with the same morning behavior — a curated digest in Telegram. The difference is how much of your weekend you spend getting there.

1. Pre-built CrewClaw Template — Running Tonight

Best for: Indie devs and solo job seekers who want this running before they go to bed, on the cheapest path that does not require any framework learning.

Buy the job-applicant template, fill out SOUL.md with your skills, target locations, and salary floor, drop the folder into Claude Code, and run npx openclaw start. The template comes pre-wired with Remote OK, We Work Remotely, HN Who is Hiring, and a generic Greenhouse / Lever / Ashby adapter. Cron config is included — change the timezone in one line and you are running overnight. Telegram bot integration is a single env var.

Get it: crewclaw.com/agents/job-applicant

2. Build From Scratch With OpenClaw + Claude Haiku

Best for: Devs who enjoy customizing every layer and want to wire up niche boards (academic listings, gov careers, a specific company subreddit) that the pre-built template does not cover.

The DIY skeleton is short: (1) Playwright or plain fetch against each board’s public feed, (2) a dedupe table (SQLite is plenty), (3) one Haiku call per posting with your skill profile in the system prompt and the listing in the user message, (4) a Telegram bot sender that wraps the top scores. The whole thing fits in 200-300 lines of Node. The slow part is not the code — it is finding which boards have stable feeds, which ones break weekly, and which ones serve Cloudflare interstitials. Expect to spend an evening on scraper hygiene the first week.

3. n8n + AI Agent Node — No-Code Workflow

Best for: People already running n8n for other automations who want to add a job hunt flow alongside existing workflows without spinning up a new runtime.

In n8n, the flow looks like: Schedule Trigger (every 4 hours overnight) → HTTP Request per board → Item Lists to flatten → AI Agent node for scoring (Anthropic credentials, Haiku model) → Filter (score >= 70) → Telegram node for digest. The strength is that you can fork the flow into Slack, Notion, or Google Sheets without writing API client code. The trap is that if you do not already run n8n, the learning curve eats most of the time you would save by going no-code. Pick this only if n8n is already in your stack.

The Agent Config That Matters: SOUL.md

Whichever setup you pick, the quality of your morning digest is decided by the skill profile you write. A loose profile returns 200 mediocre matches per week; a tight profile returns 5 strong ones. Four sections matter — target roles, hard requirements, soft preferences, and anti-match keywords.

# SOUL.md — Job Hunt Agent
target_roles:
  - Senior Backend Engineer
  - Staff Platform Engineer
  - Tech Lead (small team)
hard_requirements:
  remote: true
  salary_floor_usd: 140000
  visa_sponsorship_required: false
soft_preferences:
  stack: [Go, Python, TypeScript, Postgres, AWS]
  company_stage: [seed, series-a, series-b]
anti_match_keywords:
  - "contract-to-hire"
  - "PHP"
  - "on-site only"
  - "recruiter"

The anti_match_keywords section is the highest-leverage piece. Add the four to six phrases you find yourself dismissing every morning, and the agent skips them silently before the model ever scores them. After the first week of digests, you will know exactly what to add — recruiters, wrong-stack tags, locations you cannot move to. Iterate the profile every Sunday for the first month, then leave it alone.

Wiring It For Overnight Runs

The overnight pattern is the whole point — fresh postings, less competition, and a curated digest waiting when you wake up. Three things to wire correctly:

1. Cron pattern: 0 2,6 * * * runs at 2am and 6am local time. The 2am run sweeps overnight US Pacific drops, the 6am run catches Europe morning postings. Adjust the timezone in your crontab or in the OpenClaw scheduler config — whichever applies.
2. Telegram bot: Create a bot with BotFather, grab the token, drop it into .env as TELEGRAM_BOT_TOKEN, send any message to your bot to get your chat ID, drop that as TELEGRAM_CHAT_ID. Two env vars and you have a private channel for the agent. If your machine needs to stay awake to run the cron, see the always-on guide.
3. Why “while you sleep” works: Fresh postings get the most recruiter attention in the first 6 hours and the most applications in the first 24. An agent that pings you at 7am with a posting that dropped at 2am puts you in the early window where your application actually gets read. Compare to opening LinkedIn at 9am and being applicant #87 — same listing, completely different outcome.

FAQ