What does "works with RecruiterFlow" actually mean?
Ask a software vendor if their AI works with your ATS and the answer is always yes. Sometimes yes means a real API connection. Sometimes it means you can keep two browser tabs open and paste between them. If you run an agency desk, the difference is not academic: one of those saves you hours every week, and the other is the reason your database trails your inbox.
So here is the honest version. RecruiterClaw is an AI Chief of Staff for recruiters. It lives in Slack, installs on your own machine, and connects to any ATS that has an API. RecruiterFlow has one. Loxo comes wired out of the box; RecruiterFlow, like other API-capable ATSes, is connected during your white-glove install. You never touch a terminal, and you are live within 48 hours.
How does the RecruiterFlow connection get set up?
There is no integration project and no IT ticket. Setup is three conversations: a 30 minute discovery call, an onboarding call that goes deep on your desk, your clients, and your niche, and a remote install session where we drive and you watch. The ATS wiring happens inside that install session, alongside your email and calendar.
Onboarding is also where we scope exactly what the connection should touch for your workflow. That is a feature, not a caveat. An agency running splits across several recruiters needs different wiring than a solo headhunter working retained searches, and the white-glove model exists so the connection matches how your desk actually runs instead of forcing your desk to match the software.
What is AI allowed to do inside your database?
Your ATS is not just software. For an agency, the database is the asset: every candidate you have ever placed, every client contact, every note from every intake call. Letting an AI write to that without guardrails is how a good week turns into a restore-from-backup week.
RecruiterClaw's answer is structural. Every write to a connected ATS is additive only: create a record, add a note, add to a pipeline, update a field. Delete, merge, and archive are impossible by design. Not switched off, not hidden behind a setting. The capability does not exist, so no prompt, no bug, and no bad day can trigger it.
You also choose how much trust to extend, and when. Write-approval modes run from read-only, to confirm-each-write, to trusted. Most recruiters start with the AI asking before every write and loosen the leash as the work proves itself.
What work happens around your ATS?
The integration is plumbing. The reason to care is the work that flows through it. A job order lands and you describe the search in plain English in Slack: find me superintendents in Dallas, ground-up commercial, currently at a GC. RecruiterClaw searches 400M+ professional profiles and hands back a ranked shortlist in about 90 seconds. You refine it conversationally: drop the estimators, tighten to 30 miles. When the list is right, you say enrich the top 5 and get verified emails plus direct and mobile phones for exactly those people, in a ranked CSV. No credits burned on candidates you never vetted.
A strong candidate comes in without an order to match? Drop the resume in Slack with the word MPC. RecruiterClaw finds 5 to 10 companies with live openings matching that skill set, pulled from company career pages and 45 days fresh or newer, identifies the right hiring manager at each, enriches them with verified email and phone, and writes an anonymous 3-step outreach sequence. One CSV out: call sheet plus sequencer import.
The BD engine keeps running underneath. Job Finder scrapes company career pages directly, never LinkedIn, Indeed, or ZipRecruiter, so no fake listings, no duplicates, no recruiter-posted jobs. Two or more openings at one company gets flagged as a BD signal, which is often the first sniff of a client who needs an agency, not another job ad.
Around all of it sits the Chief of Staff cadence: a morning brief at 7 AM with email triage, calendar, pipeline alerts, deals needing a touch at 7 and 14 days, and one First Move Today. Pre-meeting intel before external meetings. Daily wins at 5 PM and a roll-up every Friday. Email drafts come out in your own voice, learned from your real sent mail, and nothing sends until you type the exact confirmation phrase.
What won't we claim?
One honest limit, because honesty is the brand: this page will not promise you a feature-by-feature list of what RecruiterClaw does inside RecruiterFlow. The specifics of what gets read and written are scoped during your onboarding call to match your workflow, and Loxo is the integration that ships wired out of the box. What carries to any connected ATS, guaranteed, is the safety model: additive-only writes, impossible deletes, and approval modes you control.
What does it cost to run next to RecruiterFlow?
A flat rate. No credits for tasks, no token budgets, no per-seat meters. Every conversation, task, and scheduled automation is unlimited, so nobody on your team hesitates to run one more search on a hunch. The only thing drawing from an allowance is candidate sourcing and contact enrichment, because verified contact data costs real money, and the allowance is sized generously. Founding-client pricing is live, and one placement more than covers the year. On an agency desk billing $28K fees, the math is not close.
Is RecruiterFlow supported out of the box?
Loxo is the ATS included out of the box. RecruiterFlow connects through its API, and API-capable ATS integrations are wired during the white-glove install. You never touch a terminal, and you are live within 48 hours.
Can RecruiterClaw delete or merge records in RecruiterFlow?
No. Every write to a connected ATS is additive only: create, note, add to pipeline, update. Delete, merge, and archive are impossible by design. The capability is not switched off, it simply does not exist.
Does RecruiterClaw replace RecruiterFlow?
No. Your ATS stays your system of record. RecruiterClaw is the Chief of Staff working around it: sourcing across 400M+ profiles, building MPC campaigns, flagging BD signals, running the morning brief, and drafting email in your voice. The ATS holds the data; the Chief of Staff does the legwork.
Do I need IT help to set up the integration?
No. Setup is a 30 minute discovery call, an onboarding call that goes deep on your desk, and a remote install session where we drive and you watch. The ATS connection is wired for you during that install.
Where does my agency's data live?
On your own machine. Memory, client profiles, conversation history, and candidate files stay local, credentials sit in the machine's encrypted keychain, and RecruiterClaw operates no servers holding client data. You own your data. We don't.