Compliance documents, chased from Recruit CRM and filed straight back
Tell GettingDocs which Recruit CRM candidates need documents and which ones. Amy chases them on WhatsApp or email until everything is in, uploads each file to the candidate’s record in a folder named after the document, and checks it.

Before you start in Brighton, could you reply with a photo or scan of your passport and your DBS certificate?
Thanks, Amy · Northside Recruitment
How Recruit CRM connects
Copy your API key
In Recruit CRM, the Account Owner opens Admin Settings → API & Integrations and copies the API key.
Paste it into GettingDocs
In GettingDocs, go to Settings → Integrations, choose Recruit CRM and paste the key. We check it immediately and tell you if it is wrong or your plan has no API access.
Nothing to set up in Recruit CRM
We register for Recruit CRM’s new- and updated-candidate notifications ourselves, so changes reach us without any webhook setup on your side.
Create a chase rule
Choose which candidates to chase and which custom field lists their documents. Preview exactly who would be chased, then switch the rule on.
Before you start
- A Recruit CRM Business plan or higher. Lower plans do not include API access.
- The Recruit CRM Account Owner, to create the API key (or a user the owner has given API access through a custom role).
- The owner of your GettingDocs account, to paste the key in.
What GettingDocs reads and writes in Recruit CRM
- Name, email address and phone number
- The custom fields your rules use
- Off-limits status, including its end date
- Email opt-out
- Files already on the candidate’s record
- Each collected document, uploaded to the candidate’s Files
- An optional note once every requested document is in
Recruit CRM stays your system of record. GettingDocs only adds documents and, if you want it, one note. Rejecting a document in GettingDocs never deletes anything from Recruit CRM.
Choosing who gets chased, and for what
Who
A chase rule decides who Amy contacts and what she asks them for.
What
Pick a candidate custom field, such as “Compliance documents required”, and map each of its values to one of your document types. You can also set documents that everyone the rule matches is asked for.

Automation
Rules decide which Recruit CRM candidates Amy chases, and for which documents.
Rule name
Care startersWho to chase
Candidates in Recruit CRM matching all of these conditions.
Which documents
Each candidate is chased for what their own Recruit CRM record says they owe.
How to decide
Read it from Documents required (dropdown)Preview: 14 would be chased
Nothing has been sent. This is what would happen if the rule ran now.
Would be chased for Passport, Right to Work.
Would be chased for DBS, References.
Would be chased for Passport, Right to Work, DBS.
Preview first
See exactly who a rule would chase, from a real search, before anything is sent.
No surprise blasts
Switching a rule on chases people who qualify from then on, not your whole database.
One conversation
If several rules match the same candidate, they get one message listing everything they owe.
Run now
Check a rule immediately instead of waiting for the next scheduled check.
Where documents land in Recruit CRM

Documents are uploaded to the candidate’s Files, grouped into a folder named after the document type.
- A passport lands in a “Passport” folder, a DBS in a “DBS” folder. Folders are created the first time they are needed.
- The candidate’s original filename is kept.
- Once the last outstanding document arrives, a note can be added to the record listing everything collected.
Filed first, then checked
Every file is filed the moment it arrives, so there's always a record of exactly what the candidate sent. Amy then opens it. If it's unreadable or the wrong document, she tells the candidate what was wrong and chases again automatically. If it's really a different document they owe, it's counted as that one instead.
If Recruit CRM can't accept a file, it goes to your Google Drive instead (if you've connected it) and you're told.
Checks what's already on file
How quickly changes reach GettingDocs

One candidate, as soon as they change
- Sarah Jones is edited in Recruit CRMA candidate is added or edited
- Recruit CRM tells GettingDocsA notification about Sarah, and only Sarah
- Sarah is checked against your rulesShe now needs a passport and a DBS
- Her chase goes outBy WhatsApp, text or email
Every rule, every candidate
- Amira KhanNot checked yet
- Tom HughesNew in Recruit CRM, no notice sent
- Priya PatelNot checked yet
- Daniel ReedNot checked yet
- …and every other candidate your rules cover
Webhooks
Set up automatically when you connect, and removed when you disconnect.
In detail
- A new or edited candidate usually reaches GettingDocs within a couple of minutes.
- A full check of every rule runs every 15 minutes, so nothing depends on a single notification arriving.
- Recruit CRM limits API requests per minute by licence count. Reading existing files across a large database can take a few hours the first time.
Who is never contacted, and other protections
Off-limits candidates are never contacted
A candidate marked off-limits in Recruit CRM is not messaged on any channel until the off-limits period ends. This also stops a chase already in progress.
Email opt-outs are respected
A candidate who has opted out of email is never chased by email.
Never matched by name
Candidates are matched by their Recruit CRM record, then exact email, then phone. Two Sarah Joneses are two people. If two records share contact details, that candidate is skipped and you’re told which record it clashes with, instead of guessing.
Merged duplicates handled
If you merge or delete a duplicate in Recruit CRM, GettingDocs checks and moves the chase to the surviving record.
Changed details follow the chase
Update a candidate's email or phone in Recruit CRM and GettingDocs picks it up. If they hadn't replied yet, the request is sent again to the new address.
Disconnecting is safe
Disconnecting removes access, keeps your rules and pauses their chases. Reconnect and they carry on, with no duplicate candidates.
Access and security
Encrypted credentials
Recruit CRM credentials are encrypted at rest with AES-256-GCM, and only used to talk to Recruit CRM on your behalf.
Owner-only connection
Only the owner of your GettingDocs account can connect or disconnect Recruit CRM. Owners and admins manage rules.
A full activity log
Every candidate a check looks at is shown under Sync activity as chased, updated, skipped or blocked, with the reason.
Each GettingDocs account connects to one ATS at a time.
Recruit CRM questions
Which Recruit CRM plan do I need?
Business or higher. Recruit CRM only offers API access on those plans, and GettingDocs connects through the API.
Who can create the API key?
The Recruit CRM Account Owner, under Admin Settings → API & Integrations, unless they have given another user API access through a custom role.
Will switching on a rule chase my whole database?
No. A rule chases candidates who match it from the moment it is switched on, or who change so that they match. You can preview exactly who that is before you turn it on, and use Run now to check immediately.
Where do the documents go in Recruit CRM?
Onto the candidate’s record, in a folder named after the document type, for example “Right to Work”. The candidate’s own filename is kept.
What if a candidate already has the document on their record?
GettingDocs reads the files already on the record before anyone is messaged. Documents it recognises are marked as received and not requested. Files it is unsure about go to a short review queue, and that candidate is not chased until you have answered.
Do I need to set up webhooks in Recruit CRM?
No. GettingDocs registers them for you when you connect and removes them when you disconnect.

Stop chasing Recruit CRM candidates by hand
See it working on your own candidates on a short call.
Book a call