Can my recruiting assistant work with our current ATS?

A simple guide for recruiting teams weighing whether an AI assistant can work with the system they already use.

Supported capabilityApplies to Recruiting CRM or ATS · Claude

Short answer

It depends on the ATS, and on what you mean by it. There are two different things here: a recruiting CRM we build for you, and a third-party ATS you already run. The recruiting assistant is built reads-first, and where a business asks for writes and its system can carry them, we wire the write path deliberately so the assistant can create candidates, add notes, and advance interview stages. Whether your specific ATS can be connected depends on what it exposes. Tell us which one you run, and we will tell you straight.

Who this is for

A recruiting team or agency owner who wants an assistant to help with the pipeline, and needs to know whether it can work with the ATS they already depend on.

What you need first

• The name of the ATS you run, or a decision to use a recruiting CRM we build.
• A clear idea of whether you want the assistant to only read, or to write too.
• The permissions each person on the team should have.

How it works

1. Two different starting points. A recruiting CRM we build is ours to shape end to end. A third-party ATS you already run is connected only as far as that product allows.
2. What the ATS exposes decides the ceiling. Some ATS products have an API or an export we can build on. Some do not. What you can reach, and whether you can write, follows from that.
3. Reads first, writes when you ask. By default the assistant reads: open roles, candidate history, stage. Writing, creating a candidate or advancing a stage, exists only if you ask for it and the system can carry it.
4. The people. Each recruiter carries their own permissions, so the assistant’s reach matches the person’s.

What it can and cannot do

It can

• Work as a read-first assistant over a pipeline, where the ATS exposes a path.
• Write into a system that supports it, when you ask for writes and we wire the write path deliberately.
• Run as a custom recruiting CRM we build, if you would rather not depend on an existing ATS.

It cannot (until we verify your system)

• Connect an ATS that exposes no path. If the product has no API and no export, there is nothing to build on, and we will say so.
• Write into a system that cannot carry writes, or before you turn writing on.
• Be promised for your specific ATS until we have checked what it exposes.

Does it read only, or can it write?

Read-first by default: open roles, candidate history, stage. Writing exists only if you ask for it and the system can carry it. Where a business asks for writes and its system has a path for them, we build the write path so the assistant can create candidates, add notes, and advance stages, turned on deliberately. For your setup, writing is a deliberate choice, not the default.

Will it work with my specific ATS?

That depends on what your ATS exposes, and we will not promise it before we have checked. Some ATS products have an API or an export we can build on; some do not. Tell us the system you run, and we will give you a straight answer rather than a guess.

How we know

EvidenceSupported capability under gate

The recruiting assistant is built reads-first, and the write path, creating candidates, adding notes, and advancing stages, is a capability we wire deliberately where a business asks for it and its ATS can carry it. That is a capability we provision, turned on by choice, not a live customer write we are attesting here. What we will not do is name your ATS as supported, or promise a write, before we have verified what your system exposes.

Where to go next

• Talk to us about your recruiting setupTell us which ATS you run.
• Can I connect AI to software with no API?When the vendor gives you no API to connect to.
• Can AI change my POS or accounting records?Read-only first, and how writes work.